Content
77%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 highly actionable, well-sequenced audit workflow with strong validation and fail-open handling. Its weaknesses are repetition of the no-data rationale, which costs tokens on every invocation, and a monolithic single-file layout that inlines template and engine-variant content a references/ bundle would absorb.
Suggestions
State the NOT ASSESSED rule once (e.g. in the 'Insufficient input' section) and reference it elsewhere in one line instead of restating it in the blockquote, Phase 3, and Phase 5.
Move the full report template and the per-engine glob variants into references/ files (e.g. references/report-template.md, references/engine-scans.md) and link to them from the phases.
Trim the justification paragraphs (false-clean-pass examples, 'absence of evidence' aphorism) to a single sentence each; the rules themselves already carry the instruction.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The instructions are mostly concrete commands, but the NOT-ASSESSED doctrine is repeated four times (top blockquote, 'Insufficient input', Phase 3, Phase 5) and includes philosophical justification ('Absence of evidence is never evidence of absence', the false-clean-pass hypothetical) that could be trimmed without losing the rule. | 3 / 5 |
Actionability | Copy-paste-ready Grep patterns with exact regexes, per-engine Glob variants (Unreal Content/, Unity Assets/, web data/), explicit status thresholds with percentage bands, table templates, and exact user-facing prompts — fully executable and covering the common engine cases. | 5 / 5 |
Workflow Clarity | Five clearly sequenced phases with explicit validation checkpoints (the FOUND/ABSENT input checklist before any report, the fail-open denominator check, 'stop if the check fails') and error-recovery paths (NOT ASSESSED verdicts, unresolved-code-root handling). | 5 / 5 |
Progressive Disclosure | The single ~325-line file is well-sectioned, but everything is inlined: the full report template, per-content-type scan lists, and engine-specific glob variants are candidates for reference files, and there are no bundled references to lean on (the .claude/docs/*.md pointers are repo docs, clearly signaled but external). | 3 / 5 |
Total | 16 / 20 Passed |