Content
88%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 lean, well-sequenced 7-phase pipeline with strong validation culture (integrity rule, dedup checkpoint, explicit error recovery) that keeps every section operational. The main gaps are minor: a few vague pointers ('enrichment service', 'Brain first'), no example recipe YAML inline, and inconsistent reference path notation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and operational throughout — specific paths ('~/.gbrain/recipes/{name}.yaml'), tool names, dedup tolerances, and a concrete output table — with zero explanation of concepts Claude already knows and no padded sections. The two-line intro after the H1 mirrors the frontmatter description, but that is standard standalone structure rather than over-explanation, so this matches 'Lean and efficient; every token earns its place' rather than 4. | 5 / 5 |
Actionability | Guidance is concrete and executable for an instruction-only skill: exact tool names (put_raw_data, file_upload, gbrain write-request <request_id>), exact recipe paths, deterministic dedup rules with tolerances, and a copy-ready output markdown table. It is not 5 because a few steps stay high-level — 'Brain first', 'Uses enrichment service for entity pages', and the recipe YAML field structure is never shown, leaving minor gaps. | 4 / 5 |
Workflow Clarity | Seven clearly sequenced phases with explicit validation for the batch operations: the numbered EXTRACTION INTEGRITY RULE ('re-read from saved files', 'Never trust LLM working memory'), a dedup checkpoint before tracker writes with exact/fuzzy/conflict handling, a fail-improve loop logging LLM fallbacks, and a dedicated error-recovery section with per-error recovery steps. This matches 'Clear sequence with explicit validation steps; feedback loops for error recovery' — the batch-operation cap does not apply since validation is present. | 5 / 5 |
Progressive Disclosure | The single-file body (~120 lines) is well organized into clearly signaled sections, and external references (recipes directory, agent-operator-protocol.md, conventions/quality.md) are one level deep and explicitly pathed. It is not 5 because no bundle reference files exist at all — recipe format details and the conventions material could be split out — and path notation is inconsistent ('../conventions/agent-operator-protocol.md' vs 'skills/conventions/quality.md'). It is not 3 since nothing inlined clearly belongs in a separate file. | 4 / 5 |
Total | 18 / 20 Passed |