Content
73%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 is an unusually actionable policy skill: exact file lists, a scannable regex table, executable PowerShell validation code, copy-paste alert templates, and two clearly sequenced workflows with explicit validation and fail-loud checkpoints. Its main weakness is redundancy — patterns and rules are repeated across the table, the code example, and the Anti-Patterns section — and its length suggests the pattern library could be split into a reference file.
Suggestions
Deduplicate the secret patterns: keep them in the regex table only and have the PowerShell example reference the table (or include all 7 patterns in the code) instead of repeating 3 of them.
Trim the Anti-Patterns section to only the cases not already covered in Patterns (e.g., keep "extracting just the host" and "temporary files") to cut repeated rules.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly directives, tables, and templates with no explanation of concepts Claude already knows, but there is real duplication: the regex patterns appear in the scanning table and again (3 of 7) in the PowerShell example, and the Anti-Patterns section restates rules already covered in Patterns. This matches anchor 3 (mostly efficient but could be tightened) rather than anchor 2, since there is no concept-level padding. | 3 / 5 |
Actionability | Guidance is highly concrete — exact prohibited/allowed file lists, a 7-row regex table, copy-paste report templates, and executable PowerShell with real git commands (git reset HEAD <file>, git filter-repo). The minor gap keeping it below anchor 5 is that the example scanning code implements only 3 of the 7 table patterns, so it is not fully copy-paste ready on its own. | 4 / 5 |
Workflow Clarity | Both workflows (pre-commit validation and leak remediation) are numbered with explicit validation checkpoints, a STOP/block/exit error path, and a fix-and-retry feedback loop ("remove the secret, replace with placeholder, and try again"), plus an explicit ordering note ("AFTER staging files, BEFORE calling git commit"). Validation is present, so the destructive-operation cap does not apply; this matches the anchor-5 example of clear sequence with explicit validation and error-recovery loops. | 5 / 5 |
Progressive Disclosure | Sections are well organized (Context, Patterns, Examples, Anti-Patterns) with no nested or buried references, but at roughly 190 lines the regex pattern library and remediation scripts are content that could live in a separate reference file. Anchor 4 (good structure, most content appropriately placed, minor organization gaps) fits; anchor 5's under-50-line simple-skill exception does not apply. | 4 / 5 |
Total | 16 / 20 Passed |