Content
22%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 a skeleton: pattern and anti-pattern sections are headings with no code or corrective guidance, and the sharp-edges table's solutions are truncated comment fragments. The sharp-edges issues themselves are valuable, but nothing in the body tells Claude how to actually set up, write, or verify a Trigger.dev task.
Suggestions
Add complete, executable code to the three Pattern sections (e.g. a trigger.config.ts plus a tasks/file.ts example with a real task definition, an OpenAI integration task with retry config, and a scheduled task with a cron expression).
Fill the Anti-Patterns sections with what to do instead (e.g. how to split a monolithic task into subtasks) and complete the sharp-edges Solution column with actual commands/snippets instead of truncated comments like '# Configure explicit timeouts:'.
Add a setup-to-deploy workflow with validation checkpoints, e.g. init the project -> write tasks -> `npx trigger.dev@latest dev` to verify locally -> deploy -> confirm the run succeeded in the dashboard/logs, which also addresses the batch/retry duplicate-side-effect risks.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly terse (headers, a table, lists) but includes unnecessary padding: two persona paragraphs ('You are a Trigger.dev expert... You've built AI pipelines that process for minutes...') and the circular filler section 'This skill is applicable to execute the workflow or actions described in the overview.' This matches anchor 3 'mostly efficient but includes some unnecessary explanation or could be tightened'. It is not 4 because the persona block is more than minor over-explanation, and not 2 because there are no lengthy concept explanations and total length is modest. | 3 / 5 |
Actionability | There is no executable code or command anywhere in the body. The Patterns sections only describe ('Setting up Trigger.dev in a Next.js project', 'Tasks that run on a schedule') without instructing, the Anti-Patterns are bare headings with no corrective guidance, and the sharp-edges 'Solution' column contains truncated comment fragments ('# Configure explicit timeouts:', '# Always use plain objects:') with no actual steps. This matches anchor 1 'no concrete code or commands; only describes rather than instructs'. It is not 2 because even the high-level hints in the table are incomplete fragments, and the core instructional sections are empty. | 1 / 5 |
Workflow Clarity | No multi-step sequence exists: the 'Basic Task Setup' pattern gives no setup steps, there is no deploy or verification flow, and no validation checkpoints despite the body itself flagging risky operations (batch processing, retries causing duplicate side effects). This matches anchor 1 'steps missing or incoherent; no sequence; no validation for risky operations'. It is not 2 because even a rough implicit sequence of setup-to-run is absent. | 1 / 5 |
Progressive Disclosure | No bundle files exist (no references/, scripts/, or assets/), and the short body is appropriately inline with clear section headers (Capabilities, Patterns, Anti-Patterns, Sharp Edges, Related Skills). However, the Patterns and Anti-Patterns sections are empty stubs that promise content that is not there, and the 'When to Use' section is circular filler, so organization is incomplete — matching anchor 3 'some structure but could be better organized'. It is not 4 because empty stub sections and filler reflect more than minor organization gaps, and the under-50-line exception for a 5 does not apply (the body is ~62 lines and not well-organized). | 3 / 5 |
Total | 8 / 20 Passed |