Content
63%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 well-structured, highly actionable protocol with a genuinely enforced safety gate and executable handlers for common file types. The main costs are repetition of the safety contract, meta-sections written for a conformance test rather than the model, and zero use of reference files for the long templates and handler details.
Suggestions
State the safety gate once (in its dedicated section) and have Phase 1 and the Anti-Patterns reference it in a single line instead of restating the full rationale each time.
Move the manifest template and the file-type handler details (mbox/docx/pst snippets) into references/ files (e.g. references/manifest-template.md, references/file-handlers.md), keeping a one-line pointer in SKILL.md.
Cut or merge the 'Contract' and 'Output Format' trailing sections, which self-describe as existing 'for the conformance test' — their guarantees are already documented in the body sections they point to.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly dense and useful (gold-filter table, lean code handlers, templates), but the safety gate is restated four times (description framing, 'Safety gate (REQUIRED, no exceptions)', Phase 1 step 1, and the Anti-Patterns entry), and the Contract/Output Format sections openly exist 'for the conformance test' rather than for the model. Not 2 because there is no conceptual over-explanation of things Claude already knows. | 3 / 5 |
Actionability | Provides executable guidance: a working mailbox.mbox Python snippet, a docx zip/XML extraction one-liner, PST magic-byte validation ('print('Valid PST' if f.read(4) == b'!BDN' ...')', exact refusal text, YAML config, and full brain-page/manifest templates. Not 5 because Dropbox, B2, and Gmail sources are declared supported types with no concrete access guidance, unlike the local file types. | 4 / 5 |
Workflow Clarity | Three phases are clearly sequenced with real checkpoints: 'Confirm scan_paths is set (safety gate). Exit if not', 'Never re-show — check the manifest before presenting anything', and 'Validate first; many PSTs are null bytes', so the batch-operation cap does not apply. Not 5 because there is no post-ingest verification of created brain pages and no error-recovery loop (e.g. what to do on unreadable files mid-crawl). | 4 / 5 |
Progressive Disclosure | A single monolithic ~300-line file with no references/ or scripts/ bundle; the file-type handlers and the ~45-line manifest template are inlined where separate reference files would fit. Sections are well-organized and external convention links (../conventions/quality.md, ../_brain-filing-rules.md) are clearly signaled at the top, which keeps it above 2, but content that should be separate is inline, matching anchor 3. | 3 / 5 |
Total | 14 / 20 Passed |