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 triage router with concrete routing tables, an explicit security validation gate, and properly signaled one-level-deep references. The main weakness is redundancy between the routing tables and the closing checklist.
Suggestions
Collapse the 'Emergency Debugging Checklist' into a pointer to the symptom tables above, or trim it to only the cross-cutting checks not already covered, to remove duplication.
Merge the 'Avoid' and 'Hand Off' sections — both restate the same 'diagnose and route, do not implement' boundary — into a single concise escalation block.
Tighten the 'Still Stuck?' section to a short pointer (consult docs, minimal repro, support email) since the diagnostic steps already live in the per-symptom sections.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Symptom/route tables are token-efficient and domain-specific, but the Emergency Debugging Checklist duplicates the table guidance above and the Avoid/Still Stuck sections restate routing that could be tightened. | 2 / 3 |
Actionability | Concrete symptom→cause→route tables, specific error strings (e.g. "Action 'search' not found", 403 'no access to the analytics dataset'), and exact file references like `core/references/local-development-proxy.md` give directly actionable routing. | 3 / 3 |
Workflow Clarity | Opens with an explicit validation gate ('If ANY checkbox is unchecked, STOP — the bug may be a security incident'), uses numbered diagnostic questions per symptom, and closes with a re-test/escalation path. | 3 / 3 |
Progressive Disclosure | Body is an overview that signals two real one-level-deep bundle files (`references/diagnostic-workflows.md`, `references/error-codes.md`) with clear descriptions, and points to external docs and sibling skills rather than duplicating them. | 3 / 3 |
Total | 11 / 12 Passed |