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.
The content is highly actionable and reasonably token-efficient, with concrete commands, templates, and metrics throughout a clearly phased workflow. Its main weaknesses are absent validation checkpoints for a risky batch operation and failure to use the existing reference bundle, leaving large detail blocks inlined in SKILL.md.
Suggestions
Add explicit validation checkpoints between phases: verify infrastructure with a test send to controlled accounts, confirm SPF/DKIM/DMARC on the attack domain, and validate landing-page capture before launching the batch campaign.
Link the existing bundle files from the body (e.g. 'GoPhish API details: see references/api-reference.md', 'Campaign lifecycle: see references/workflows.md') and move the email templates and tools table into references/ to slim SKILL.md.
Trim the Verizon DBIR sentence, the 'When to Use' section that duplicates the frontmatter description, and the hardcoded 2025 dates in example templates, which are time-sensitive and will age poorly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with commands, templates, and tables and assumes domain competence, but contains trimmable material: the Verizon DBIR statistic sentence, a 'When to Use' section that duplicates the frontmatter, and time-dated example content ('Q1 2025', 'March 15, 2025') that is not isolated in a deprecated section. | 4 / 5 |
Actionability | Mostly executable guidance: real theHarvester/dig/Evilginx commands, GoPhish campaign JSON, and complete email and vishing scripts. Minor gaps remain, e.g. 'sudo apt install gophish' is not an actual apt package, the campaign JSON is illustrative rather than an API payload, and the email HTML is elided. | 4 / 5 |
Workflow Clarity | Phases 1-6 provide a clear sequence from OSINT through reporting, but a batch campaign against 200 employees has no validation checkpoints (no test send, no infrastructure verification, no pre-launch DMARC/SPF checks), which caps workflow clarity at 3 per the batch-operation rule. | 3 / 5 |
Progressive Disclosure | The phase structure is well organized, but the body never links to the existing bundle files (references/api-reference.md, workflows.md, standards.md, scripts/, assets/template.md), and large email templates and tool/API reference blocks that belong in those files are inlined in SKILL.md. | 3 / 5 |
Total | 14 / 20 Passed |