inngest

You are an Inngest expert who builds reliable background processing without managing infrastructure. You understand that serverless doesn't mean you can't have durable, long-running workflows - it means you don't manage the workers.

Quality

27%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/inngest/SKILL.md

Quality

Content

18%Scale 1-5

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

This skill is essentially a skeleton or outline with no substantive content. It has section headers for patterns and anti-patterns but provides zero executable code, no concrete examples, no workflow steps, and no actionable guidance for using Inngest. The introductory philosophy text consumes tokens without teaching Claude anything it doesn't already know.

Suggestions

Add complete, executable code examples for each pattern (Basic Function Setup, Multi-Step Workflow, Scheduled Functions) showing actual Inngest function definitions with typed events, step usage, and error handling.

Flesh out the anti-patterns sections with concrete 'wrong way' vs 'right way' code comparisons showing why steps matter, how to handle event payloads, and how to configure concurrency.

Add a clear multi-step workflow example with explicit validation checkpoints, especially for the durable workflow pattern which is Inngest's core value proposition.

Remove the philosophical intro paragraphs and replace with a concise quick-start showing the minimal setup (install, serve, define function, trigger event) with copy-paste ready code.

Dimension	Reasoning	Score
Conciseness	The content includes some unnecessary filler (e.g., the philosophical intro about serverless, 'You've built AI pipelines...') that doesn't add actionable value. The capabilities list is reasonable but the patterns/anti-patterns sections are just headers with one-line descriptions and no actual content, which wastes tokens on structure without substance.	3 / 5
Actionability	There is zero concrete, executable guidance anywhere in this skill. The patterns sections ('Basic Function Setup', 'Multi-Step Workflow', 'Scheduled/Cron Functions') are empty headers with vague one-line descriptions but no code, commands, examples, or specific instructions. The anti-patterns are also just headers with no explanation of what to do instead.	1 / 5
Workflow Clarity	There are no actual workflow steps defined anywhere. The 'Multi-Step Workflow' section promises 'Complex workflow with parallel steps and error handling' but provides absolutely no steps, sequence, or validation checkpoints. The skill is entirely aspirational with no procedural content.	1 / 5
Progressive Disclosure	The document has section headers providing some structure, but there are no bundle files and no references to external files for detailed content. The sections are skeleton placeholders with no actual content to organize. The 'Related Skills' section lists connections but provides no navigation to detailed materials.	2 / 5
	Total	7 / 20 Passed

Description

36%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.

The description reads as a persona/identity statement ('You are an Inngest expert') rather than a functional skill description. It uses second-person voice which is inappropriate, lacks concrete actions, and has no 'when to use' guidance. While it names the specific tool (Inngest), it fails to describe what the skill actually does or when it should be triggered.

Suggestions

Replace the persona framing with concrete actions in third person, e.g., 'Creates Inngest functions, defines event triggers, configures step-based workflows, sets up retries and error handling for durable background jobs.'

Add an explicit 'Use when...' clause with trigger terms, e.g., 'Use when the user asks about Inngest, background jobs, event-driven workflows, durable execution, or serverless task queues.'

Remove the philosophical statement about serverless and replace with specific capabilities and file types/patterns the skill handles.

Dimension	Reasoning	Score
Specificity	Names the domain (Inngest, background processing, serverless workflows) but provides no concrete actions. 'Builds reliable background processing' is vague and doesn't specify what actions the skill performs (e.g., creating step functions, defining event triggers, configuring retries).	2 / 5
Completeness	Has a vague 'what' (builds reliable background processing) but completely lacks a 'when' clause. There is no explicit guidance on when Claude should select this skill. The description reads more like a persona statement than a skill description.	2 / 5
Trigger Term Quality	Includes some relevant keywords like 'Inngest', 'background processing', 'serverless', 'durable', 'long-running workflows', and 'workers'. However, it misses natural user phrases like 'event-driven', 'queue', 'cron', 'step functions', 'retries', or specific Inngest concepts users would mention.	3 / 5
Distinctiveness Conflict Risk	The mention of 'Inngest' specifically provides some distinctiveness, but 'background processing', 'serverless', and 'durable workflows' could overlap with skills for other tools like Temporal, AWS Step Functions, or Bull/BullMQ. The lack of specific actions increases overlap risk.	3 / 5
	Total	10 / 20 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/inngest/SKILL.md
Commit: 57c135b

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.