Content
85%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 an unusually actionable, well-sequenced seven-phase workflow with explicit human-approval gates and strong error handling — top marks for actionability and workflow clarity. The weaknesses are inlined detail that belongs in reference files and a referenced investigator prompt file that is missing from the bundle entirely, which caps progressive disclosure at 3.
Suggestions
Ship the referenced prompts/investigator.md file in the skill bundle (or inline its prompt) — Phase 2 depends on it, and it is currently absent, breaking the workflow at runtime.
Move the diagnosis-bundle JSON schema, the per-fix-type recovery playbook, and the issue body template into a reference file (e.g., references/diagnosis-format.md), keeping SKILL.md as a lean phase overview.
Trim rationale asides like "(materialized views, numbered MV shards, and copy targets — they do not receive direct ingestion)" to keep only the exclusion rules, since Claude does not need the why to execute the filter.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and operational with essentially no explanation of concepts Claude already knows — every line carries repo-specific facts (exclusion patterns, gh project field choreography, 1-month quarantine retention). It falls short of level 5 because the ~25-line recovery-path block inside the Phase 3 report template and the full 30-line diagnosis-bundle JSON schema are inlined where a tighter summary or reference file would do. It is clearly above level 3, which expects unnecessary explanation. | 4 / 5 |
Actionability | Guidance is copy-paste executable throughout: exact SQL ("SELECT count() AS live_quarantined, max(insertion_date)"), exact exclusion regexes, gh issue/project commands with --json/--jq filters, a complete JSON issue payload, and a concrete git worktree fallback including the .git/info/exclude trick. Specific examples cover the common cases, matching the level-5 anchor; only placeholders like {DS_NAME} remain, which are parameterized by design. | 5 / 5 |
Workflow Clarity | Seven phases are clearly sequenced with two explicit blocking validation checkpoints ("Do not proceed to Phase 5 until the user responds"; same before Phase 7), plus race-condition handling for null dominant_error, fingerprint-based duplicate-issue prevention, per-failure error handling, and an explicit stop condition when no live rows remain. This matches the level-5 anchor (explicit validation steps and feedback loops for error recovery); the approval gates validate the batch GitHub/worktree operations. | 5 / 5 |
Progressive Disclosure | The body references ".claude/skills/tb-quarantine-triage/prompts/investigator.md", but no prompts/ directory or any other bundle file exists — a broken in-bundle reference. Additionally, content that clearly belongs in a separate file (the 30-line diagnosis JSON schema, the recovery-path playbook, the issue body template) is inlined in a 330-line SKILL.md. This matches the level-3 anchor (content that should be separate is inline; references not verifiable) rather than level 4, which expects references to be mostly clear and appropriately placed. | 3 / 5 |
Total | 17 / 20 Passed |