CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

inngest-flow-control

Configure Inngest flow control for functions. Covers concurrency limits with keys, throttling, rate limiting, debounce, priority, singleton, and event batching.

Quality

83%

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

82%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, example-driven reference: fully executable TypeScript snippets for every flow control mechanism, an excellent quick decision guide, and precise when-to-use guidance throughout. The main improvement areas are trimming minor intro/comment padding and adding a way to verify applied flow control behavior.

Suggestions

Trim the marketing-style opening sentence and code comments that duplicate the prose (e.g. "// Only 5 steps can execute simultaneously") to tighten token efficiency.

Add a brief verification pointer — e.g. how to confirm a limit is active (Inngest dashboard/app function settings) — so users can validate a chosen configuration.

Consider moving the advanced priority ladder and combined-mechanism example into a references/ file to keep SKILL.md a lean overview with clearly signaled one-level-deep references.

DimensionReasoningScore

Conciseness

The body is mostly lean: code, "When to use" notes, and key-difference callouts ("Rate limiting discards events; throttling delays them") with no basic-concept explanations. Minor trimmable padding remains — the marketing-flavored intro ("Master Inngest flow control mechanisms to manage resources, prevent overloading systems...") and code comments that restate the prose — so it fits the 4 anchor rather than the every-token-earns-its-place 5 anchor.

4 / 5

Actionability

Every mechanism (concurrency, keyed concurrency, account-scope limits, throttle, rate limit, debounce, priority, singleton skip/cancel, batching, and a combined example) ships as a complete, copy-paste-ready inngest.createFunction snippet with real option values, covering the common cases per the 5 anchor.

5 / 5

Workflow Clarity

The Quick Decision Guide ("Limit how many run at once" → Concurrency, etc.) plus per-section "When to use" and "Key difference" notes make the selection-and-apply workflow unambiguous. It is not 5 because at ~330 lines it is not a simple <50-line skill, and there are no checkpoints for verifying that a chosen configuration behaves as intended (e.g. no pointer to observing limits in the Inngest dashboard).

4 / 5

Progressive Disclosure

Sections are cleanly organized per mechanism with a decision guide up front, no buried or nested references, and the single-file layout is reasonable for this scope. It falls short of the 5 anchor (clear overview with well-signaled one-level-deep references) because everything — including the advanced priority example and the combined example — is inlined in one 334-line file with no split of advanced detail into a reference file.

4 / 5

Total

17

/

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 highly specific, well-scoped description that comprehensively enumerates the domain's capabilities and is unlikely to trigger for the wrong skill. Its one clear weakness is the absence of any explicit "Use when..." trigger guidance, which caps completeness and slightly limits natural-trigger coverage.

Suggestions

Add an explicit trigger clause, e.g. "Use when configuring or debugging Inngest function limits, queueing behavior, or event processing behavior, or when the user mentions Inngest, concurrency, throttling, rate limits, or debouncing."

Include one or two natural phrasing synonyms beyond the canonical mechanism names, such as "throttle" or "limit simultaneous/parallel runs", to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

"Configure Inngest flow control for functions. Covers concurrency limits with keys, throttling, rate limiting, debounce, priority, singleton, and event batching" lists seven concrete, named capabilities covering the full mechanism set of the domain, matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.

5 / 5

Completeness

The "what" is clear and comprehensive (configure these seven flow control mechanisms), but there is no "Use when..." clause or equivalent explicit trigger guidance; per the judging guidelines this caps completeness at 3. It is not 2 because the "what" is specific, not vague.

3 / 5

Trigger Term Quality

The mechanism names ("concurrency", "throttling", "rate limiting", "debounce", "singleton", "batching", "priority") are exactly the keywords a user needing this skill would say, giving good coverage. It falls short of the 5 anchor because no synonyms or phrasings beyond the canonical mechanism names are included (e.g. "throttle", "limit parallelism", "run only once").

4 / 5

Distinctiveness Conflict Risk

"Inngest" names a specific platform and the enumerated mechanisms form a clear niche with distinct triggers, giving minimal conflict risk with other skills, which matches the 5 anchor exactly.

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-flow-control/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.