Content
81%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 strong, safety-first skill body: fully executable handler code, explicit phase sequencing with validation gates and error-recovery loops, and complete output templates. The only notable gaps are the absent concrete guidance for Dropbox/B2 sources and some conformance-test boilerplate that inflates token cost.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and earns its tokens: numbered protocol phases, a gold-filter table, and executable handler code with no explanations of concepts Claude already knows. Not 5 because of minor trimmable content: the "Contract" and "Output Format" sections exist purely "for the conformance test", the safety-gate refusal is repeated across three sections, and an inline version reference ("the db_tracked / db_only allow-list pattern from v0.22.11 storage tiering") is time-sensitive information not placed in a deprecated/old-patterns section. | 4 / 5 |
Actionability | Provides copy-paste-ready code for the common cases — the Python `mailbox.mbox` walker, the zip/XML `.docx` extraction one-liner, `antiword`/`catdoc` for legacy `.doc`, PST magic-byte validation plus `readpst` — and complete brain-page and manifest templates, with specific error-recovery commands ("poll `gbrain write-request <request_id>`", re-read and merge on `revision_conflict`). Not 5 because two of the five advertised source types, Dropbox and Backblaze B2, get no concrete connection or listing commands at all. | 4 / 5 |
Workflow Clarity | Three phases (Inventory → Crawl → Ingest) are explicitly sequenced with validation checkpoints throughout: the scan_paths safety gate as mandatory step 1 of Phase 1 with exit-on-failure, PST validation before parsing, manifest status updates after every interaction, a "Never re-show" manifest check, and explicit error-recovery feedback loops in "When it fails" (poll write-requests, re-read and merge on revision_conflict, never re-file). The Anti-Patterns section adds a checklist, matching the top anchor for a batch/mutating operation. | 5 / 5 |
Progressive Disclosure | The body is well-sectioned with clear headers, and external references ([conventions/quality.md](../conventions/quality.md), [_brain-filing-rules.md](../_brain-filing-rules.md), [agent-operator-protocol.md](../conventions/agent-operator-protocol.md)) are prominently signaled at the top and one level deep — no nested reference chains. Not 5 because this ~330-line body has no bundle files at all: the 44-line manifest template and the file-type handler details are inlined where dedicated reference files (e.g., references/manifest-template.md, references/handlers.md) would keep SKILL.md a leaner overview. | 4 / 5 |
Total | 17 / 20 Passed |