CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

inngest-setup

Set up Inngest in a TypeScript project. Install the SDK, create a client, configure environment variables, serve endpoints or connect as a worker, and run the local dev server.

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 highly actionable, well-sequenced setup guide with excellent executable examples, weakened by duplicated environment-variable content, no explicit validation checkpoint, and a monolithic single-file structure that should split framework-specific and advanced content into reference files.

Suggestions

Move the framework-specific serve variants (Fastify, Cloudflare, Lambda) and the connect-mode details into a references/ file, keeping SKILL.md to the core setup flow.

Consolidate the duplicate environment-variable sections (Step 2 and 'Environment-Specific Setup') into one place to save tokens.

Add an explicit validation step after starting the dev server, e.g. 'Open http://localhost:8288 and confirm your app and functions appear', to close the workflow feedback loop.

DimensionReasoningScore

Conciseness

The body is code-first and efficient, but the intro paragraph repeats the frontmatter description, environment variables are explained twice (Step 2 and the 'Environment-Specific Setup' section), and the typed-events section drifts into the inngest-events skill's territory.

4 / 5

Actionability

Fully executable, copy-paste-ready code and commands throughout: client creation, EventSchemas, serve examples for Next.js App Router, Pages Router, and Express, connect worker setup, CLI commands, and inngest.json config covering the common cases.

5 / 5

Workflow Clarity

Steps 1-6 form a clear numbered sequence with an explicit Mode A/B decision point, and 'Common Issues & Solutions' provides recovery guidance, but there is no explicit verification checkpoint such as confirming the app appears in the dev server dashboard.

4 / 5

Progressive Disclosure

No reference files exist; all ~310 lines live in SKILL.md with framework serve variants, connect mode, and typed-events detail inlined — content that clearly belongs in separate reference files. Sections are well-headed and navigable, keeping this above 2.

3 / 5

Total

16

/

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 specific, well-scoped description with comprehensive concrete actions and strong distinctiveness, held back only by the complete absence of a 'when to use' trigger clause and thin synonym coverage.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when setting up Inngest in a TypeScript project, adding Inngest to a new or existing app, or when the user mentions Inngest, background jobs, or durable functions.'

Include a few natural synonyms or related trigger phrases users would actually say (e.g. 'event-driven functions', 'job queue', 'Inngest dev server') to broaden keyword coverage.

DimensionReasoningScore

Specificity

The description lists five concrete actions — 'Install the SDK, create a client, configure environment variables, serve endpoints or connect as a worker, and run the local dev server' — which comprehensively covers the setup lifecycle with no vague language.

5 / 5

Completeness

The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Natural phrases like 'Set up Inngest', 'TypeScript project', and 'local dev server' are present, but coverage relies mostly on the product name and misses common variations users might say such as 'background jobs', 'durable functions', or 'event-driven'.

4 / 5

Distinctiveness Conflict Risk

'Inngest' is a distinct product name with a well-defined niche (TypeScript SDK setup), so the description is clearly distinguishable and unlikely to trigger for the wrong skill.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

joelhooks/joelclaw

Path

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