Content
77%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 operational skill body: the ten-phase lifecycle is unambiguously sequenced with validation checkpoints, verification-over-trust rules, and error-recovery paths, and the guidance is concrete (real gbrain commands, file layouts, templates). Its two weaknesses are a missing companion file — the manifest pattern that Phases 2/6/9 depend on is referenced but not shipped in the bundle — and noticeable repetition of the trial-before-bulk rule across six sections.
Suggestions
Ship MANIFEST-PATTERN.md in the skill bundle (or inline its essentials: manifest.json item shape and status values, the idempotent-worker contract, and the sharding rule) — the body defers core Phase 2/9 detail to a file that is not present.
State the trial-before-bulk rule once (e.g., in the Contract) and reference it elsewhere; it is currently repeated in the conventions header, Contract, Phase 9, Quality Checklist, Anti-Patterns, and Related skills.
Show a minimal manifest.json example (items array with id/status plus a run-history entry) so Phase 2 and Phase 9 are executable without the missing companion file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and prescriptive, delegates rather than re-derives ('Delegate to skills/skillify/SKILL.md ... Don't re-derive that checklist here'), and assumes competence throughout. The main trimmable redundancy is that the trial-before-bulk rule is restated roughly six times (conventions header, Contract, Phase 9 ladder, Quality Checklist, Anti-Patterns, Related skills). Efficient with minor instances of over-explanation — a 4, not 5 due to that repetition, not 3 since nearly every section is house-specific, non-obvious operational content. | 4 / 5 |
Actionability | Concrete, executable guidance throughout: 'gbrain jobs submit shell --params '{"cmd": ...}'', 'gbrain agent run "Read skills/<pipeline-name>/SKILL.md and process the next 50 pending manifest items"', 'gbrain sync', 'gbrain check-backlinks check', a full YAML page template, the projects/<pipeline-name>/ artifact layout, and named pipeline responsibilities (fetchBatch(offset, limit), transformToPage(raw), ...). Not a 5 because the core artifact — the manifest.json structure — is never shown; its schema, the idempotent-worker contract, and sharding rules are all deferred to MANIFEST-PATTERN.md, which is not present in the bundle. | 4 / 5 |
Workflow Clarity | Ten phases are explicitly sequenced with an ASCII spine, a mandated feedback loop ('Phases 3-5 loop until quality is satisfactory. Don't skip to bulk.'), gated ramping ('10 → 100 → 500 → full — with a quality check between rungs'), artifact-existence verification ('NEVER mark an item done without verifying its output artifact exists on disk'), a 12-item Quality Checklist before declaring done, and a dedicated 'When it fails' error-recovery section with exit codes. This matches the top anchor: clear sequence, explicit validation, feedback loops, and checklists — exactly what a batch-operation skill requires. | 5 / 5 |
Progressive Disclosure | The body is well-sectioned and references are clearly signaled with read-timing ('read before Phase 2'), but the single most load-bearing reference — [MANIFEST-PATTERN.md](MANIFEST-PATTERN.md), cited ~6 times as the substrate for Phases 2, 6, and 9 — does not exist in the bundle (no references/, scripts/, or assets/ directories and no MANIFEST-PATTERN.md beside SKILL.md). Scoring against the actual bundle structure per the rubric guideline, the one-level-deep reference chain is broken for the skill's core mechanism. Not a 4 because a critical reference dangles; not a 2 because the body itself is well organized and nothing bulky is wrongly inlined. | 3 / 5 |
Total | 16 / 20 Passed |