CtrlK
BlogDocsLog inGet started
Tessl Logo

wordpress-penetration-testing

This skill should be used when the user asks to "pentest WordPress sites", "scan WordPress for vulnerabilities", "enumerate WordPress users, themes, or plugins", "exploit WordPress vulnerabilities", or "use WPScan". It provides comprehensive WordPress security assessment methodologies.

68

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with extensive executable WPScan/Metasploit commands and a clear phased sequence, but it is verbose with redundant tables and lacks validation checkpoints in its destructive exploitation workflows. Progressive disclosure is weak because everything lives in a single monolithic file with no references.

Suggestions

Trim redundancy: remove the Quick Reference tables that restate flags already documented in Phase 7, and consolidate the repeated version-detection snippets into one location to earn the conciseness score-3 anchor.

Add explicit validation/verification checkpoints in the credential-attack and exploitation phases (e.g., confirm valid credentials before running wp_admin_shell_upload, verify the uploaded webshell responds) to lift workflow clarity toward 3.

Split large reference material — Advanced Techniques, Quick Reference tables, and Troubleshooting — into separate files under references/ linked from a leaner SKILL.md to improve progressive disclosure.

DimensionReasoningScore

Conciseness

Commands are concrete, but the ~480-line body is padded with redundancy — the Quick Reference tables restate flags already explained in Phase 7, version detection recurs across phases, and the intro adds fluff Claude knows ('WordPress powers approximately 35% of websites'); not a 3 because not every token earns its place.

2 / 3

Actionability

Provides copy-paste-ready, executable commands throughout (wpscan, curl, msfconsole, searchsploit, cewl) with specific flags and parameters, matching the score-3 'fully executable' anchor.

3 / 3

Workflow Clarity

Phases 1–10 are clearly sequenced, but the destructive exploitation and batch brute-force workflows lack explicit validation/verification checkpoints (e.g., verify credentials before exploiting, confirm shell access), so per the guidelines workflow clarity is capped at 2 rather than 3.

2 / 3

Progressive Disclosure

No bundle files exist and the entire content sits in one monolithic SKILL.md; sections are well-organized, but reference-worthy material (advanced techniques, quick reference, troubleshooting) that could be split into separate files is inline, so it does not reach the score-3 'content appropriately split' anchor.

2 / 3

Total

9

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it states concrete actions, provides natural trigger phrases users would actually say, and explicitly covers both what the skill does and when to use it. It is clearly distinct from other skills with low conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'pentest WordPress sites', 'scan WordPress for vulnerabilities', 'enumerate WordPress users, themes, or plugins', 'exploit WordPress vulnerabilities', 'use WPScan' — matching the score-3 anchor.

3 / 3

Completeness

Explicitly answers 'when' via 'This skill should be used when the user asks to...' and 'what' via 'provides comprehensive WordPress security assessment methodologies'; both halves are present with explicit trigger guidance, so it is not capped at 2.

3 / 3

Trigger Term Quality

The quoted triggers ('pentest WordPress sites', 'scan WordPress for vulnerabilities', 'exploit WordPress vulnerabilities', 'use WPScan') are natural phrases a user would say, with good coverage of variations; not a score-2 'some keywords' case because several common phrasings are present.

3 / 3

Distinctiveness Conflict Risk

A clearly distinct WordPress-pentesting niche with WPScan-specific triggers that are unlikely to fire for unrelated skills; it is not generic enough to fall to score 2.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
zebbern/claude-code-guide
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.