Content
57%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 body is well-organized and concise but stays at a high level: steps are abstract prose with no executable code, validation checkpoints are absent, and the useful bundle files (api-reference.md, agent.py) are never referenced from SKILL.md. Most gains come from surfacing the existing executable material and adding verification steps.
Suggestions
Add a concrete, copy-paste-ready example in the Steps or a Quick Start section, e.g. `python agent.py --group "APT29" --layer-output apt29_layer.json`, and link to scripts/agent.py and references/api-reference.md so the executable detail is reachable.
Insert validation checkpoints into the workflow — e.g., confirm the group resolved before extracting techniques, sanity-check technique_count > 0, and validate the generated layer JSON against the Navigator schema before exporting.
Replace the templated 'When to Use' bullets and the redundant Overview with tighter, skill-specific guidance to remove filler and avoid restating the frontmatter description.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly lean body, but the Overview re-states the description and the 'When to Use' bullets are templated filler ('When SOC analysts need structured procedures for this analysis type') that could be trimmed. | 4 / 5 |
Actionability | Steps are abstract prose ('Query ATT&CK STIX data for target threat group using attackcti', 'Extract techniques…via STIX relationships') with no executable code or commands in the body; only an expected-output JSON is concrete, and the executable agent.py / CLI usage in the bundle is never surfaced. | 3 / 5 |
Workflow Clarity | Five steps are clearly sequenced but there are no validation checkpoints or feedback loops (e.g., verify the group resolved, confirm technique count, validate the layer JSON before export). | 3 / 5 |
Progressive Disclosure | Section structure is clean (Overview/When to Use/Prerequisites/Steps/Expected Output), but the body never links to the existing bundle files (references/api-reference.md with API+CLI tables, scripts/agent.py with the executable CLI), so navigation to the real detail is missing. | 3 / 5 |
Total | 13 / 20 Passed |