Content
92%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 mature, highly actionable skill: executable commands for every format family, a validated YARA workflow, a calibrated verdict rubric, and clean one-level-deep progressive disclosure into three real reference files. The only cost is length — the intro and a few meta-asides could be trimmed without losing any instructional value.
Suggestions
Trim the opening paragraph and the cross-references paragraph, which largely restate the description's scope and trigger content — the highest-token, lowest-instruction text in the body.
Compress the 'Why not findings.json?' aside to a single sentence (or fold it into the report-format section), since it justifies a format choice rather than instructing the analyst.
Consider moving the ten-item external bibliography to a reference file — it is rarely consulted mid-execution and would shorten the always-loaded body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and assumes Claude's competence — it never explains what a hash, YARA, or a PE file is, and every judgment call ('Packed is not malicious', 'Signed is not benign', 'No hit is not clean') is domain-specific knowledge worth its tokens. Minor trims remain: the opening paragraph restates the description nearly verbatim, the cross-references paragraph is long, and the 'Why not findings.json?' aside justifies rather than instructs, so it matches anchor 4 ('efficient; minor instances that could be trimmed') rather than anchor 5's 'every token earns its place'. | 4 / 5 |
Actionability | Copy-paste-ready commands with flags throughout: 'shasum -a 256', 'strings -a -n 6 -e l', 'floss -n 6 -- sample.bin', 'capa -j sample.bin', 'olevba --decode --reveal', the pefile imphash one-liner, ready-made rg/grep triage patterns, a populated CSV example, and a full report template. Common cases (PE, ELF, Mach-O, scripts, Office, archives/LNK/ISO) are each covered with the concrete tool invocation, matching 'fully executable; specific examples cover the common cases'. | 5 / 5 |
Workflow Clarity | A clearly sequenced 10-step flow with explicit validation checkpoints: hash 'before anything else', YARA rules must 'match, and show which strings hit' with 'must be 0' on a goodware corpus ('A rule nobody tested against goodware is a draft'), and the verdict step has an evidence bar plus a devil's-advocate check ('argue the other side once') with four worked cases. Recovery paths are stated (re-run Steps 4–6 on the unpacked copy; unknown verdict → 'say what would resolve it'), matching anchor 5's explicit validation and feedback loops. | 5 / 5 |
Progressive Disclosure | The body is an actionable overview that links three existing one-level-deep reference files exactly at point of need: static-triage.md from Steps 3 and 5, ioc-export.md from Step 7, yara-rules.md from Step 8 ('Full guidance is in [references/yara-rules.md]'). All three files exist in references/ with no nesting, and detail (per-format commands, STIX field lists, YARA style guidance) is appropriately deferred to them, matching anchor 5. | 5 / 5 |
Total | 19 / 20 Passed |