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.
The content is a strong, lean instruction skill: a clearly sequenced white-box loop with an explicit validation gate, concrete tooling, and no filler. Its main gaps are the missing validate_finding call signature and a slightly long single-file layout that could offload reference material. The report title convention with good/bad examples is a particularly effective pattern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and skimmable: bullet lists of sinks and trust-boundary sources, a one-line find command, and no padding or explanation of concepts Claude already knows. A few interpretive sentences (e.g. "Projects with zero advisories are either very secure or don't have a disclosure process") could be tightened, which keeps it just below the leanest anchor. | 4 / 5 |
Actionability | Guidance is mostly executable: a concrete find command, kg_add_node snippets with props, named tools (semgrep, grep), and explicit validate_finding requirements (poc_command, success_patterns, negative_command, negative_patterns, cvss_vector). Gaps remain — validate_finding is never shown as an actual call signature, and sink discovery says "use semgrep" without a concrete query example. | 4 / 5 |
Workflow Clarity | The five-step core loop (map project, map trust boundaries, crown jewels, trace source to sink, prove or discard) is clearly sequenced, and Step 5 is an explicit validation checkpoint with a working PoC, a negative control run, matching patterns, and a prove-or-discard decision loop ("An unreproduced claim remains unverified"). This matches the anchor for explicit validation steps with feedback loops. | 5 / 5 |
Progressive Disclosure | The body is well-organized into clear sections with no buried or nested references, and the skill ships no bundle files so everything is appropriately self-contained. It exceeds 50 lines and a couple of sections (mechanism families, report title convention) could plausibly be split into reference files, which keeps it below the top anchor for its size. | 4 / 5 |
Total | 17 / 20 Passed |