CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

inngest-steps

Use Inngest step methods to build durable workflows. Covers step.run, step.sleep, step.waitForEvent, step.waitForSignal, step.sendEvent, step.invoke, step.ai, and patterns for loops and parallel execution.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/inngest-steps/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, example-rich reference that teaches Inngest's step model effectively through executable code and gotchas, and it is notably lean for its coverage. Its weaknesses are the total absence of validation/verification guidance for its batch and parallel patterns, and a monolithic structure whose only external reference is broken. Fixing the expressions.md reference and adding error/timeout checks to the pattern examples would lift the two lowest dimensions.

Suggestions

Add validation checkpoints to the batch/parallel patterns: check for null waitForEvent returns is covered, but extend it to verifying step outputs before combining chunk results and handling partial failures in Promise.all.

Fix the dangling reference: either create references/expressions.md at the linked path or remove/repair the link, and point the "inngest-flow-control" mention at its actual file path.

Consider moving the per-method API detail into a reference file so SKILL.md stays an overview, which would also let you demonstrate step.ai properly.

DimensionReasoningScore

Conciseness

The body is code-first and assumes competence — "Each step is a separate HTTP request that can be independently retried and monitored" plus tight examples, with no explanation of concepts Claude already knows. Minor trimming opportunities exist: DO/DON'T lists restate nearby prose, emoji labels add tokens, and the "Remember: Steps make your functions durable... Embrace them!" closer earns nothing. Not 3, since padding is minor rather than a pattern.

4 / 5

Actionability

Nearly every section ships concrete, executable TypeScript (step.run, waitForEvent with match/if, Promise.all parallelism, pagination loop), matching "concrete code with minor gaps". It falls short of 5 because `chunkArray` is an undefined helper, sending signals is only sketched as a comment ("// POST /v1/events with signal matching taskId"), and step.ai is claimed in the description and use cases but never demonstrated.

4 / 5

Workflow Clarity

Sections are clearly organized with WRONG/CORRECT contrasts and a gotchas recap, but no validation or verification checkpoints appear anywhere. The Patterns section involves batch operations (pagination loops, chunking, parallel Promise.all), and the rubric states missing validation in batch-operation workflows caps workflow clarity at 3 — it cannot reach 4 despite good sequencing.

3 / 5

Progressive Disclosure

Everything lives in one ~340-line SKILL.md that reads partly as an inline API reference, and the single reference link "See [Expression Syntax Reference](../references/expressions.md)" points to a nonexistent path (no references/ directory exists in the bundle). "See inngest-flow-control" is likewise invoked without a path. This is "some structure, references present but not clearly signaled / content that should be separate is inline"; it does not reach 4 because a referenced file is dangling and the flow-control pointer is unresolvable.

3 / 5

Total

14

/

20

Passed

Description

75%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly conveys what the skill covers through enumerated Inngest step methods. Its main weakness is the complete absence of "when to use" trigger guidance, which both caps completeness and slightly weakens natural discoverability. Adding a "Use when..." clause with a few synonyms would raise it substantially.

Suggestions

Add an explicit trigger clause, e.g., "Use when building or debugging Inngest functions, durable workflows, or retryable multi-step pipelines."

Include natural synonyms users might say, such as retries, fan-out, background jobs, or human-in-the-loop waits, alongside the method names.

Either add a step.ai usage note in the description or drop it from the list, since it is named but never demonstrated in the body.

DimensionReasoningScore

Specificity

The description enumerates concrete actions for the domain: "Covers step.run, step.sleep, step.waitForEvent, step.waitForSignal, step.sendEvent, step.invoke, step.ai, and patterns for loops and parallel execution" — multiple specific capabilities with comprehensive coverage, matching the top anchor. It clearly exceeds the score-4 anchor, which allows minor gaps in coverage.

5 / 5

Completeness

It has a clear "what" ("Use Inngest step methods to build durable workflows" plus the enumerated methods) but no "Use when..." clause or equivalent trigger guidance, which the judging guidelines explicitly cap at 3. It does not reach 4 because the "when" is entirely absent rather than present-but-imprecise.

3 / 5

Trigger Term Quality

Good natural keyword coverage: "Inngest", "durable workflows", "step.run", "loops", "parallel execution" are terms a user working with Inngest would naturally say. It falls short of the score-5 anchor because no synonyms or common variations are included (e.g., retries, fan-out, background jobs, durable functions).

4 / 5

Distinctiveness Conflict Risk

The description names a specific vendor and API surface ("Inngest step methods"), creating a clear niche with distinct triggers and minimal risk of firing for the wrong skill. It is far from the overlapping examples at scores 2–3.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

joelhooks/joelclaw

Path

skills/inngest-steps/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.