CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

inngest-events

Design and send Inngest events. Covers event schema and payload format, naming conventions, IDs for idempotency, the ts param, fan-out patterns, and system events like inngest/function.failed.

Quality

76%

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

Quality

Content

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

The content is highly actionable, with complete, copy-paste-ready TypeScript for every topic, and decision guidance is explicit. It is weakened by padding in the fan-out section, a monolithic 470-line inline structure with no reference files, and a dangling cross-skill reference.

Suggestions

Split advanced material (fan-out orchestration with waitForEvent, system-event handling) into a references/ file and keep SKILL.md as a concise overview with clearly signaled links.

Trim the fan-out example to one representative function plus a note that multiple functions subscribe to the same event, and drop the generic "Fan-Out Benefits" and intro paragraphs.

Fix or inline the "../references/expressions.md" pointer — it points outside the skill bundle and the file does not exist in this skill's references directory.

DimensionReasoningScore

Conciseness

The body is mostly efficient — code is Inngest-specific and non-obvious — but includes unnecessary padding: the intro paragraph restates the description, the "Fan-Out Benefits" bullets explain generic concepts, and three near-identical fan-out function definitions (sendWelcomeEmail, createTrialSubscription, addToCrm) repeat where one plus a note would suffice. This fits "mostly efficient but includes some unnecessary explanation", not the minor-trimming level 4.

3 / 5

Actionability

Every section contains complete, executable TypeScript covering the common cases: single and batch sends, sending from functions via step.sendEvent, ID-based deduplication, ts scheduling, fan-out with step.waitForEvent, and system-event handling. This matches the fully executable, copy-paste-ready anchor.

5 / 5

Workflow Clarity

As a topical reference skill, it provides explicit "When to use" decision guidance for IDs, ts, and fan-out, and sections are clearly organized. It fits level 4 (clear organization, most decision checkpoints present) but not 5 because there are no verification or error-recovery loops (e.g., confirming events were received) anywhere.

4 / 5

Progressive Disclosure

Section headers are clear, but all ~470 lines live inline in SKILL.md with advanced material (fan-out orchestration, system events) that clearly belongs in reference files, and the cited "../references/expressions.md" points outside the bundle with no references directory present. This fits level 3: some structure, but content that should be separate is inline and references are not clearly signaled.

3 / 5

Total

15

/

20

Passed

Description

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

The description is specific and comprehensive about what the skill covers, with a clear Inngest niche and good keyword coverage. Its main weakness is the complete absence of a "Use when..." trigger clause, which caps completeness and leaves invocation conditions implicit.

Suggestions

Add an explicit trigger clause, e.g. "Use when sending or triggering Inngest events, designing event schemas, or setting up event-driven functions."

Include more natural user phrasings and synonyms such as "event-driven", "event triggers", or "background jobs" to broaden keyword coverage.

Sharpen the boundary against sibling skills (e.g. note that function/step internals belong to inngest-steps) to reduce overlap risk.

DimensionReasoningScore

Specificity

"Design and send Inngest events" plus an enumerated list of concrete capability areas ("event schema and payload format, naming conventions, IDs for idempotency, the ts param, fan-out patterns, and system events like inngest/function.failed") matches the comprehensive multiple-concrete-actions anchor. Coverage is thorough across the domain, so it does not fit the minor-gaps level 4 anchor.

5 / 5

Completeness

The "what" is clear ("Design and send Inngest events. Covers event schema and payload format..."), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It does not reach level 4 because "when" is entirely absent, not merely imprecise.

3 / 5

Trigger Term Quality

Natural terms like "Inngest events", "send", "idempotency", "fan-out", and "system events" are present, but common variations users might say ("event triggers", "event-driven", "background jobs", "event payload") are missing. Good keyword coverage with a few natural terms missing fits level 4, below the synonym-comprehensive level 5.

4 / 5

Distinctiveness Conflict Risk

"Inngest events" is a clear niche with distinct platform-specific triggers, but the description's scope (fan-out patterns, function behavior) overlaps with closely related sibling Inngest skills (inngest-steps, inngest-durable-functions referenced in the body). Mostly distinct with minor overlap risk fits level 4, short of the minimal-conflict level 5.

4 / 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: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

joelhooks/joelclaw

Path

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