Content
67%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 body gives a well-structured, actionable workflow with sound policy on overrides, report format, and cautious fixing, and it points to a clean one-level reference bundle. Its main weakness is redundancy — the decision tree repeats workflow branches and several instructions are stated multiple times — plus a few vague or malformed sentences.
Suggestions
Merge the 'Workflow' and 'Workflow Decision Tree' sections into one structure: the no-matching-guidance branch is currently stated twice in slightly different forms.
Trim duplicated report-delivery instructions ("also report it to the user directly... Also tell the user where the final report was written to") and fix the broken sentence "a full report should be produced describe anyways the project fails to follow security best practices guidance".
Add a brief list of the available reference files (e.g. the 10 `<language>-<framework>-<stack>-security.md` files) so the right file can be picked without listing the directory first.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient policy content, but the Workflow and Workflow Decision Tree sections repeat the no-matching-guidance branch, report-delivery instructions are stated twice, and padded asides ("and this is why insecure code lives on for so long") could be trimmed. | 3 / 5 |
Actionability | Concrete executable guidance throughout (filename pattern `<language>-<framework>-<stack>-security.md`, named reference file, report path `security_best_practices_report.md`, severity sections with numeric IDs, one-finding-at-a-time fix policy), though some directions remain vague ("think a little bit about what you know... try to search online") and one report-format sentence is broken. | 4 / 5 |
Workflow Clarity | Clear sequence from language/framework identification, through reference loading and mode selection, to report and fixes, with explicit regression/test validation in the Fixes section; however checkpoints are partially implicit (no verification step after language identification). | 4 / 5 |
Progressive Disclosure | References are one level deep, real, and well-signaled via the documented filename pattern (all named files verified present in references/), with cross-language general advice appropriately inline; minor gap in that no index of available reference files is provided. | 4 / 5 |
Total | 15 / 20 Passed |