Content
43%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 compact and well-sectioned but carries almost no substance: guidance is generic boilerplate that would apply to any skill, the sole concrete action points to a resource file that is missing from the bundle, and no actual security patterns, checks, or workflow steps appear. It reads as a template skeleton rather than an operational skill.
Suggestions
Ship resources/implementation-playbook.md (or remove the reference): the dangling reference is the body's only concrete instruction and currently points to nothing.
Replace the generic Instructions bullets with skill-specific steps, e.g., a triage workflow for audits (map external calls, check access control on privileged functions, verify checks-effects-interactions, re-test) so the body instructs rather than describes.
Inline a small quick-start set of the highest-value secure patterns (reentrancy guard, checks-effects-interactions, access-control modifier, CEI in token transfers) instead of the filler 'Do not use this skill when' section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean (~35 lines) with zero over-explanation of concepts Claude already knows, and sections are compact. Not a 5 because the generic 'Instructions' bullets ('Clarify goals, constraints, and required inputs'), the vacuous 'Do not use this skill when' section, and the opening line duplicating the frontmatter description are filler that does not earn its place. | 4 / 5 |
Actionability | The only concrete instruction in the entire body is 'If detailed examples are required, open resources/implementation-playbook.md'; everything else — 'Apply relevant best practices and validate outcomes', 'Provide actionable steps and verification' — is abstract direction with no specific steps, patterns, code, or commands. Not a 1 because the conditional pointer to the playbook is a real, executable instruction; not a 3 because no concrete guidance for any actual task (writing, auditing, hardening a contract) is present. | 2 / 5 |
Workflow Clarity | 'Clarify goals → apply best practices → validate outcomes' is a rough sequence, but it is a generic template applicable to any skill, with no domain-specific steps and no validation method behind 'validate outcomes'. Not a 1 because a rough sequence with a verification mention exists; not a 3 because the steps are boilerplate rather than defined for smart-contract work, and no checkpoints are actually specified. | 2 / 5 |
Progressive Disclosure | Sections are well organized (Use when / Do not use / Instructions / Resources) and the reference is clearly signaled one level deep in a Resources section. However, the referenced file resources/implementation-playbook.md does not exist in the bundle (no resources/ directory is present), so the only promised detailed content is unreachable — structure is present but navigation breaks in practice, which fits anchor 3 better than 4. | 3 / 5 |
Total | 11 / 20 Passed |