Content
82%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.
An exemplary knowledge-dense skill body: every gotcha is load-bearing and codebase-specific, and the corrected Cypher is directly usable. The main improvements are adding executable examples for the block↔symbol join and anchoring constraints, and possibly splitting the RFC-correction backstory into a reference file.
Suggestions
Include an executable Cypher example for the reconstructed BasicBlock↔symbol join (id-prefix + shifted startLine bounds) so the anchor-5 anchoring rule is copy-paste ready rather than prose-described.
Add a short example invocation and result shape for the 'flows' mode to mirror the coverage given to 'controls'.
Consider moving the RFC #567 correction backstory into a reference file so SKILL.md keeps only the currently-correct query form.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line carries codebase-specific, non-derivable knowledge (layer build order with milestone IDs, the +1 line-basis shift, the absence of a rel-property index, "no Function→BasicBlock edge") with zero padding and no re-teaching of concepts Claude already knows. | 5 / 5 |
Actionability | The corrected guard-clause Cypher is executable and copy-paste ready, and both modes are specified with concrete invocation shapes, but the BasicBlock↔symbol join and the raw-cypher anchoring requirement are described only in prose without executable examples — minor gaps versus fully copy-paste-ready coverage. | 4 / 5 |
Workflow Clarity | A clear "When to Use" list, two well-defined query modes, and explicit failure-mode handling (the no-PDG-layer note, empty-result debugging, guard polarity warning) give an unambiguous usage path; it lacks the explicit validate/fix/retry checkpoints of the anchor-5 pattern, though none are strictly required for a read-only query surface. | 4 / 5 |
Progressive Disclosure | The single-file body is well organized with clear section headers and no buried or nested references, and no bundle files are needed; the ~80-line dense body sits slightly past the lean single-file ideal, and peripheral material such as the RFC #567 correction could be moved to a reference file. | 4 / 5 |
Total | 17 / 20 Passed |