penetration-test-planner

Quick Review

This skill is severely underdeveloped. The description is vague and circular ('plan penetration test planner operations'), providing no concrete understanding of what the skill actually does. Task knowledge is nearly absent—there are no specific methodologies, frameworks, penetration testing phases (reconnaissance, scanning, exploitation, post-exploitation), tool integration, or actionable steps. The structure is clear but hollow, with generic placeholder content throughout (e.g., 'Provides step-by-step guidance' without actual steps, 'Best practice recommendations' without listing any). Novelty is low because the skill adds minimal value over asking a CLI agent directly about penetration testing; it provides no specialized tooling, automation, or domain-specific workflows that would justify its existence as a distinct skill. To improve: define specific penetration testing workflows (OWASP, PTES, etc.), integrate concrete tools (nmap, Metasploit, Burp Suite commands), provide actual test planning templates, and demonstrate how this reduces the token/effort cost compared to ad-hoc querying.