CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

inngest-durable-functions

Create and configure Inngest durable functions. Covers triggers (events, cron, invoke), step execution and memoization, idempotency, cancellation, error handling, retries, logging, and observability.

Quality

72%

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-durable-functions/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 strong, actionable pattern reference with executable TypeScript examples and crisp always/never rules, undermined primarily by a broken progressive-disclosure layer: all referenced files are missing from the bundle, and the inlined detail that should live in them makes the skill heavier than its structure promises. Minor code-syntax errors in the cron section slightly reduce copy-paste reliability.

Suggestions

Ship the referenced files (references/step-execution.md, error-handling.md, observability.md, checkpointing.md) or remove the dead links; fix the "../references/expressions.md" path to stay inside the skill directory.

Move the deep-dive sections (cancellation patterns, logging setup, checkpointing config) into the reference files so SKILL.md is a lean overview, matching the Next Steps promises.

Fix the cron trigger snippets' syntax errors (semicolons inside object literals, mismatched brackets) so every code block is copy-paste executable.

DimensionReasoningScore

Conciseness

The body is dense and example-driven with almost no padding of concepts Claude already knows; Inngest-specific semantics (memoization, step counters, attempt semantics) genuinely add information. Minor trimmable material exists: the "Core Concepts" bullet list partially duplicates "When to Use Steps", and "Common Mistakes to Avoid" recaps points already made with code. Not 5 because of those few redundant passages; not 3 because there is no noticeable over-explanation.

4 / 5

Actionability

Mostly copy-paste-ready TypeScript covering creation, triggers, idempotency, cancellation, NonRetriableError/RetryAfterError, logging, and checkpointing, with good/bad contrasts. Not a 5 because of real minor gaps: the cron trigger snippets contain syntax errors ("{ cron: \"0 */6 * * *\"; }" uses a semicolon inside an object literal and the combined example mixes "[" and "{"), and a few snippets are fragments ("/* ... */" bodies) or reference undefined helpers without noting them.

4 / 5

Workflow Clarity

This is a pattern-reference skill, and it sequences guidance logically (limits → when to use steps → creation → triggers → idempotency → cancellation → errors → logging → performance) with explicit decision rules ("Always wrap in step.run()" / "Never wrap") and error-recovery patterns (try/catch fallback). Not a 5 because there is no verification step for the resulting functions (e.g., testing with `inngest dev` or validating trigger configs) and no guidance on ordering concerns when mixing steps and conditionals.

4 / 5

Progressive Disclosure

The body points to "references/step-execution.md", "references/error-handling.md", "references/observability.md", "references/checkpointing.md", and "../references/expressions.md", but no references/ directory exists anywhere in the bundle — every file reference is dead, and the expressions.md path even escapes the skill directory. Per the guideline to score against the actual bundle structure, the claimed progressive disclosure is broken, and detailed material (cancellation patterns, logging setup, checkpointing) that the Next Steps section says lives in reference files is instead inlined. Not a 1 because the SKILL.md itself is well sectioned and the Next Steps list clearly signals where detail should live; not a 3 because signaling to nonexistent files fails the core purpose of progressive disclosure.

2 / 5

Total

14

/

20

Passed

Description

66%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 specific, well-scoped description with good domain keyword coverage, but it omits any explicit "Use when..." trigger guidance, which caps its completeness and weakens its value as a skill-selection signal. Adding a trigger clause would lift most dimensions.

Suggestions

Append an explicit trigger clause, e.g. "Use when creating or debugging Inngest functions, writing step-based workflows, or configuring triggers, retries, or idempotency for Inngest functions."

Add natural user-facing synonyms users might type (e.g., "background jobs", "durable workflows", "step functions") to broaden trigger term coverage.

Clarify the boundary with sibling skills (e.g., note that this is the function-authoring skill, with inngest-steps/inngest-events for deep dives) to reduce overlap risk.

DimensionReasoningScore

Specificity

"Create and configure Inngest durable functions" plus a specific coverage list ("triggers (events, cron, invoke), step execution and memoization, idempotency, cancellation, error handling, retries, logging, and observability") names several concrete, distinct capabilities. Not a 5 because beyond "create" and "configure" the coverage items are topic nouns rather than concrete actions, leaving minor gaps in action phrasing.

4 / 5

Completeness

The "what" is clear ("Create and configure Inngest durable functions" plus the coverage list), but there is no "Use when..." clause or equivalent explicit trigger guidance — the "when" is only weakly implied by the domain name. Per the judging guideline, a missing explicit trigger clause caps completeness at 3; it is not 4 because nothing explicit tells Claude when to load this skill, and not 2 because the "what" half is well defined.

3 / 5

Trigger Term Quality

Strong domain keywords a user would naturally say: "Inngest", "durable functions", "triggers", "events", "cron", "idempotency", "retries", "memoization". Not a 5 because common natural variations users might say are missing (e.g., "background jobs", "workflows", "step functions", "serverless functions").

4 / 5

Distinctiveness Conflict Risk

"Inngest durable functions" is a clear niche with distinct triggers, but the description claims coverage of "step execution and memoization", "events", and "error handling" while sibling skills "inngest-steps" and "inngest-events" exist (referenced in the body), creating minor overlap risk with those closely related skills. Not 5 due to that overlap; not 3 because the niche is well-defined and unlikely to trigger for unrelated skills.

4 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 4 missing, 1 suspicious

Warning

referenced_paths_exist

Referenced path issues: 8 missing

Warning

Total

14

/

16

Passed

Repository

joelhooks/joelclaw

Path

skills/inngest-durable-functions/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.