Content
35%Weight 40%Scale 1-3Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a generic template: well-organized and brief but lacking any concrete, executable guidance, with validation only implicit and a referenced playbook file that is missing from the bundle.
Suggestions
Replace abstract instructions ('Apply relevant best practices') with concrete, service-specific examples (e.g., Sentry DSN config, a structured logging JSON snippet, an alert-rule YAML).
Add explicit validation/feedback checkpoints to the workflow (e.g., 'trigger a test error and confirm it appears in the dashboard before proceeding').
Either create the referenced 'resources/implementation-playbook.md' or remove the broken reference so progressive disclosure actually resolves.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short and sectioned but pads with generic restating of the description ('You are an error tracking and observability expert...') and filler like 'Focus on real-time error detection...' that could be tightened. | 2 / 3 |
Actionability | Instructions are abstract — 'Apply relevant best practices and validate outcomes', 'Provide actionable steps and verification' — with no concrete commands, code, service-specific config, or copy-paste guidance, matching the vague/abstract anchor. | 1 / 3 |
Workflow Clarity | A sequence is present (clarify goals, apply practices, verify) and an 8-step Output Format is listed, but validation checkpoints and feedback loops are only implicit and generic rather than explicit. | 2 / 3 |
Progressive Disclosure | Sections are organized and a reference is signaled, but it points to 'resources/implementation-playbook.md' which does not exist in the bundle, so the one-level-deep reference leads nowhere. | 2 / 3 |
Total | 7 / 12 Passed |