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 skill body is a hollow skeleton: sensible section headings with almost no content behind them. No code, commands, or step sequences are provided anywhere, the anti-patterns are empty labels, and one list is visibly truncated, leaving the skill unable to actually guide implementation of Inngest functions.
Suggestions
Add executable code examples for the three named patterns (e.g., a complete typed Next.js Inngest function with CreateStep usage, a multi-step workflow with Step.run and error handling, and a cron config), replacing the one-line topic labels.
Fill in the Anti-Patterns sections with the concrete risk and the correct alternative (e.g., why not using steps loses checkpointing, payload size limits and passing IDs instead, concurrency key configuration).
Complete or remove the truncated "core philosophy" list and replace the filler "When to Use" section with genuine applicability guidance or trigger conditions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short and avoids tutorial-style over-explanation, but the opening persona paragraph repeats the frontmatter description verbatim and the "When to Use" section is pure filler ("This skill is applicable to execute the workflow or actions described in the overview"), so several tokens earn nothing. Not 4 because these unnecessary sections could be trimmed or replaced with substance. | 3 / 5 |
Actionability | There is zero executable guidance anywhere: the Patterns section only labels topics ("Inngest function with typed events in Next.js", "Complex workflow with parallel steps and error handling") with no code, commands, or specifics, and the Anti-Patterns headers ("❌ Not Using Steps", "❌ Huge Event Payloads") have no content explaining what to do instead. This matches the anchor 'only describes rather than instructs'. | 1 / 5 |
Workflow Clarity | No sequence of steps exists for any task; the "Your core philosophy" list is literally truncated after "1. Event", and none of the named patterns (setup, multi-step workflow, cron) has any procedure. This matches the anchor 'steps missing or incoherent; no sequence; no validation', and the skeleton would not support error-recovery checkpoints. | 1 / 5 |
Progressive Disclosure | No bundle files exist and no external references are cited, so there is no nesting or buried-reference problem, and section headers are sensible. However, the structure is hollow: the pattern and anti-pattern detail that should be inline or in referenced files is simply absent, and the "When to Use" section is filler, so it does not meet the well-organized standard needed for a 5 on a short single-file skill. | 3 / 5 |
Total | 8 / 20 Passed |