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.
A highly actionable, well-structured instruction skill: concrete commands, exact formats, a full output template, and an explicit failure-handling protocol. Its main deductions are triple-statement of the notability rule, validation steps that live outside the phase sequence, and inconsistent external reference paths.
Suggestions
State the notability-gate rule once (in Phase 3) and have the Contract and Anti-Patterns sections reference it by name instead of restating it, trimming the duplicated fetch-failure handling between Edge Cases and 'When it fails'.
Move the duplicate-URL pre-check and fetch-success verification into the numbered phases as explicit validation checkpoints (e.g., a 'Phase 0: Check brain for existing coverage' and a verify step after fetch) so the sequence itself carries its validation.
Normalize the external reference paths to a single consistent root and confirm they resolve from the skill's location, since none of the referenced files ship in the skill bundle.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and domain-specific with no explanations of concepts Claude already knows, but the notability-gate rule is stated three times (Contract, Phase 3, Anti-Patterns) and fetch-failure handling is duplicated between Edge Cases and 'When it fails'. | 4 / 5 |
Actionability | Provides copy-paste-ready commands ('gbrain files upload-raw <file> --page <slug>', 'gbrain write-request <request_id>', 'gbrain sync'), exact formats (back-link template, '**Author:** {Author}, {role}'), a complete output template, and edge cases covering the common failure modes. | 5 / 5 |
Workflow Clarity | Six clearly numbered phases with a gated author decision tree and an error-recovery section (exit codes, write_pending polling), but the duplicate-URL check and fetch-success verification are described in Edge Cases/Anti-Patterns rather than embedded as validation checkpoints in the phase sequence. | 4 / 5 |
Progressive Disclosure | Well-organized sections with detailed filing rules correctly deferred to one-level-deep referenced files ('skills/_brain-filing-rules.md', 'skills/conventions/quality.md') instead of inlined, though the referenced paths are inconsistently rooted ('skills/...' vs '../conventions/...') and none exist in the skill bundle. | 4 / 5 |
Total | 17 / 20 Passed |