Content
85%Reviews 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 debugging protocol with clear phased workflows, verification gates, and codebase-specific guidance. The lone weakness is mild verbosity from coaching aphorisms that don't strictly earn their tokens.
Suggestions
Tighten conciseness by trimming coaching aphorisms ('If you can't reproduce, you don't understand it', 'Knowledge decays fast') and the quoted 'Red flags' lines down to imperative directives.
Condense the motivational framing in Phase 3 ('No random guess-and-check', 'Let me just try changing X...') into a single concise 'avoid uncontrolled experimentation' rule.
Move the standalone verification-subagent prompt out of inline prose into a clearly delimited, copy-paste block to reduce surrounding explanatory tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean and codebase-specific (file paths, uv bisect commands, pitfalls, checklists), but it is padded with coaching aphorisms ('If you can't reproduce, you don't understand it', 'Knowledge decays fast') and the quoted 'Red flags' lines that could be tightened. | 2 / 3 |
Actionability | It provides concrete commands ('git log --oneline -10', 'pytest tests/<module>/', '/veomni-review', 'make quality'), an executable uv bisect block, specific paths like 'veomni/distributed/parallel_plan.py', and a copy-paste verification-subagent prompt template. | 3 / 3 |
Workflow Clarity | A clear Quick Path plus Full Protocol Phase 1-5 with TodoWrite tracking, explicit verification gates, regression checks, domain checklists, and feedback loops (15-min escalation, three-strike, hypothesis retry); validation is present for risky fixes so it is not capped at 2. | 3 / 3 |
Progressive Disclosure | No bundle files exist; the single self-contained SKILL.md opens with a routing table and uses well-signaled sections with no nested-reference chains, which is appropriate organization for this debugging protocol. | 3 / 3 |
Total | 11 / 12 Passed |