Content
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A lean, highly actionable skill body with copy-paste-ready commands and well-organized sections. The main gap is the engagement workflow, which lists steps but omits explicit validation checkpoints for its destructive/risky phases.
Suggestions
Insert validation/verification gates into the Common workflow — e.g. after delivery confirm a callback before enumerating, and verify lateral SMB reachability before pivoting — to lift workflow clarity to 3.
Add a brief 'verify / cleanup confirmation' checkpoint before the teardown step so destructive actions are gated on an explicit check.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Dense, action-oriented content with no padded explanations of what a C2 is or basic concepts; tables and commands earn their tokens and assume Claude's competence. | 3 / 3 |
Actionability | Fully executable, copy-paste-ready commands throughout — the full 'mythic-cli payload create' invocation with all parameters, install commands, and a complete Python scripting example. | 3 / 3 |
Workflow Clarity | A clear 9-step 'Common workflow' sequence exists, but it involves destructive/risky operations (lateral movement, persistence, teardown) with no explicit validation or verify-before-proceeding checkpoints, capping clarity at 2 per the rubric. | 2 / 3 |
Progressive Disclosure | No bundle files exist, but the body is cleanly organized into well-signaled sections (Setup, Agent matrix, Profile matrix, Build, Tasking, OPSEC, Workflow, Comparison) with no nested references and easy navigation. | 3 / 3 |
Total | 11 / 12 Passed |