Content
75%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 a well-structured, actionable workflow: clear phases, concrete CLI commands, a complete output template, thorough edge-case and failure handling, and a meaningful anti-patterns list. The main costs are repetition of the notability-gate rule across three sections, a vague fetch step, and references that point outside the skill bundle.
Suggestions
State the notability-gate author-credit rule once (in the Contract or Phase 3) and have other sections reference it by name to cut repeated tokens.
Make Phase 1 concrete: name the fetch tool per content type (web fetch for articles, which API/tool for tweets, which PDF reader) instead of 'use appropriate tools'.
Add an explicit post-save verification step (e.g., confirm the page exists via search/query before reporting 'ingested') to close the workflow's validation gap.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and operational with no explanations of concepts Claude already knows, but the notability-gate/author-credit rule is stated three times (Contract, Phase 3, Anti-Patterns) and the inline author-credit format appears twice. Minor trimming is possible without losing clarity, which fits anchor 4 rather than the lean anchor 5. | 4 / 5 |
Actionability | Concrete commands ("gbrain files upload-raw <file> --page <slug>", "gbrain sync", "gbrain write-request <request_id>") plus a full output-format template and specific filing rules make the guidance mostly executable. Phase 1 ("Use appropriate tools for the content type") remains high-level without naming the tools, keeping it below anchor 5. | 4 / 5 |
Workflow Clarity | Six clearly sequenced phases with real checkpoints for a mutating skill: pre-ingest duplicate-URL search, fetch-failure recovery, write_pending polling, and an anti-pattern guard against assuming fetch success. It approaches anchor 5, but the fetch method in Phase 1 and any post-write/sync verification are left implicit — anchor 4 (most checkpoints present, minor gaps). | 4 / 5 |
Progressive Disclosure | Well-organized sections (Contract, Phases, Output Format, Edge Cases, When it fails, Anti-Patterns) with clearly signaled one-level references to external convention files ("skills/_brain-filing-rules.md", "skills/conventions/quality.md"). No bundle files exist to split content into, and the body is cohesive, but the referenced paths live outside the bundle and cannot be navigated from it — anchor 4 rather than 5. | 4 / 5 |
Total | 16 / 20 Passed |