CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

inngest-middleware

Create and use Inngest middleware for cross-cutting concerns. Covers the middleware lifecycle, creating custom middleware, dependency injection with dependencyInjectionMiddleware, encryption via @inngest/middleware-encryption, Sentry error tracking via @inngest/middleware-sentry, and custom middleware patterns.

Quality

68%

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

Quality

Content

53%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 generally actionable TypeScript guide with good executable examples, undermined by broken structure: every reference link targets files missing from the bundle, a malformed code fence hides the Dependency Injection section, and a TypeScript-only note contradicts a 'Python Implementation' section pointing to a nonexistent reference.

Suggestions

Fix progressive_disclosure first: either add the referenced files (references/dependency-injection.md, references/built-in-middleware.md) or inline their essential content and stop deferring to them.

Repair the stray ```` fence at line 125/163 that renders the '## Dependency Injection' section as code, and remove or rewrite the 'Python Implementation' section, which contradicts the TypeScript-only scope note.

Consolidate the three repeated InngestMiddleware skeletons into one, and either give 'Advanced Patterns' and 'Configuration-Based Middleware' concrete code or cut them, so testing guidance (createMockContext usage) becomes an actual verification checkpoint.

DimensionReasoningScore

Conciseness

The bulk (~200 lines) is concrete, executable TypeScript, but there is real tightening opportunity: the InngestMiddleware skeleton is demonstrated three times (logging, metrics, error-handling examples), and three sections are vague stubs — 'Advanced Patterns' (three one-line bullets), 'Common Use Cases to Implement' (six vague bullets), and 'Configuration-Based Middleware' ('See reference documentation for complete examples' without naming which reference). Not a 2 because the padding is stub sections rather than explanations of concepts Claude already knows.

3 / 5

Actionability

Most guidance is executable: complete custom-middleware code, working DI/encryption/Sentry setup with install commands, and a concrete fail-open error-handling pattern. Falls short of 5 because the metrics example depends on undefined `metrics` and `setupLogger()`, 'Testing Middleware' names utilities (`createMockContext`, `createMockFunction`) with no usage example, and every promised deep-dive ('complete Python examples', 'detailed patterns', 'complete details') points to reference files that do not exist in the bundle.

4 / 5

Workflow Clarity

The document is logically ordered (concept → lifecycle → custom middleware → packages → patterns → best practices) but presents no sequenced procedure: there is no 'identify the lifecycle hook → implement → test' flow, and the Testing section is a single sentence with no validation checkpoint, leaving sequence present but checkpoints implicit.

3 / 5

Progressive Disclosure

The body leans on five clearly-signaled references to `./references/dependency-injection.md` and `./references/built-in-middleware.md`, but the bundle contains no references/ directory at all — every link is broken, so the promised detail (Python examples, DI patterns, package details, configuration-based middleware examples) is unreachable. Compounding this, a stray four-backtick fence (lines 125-163) wraps the '## Dependency Injection' heading and its content inside a code block, breaking document structure. References being nonexistent is a worse structural failure than the buried references of anchor 2, and the inline content alone doesn't recover it.

2 / 5

Total

12

/

20

Passed

Description

70%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 names concrete capabilities and real package names, but it is purely declarative: it never tells Claude when to reach for the skill, which caps completeness at 3 and limits trigger-term coverage.

Suggestions

Append an explicit trigger clause, e.g. 'Use when working with Inngest functions and the user mentions middleware, cross-cutting concerns, dependency injection, encryption, or Sentry integration.'

Include the skill's own primary use-case keywords — logging, tracing, metrics, observability — so natural phrasings like 'add logging to my Inngest functions' match.

Replace the vague 'custom middleware patterns' with a concrete capability (e.g. 'writing custom lifecycle hooks with onFunctionRun/onSendEvent') to sharpen specificity.

DimensionReasoningScore

Specificity

The description names the domain ('Create and use Inngest middleware for cross-cutting concerns') and lists several concrete capabilities with specific API/package names ('dependency injection with dependencyInjectionMiddleware', 'encryption via @inngest/middleware-encryption', 'Sentry error tracking via @inngest/middleware-sentry'). It falls short of a 5 because 'custom middleware patterns' is vague and redundant with 'creating custom middleware', and 'cross-cutting concerns' is abstract filler rather than a concrete action.

4 / 5

Completeness

The 'what' is clearly and thoroughly stated (lifecycle, custom middleware, DI, encryption, Sentry), but the 'when' is entirely absent — there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural terms a user would say are present: 'middleware', 'Inngest', 'dependency injection', 'encryption', 'Sentry', 'error tracking'. Not a 5 because common variations from the skill's own use-case list are missing — 'logging', 'tracing', 'metrics', 'observability' — and no 'Use when...' style trigger phrases appear.

4 / 5

Distinctiveness Conflict Risk

'Inngest middleware' plus named packages (@inngest/middleware-encryption, @inngest/middleware-sentry) occupy a clear niche with minimal overlap risk; generic 'middleware' queries (Express, Redux) would not match because the first sentence anchors on Inngest.

5 / 5

Total

16

/

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: 5 missing

Warning

Total

15

/

16

Passed

Repository

joelhooks/joelclaw

Path

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