Content
65%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A highly actionable, well-sequenced command reference for WordPress pentesting, with copy-paste-ready examples at every phase. Its weaknesses are token efficiency (duplicated path/flag tables and repeated command listings), no validation checkpoints in the destructive brute-force and exploitation phases, and a fully monolithic 480-line structure with no progressive disclosure into reference files.
Suggestions
Deduplicate the reference material: the 'Common WordPress Paths' table repeats the Phase 1 file listing and the WPScan flag table repeats the Phase 7 inline comments — keep each in one place only.
Add explicit validation/verification checkpoints to the risky workflows (e.g., confirm a credential works before launching wp_admin_shell_upload, verify webshell access with a harmless command like `id` before use, and stop brute-force on lockout signals), integrating the existing Troubleshooting guidance into the workflow steps.
Split the SKILL.md into an overview plus one-level-deep reference files (e.g., references/wpscan-flags.md for the Quick Reference tables, references/exploitation.md for Metasploit and manual webshell techniques, references/troubleshooting.md) to reduce the monolithic body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean command examples rather than concept explanations, but contains clear duplication: WordPress paths are listed in Phase 1 and again verbatim in the 'Common WordPress Paths' table, WPScan enumeration flags are explained in Phase 7 comments and repeated in the Quick Reference table, and there is unsolicited padding like "WordPress powers approximately 35% of websites". Not a 2 because there is no explanation of concepts Claude already knows; not a 4 because the duplicated tables and repeated wpscan invocations could be meaningfully trimmed. | 3 / 5 |
Actionability | Fully executable, copy-paste-ready commands throughout: curl probes, wpscan invocations with real flags, nmap scripts, Metasploit module configurations, and complete PHP webshell code. Specific examples cover the common cases for every phase of the workflow. | 5 / 5 |
Workflow Clarity | Phases 1-10 are clearly sequenced (discovery → enumeration → exploitation), but the batch password-attack and destructive exploitation workflows include no validation or verification checkpoints — per the rubric guideline, missing validation for destructive/batch operations caps workflow clarity at 3. The Troubleshooting section offers some error-recovery guidance but it is disconnected from the workflow steps, so a 4 is not warranted. | 3 / 5 |
Progressive Disclosure | Section structure is good with clear headers and a Quick Reference, but the ~480-line skill is entirely monolithic with no bundle files at all — reference material (enumeration flag tables, common paths, XML-RPC exploitation detail, troubleshooting) that clearly belongs in separate files is inlined. It is above a 2 because the structure is not minimal or buried, but below a 4 because nothing is offloaded and there are no references to split content into. | 3 / 5 |
Total | 14 / 20 Passed |