Content
81%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 lean, highly actionable audit skill: concrete inventory commands, executable PoCs, explicit positive/negative validation contracts, and a well-sectioned single-file structure. Only minor issues hold it back — a few undefined placeholders in code examples and slightly overweight inline material (PoC payloads, CVSS tables) that could be split into reference files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and assumes competence — recognition signals, attack vectors, audit greps, PoC code, a CVSS table, and a chain-promotion note with no padding or beginner-level explanation. Minor trimming is possible (the opening trust-boundary paragraph and the one-line definition of typo-squatting in 'Typo-squatted framework package' restate things Claude can infer), which keeps it at anchor 4 rather than 5. | 4 / 5 |
Actionability | Concrete, mostly copy-paste-ready guidance throughout: four grep inventory commands, an executable Python trigger-sweep script, a bash typo-squat check, a per-artifact 3-question checklist, indicator/CVSS tables, and a validate_finding contract. Minor gaps — the Python snippet's 'API' variable is undefined, the bash snippet depends on an unspecified 'known-good.txt', and the glob '/workspace/**/*.txt' requires globstar — place it just below anchor 5. | 4 / 5 |
Workflow Clarity | The audit workflow is clearly sequenced (inventory greps by artifact class → per-artifact origin/push-rights/eval checklist → PoC payload → validate) and closes with an explicit validation contract: success_patterns, a negative_command ('same query / build with the suspicious artifact removed'), and negative_patterns that define a feedback loop. This matches anchor 5's checklist + explicit validation + error-recovery pattern; no destructive/batch cap applies since negative controls are present. | 5 / 5 |
Progressive Disclosure | No bundle files exist and the single 145-line body is cleanly sectioned (signals → vectors → workflow → goals → PoCs → validation → CVSS → chaining), with one clearly signaled cross-reference to the prompt-injection skill. It is not anchor 5 because the simple-skill exception is scoped to under-50-line skills: material such as the PoC payloads and the CVSS variant table could live in reference files to slim the main body, i.e. good structure with minor organization gaps. | 4 / 5 |
Total | 17 / 20 Passed |