Content
18%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 well-sectioned but almost entirely non-instructional: it relies on persona framing and one-line pattern descriptions with no code, commands, or sequenced workflow. It functions as an outline rather than actionable guidance.
Suggestions
Replace the persona intro and 'core philosophy' filler with concrete code: a basic Queue/Worker setup, a delayed-job example, and a flow-producer example.
Expand each Patterns subsection into executable steps with configuration values (concurrency, removeOnComplete, attempts/backoff) rather than single descriptive sentences.
Add validation/verification guidance for job operations (inspecting failed jobs, retry/backoff behavior, DLQ handling) so the workflow includes checkpoints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The persona intro ('processed billions of jobs', 'queues... decouple services, smooth traffic spikes') explains queue concepts Claude already knows, and 'Your core philosophy:' dangles with no content, matching the noticeably-verbose/padded anchor rather than the mostly-efficient 3. | 2 / 5 |
Actionability | There is no code, command, or executable guidance anywhere; sections like 'Production-ready BullMQ queue with proper configuration' only describe, fitting the entirely-vague/no-instruction anchor. | 1 / 5 |
Workflow Clarity | No multi-step process is sequenced and no validation checkpoints exist for batch/job operations; the Patterns section is only titles with one-line descriptions, matching the steps-missing anchor. | 1 / 5 |
Progressive Disclosure | The file is under 50 lines with no external references needed and is organized into labeled sections (Capabilities, Patterns, Anti-Patterns, Related Skills); minor gaps (a redundant 'When to Use' and dangling 'core philosophy') keep it at 4 rather than 5. | 4 / 5 |
Total | 8 / 20 Passed |