CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

event-gateway

Comprehensive guide to the Hookdeck Event Gateway for receiving, routing, and delivering webhooks and events. Covers setup, connections, authentication, local development, monitoring, and API automation. Use when receiving webhooks, setting up webhook endpoints, testing webhooks locally, configuring webhook relay or event queue, event routing, webhook retry, webhook monitoring, third-party routing, asynchronous APIs, or local webhook development. For provider webhooks (Stripe, Shopify, Chargebee, GitHub, etc.), use together with the matching skill from hookdeck/webhook-skills; do not only parse JSON — use provider SDK verification and event construction (e.g. Stripe constructEvent).

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 body is highly actionable with concrete commands, a clear staged workflow, and well-organized one-level-deep references. Its main weaknesses are systematic repetition of three policy blocks across sections (hurting token efficiency), a few overly dense inline sections that belong in reference files, and example-codebase links that point at paths absent from the bundle.

Suggestions

State each repeated policy once (CLI prerequisite, context verification, provider-webhooks checklist) in its own section and reference it with a single link from the Workflow Stages, Quick Start, and Reference table entries instead of restating it in each place.

Remove or fix the links to examples/express/, examples/nextjs/, and examples/fastapi/ — these directories do not exist in the bundle, yet the body calls them the canonical runnable implementations.

Move the CLI-vs-API-vs-Dashboard decision guide and the Production deployment paragraph into a reference file (e.g. cli-workflows.md or a new interfaces.md), keeping only the short default rule in SKILL.md.

DimensionReasoningScore

Conciseness

Three policies are stated repeatedly: the CLI prerequisite appears in its own section, the Workflow Stages note, the Quick Start prerequisite, and the Reference table; context verification (whoami/confirm) gets a full section, a blockquote, and a table row; the provider-webhooks guidance appears in its own section, stage 02, and the table. This systematic duplication plus the dense Production paragraph goes beyond the "minor instances" of the 4 anchor.

3 / 5

Actionability

Concrete, copy-paste commands abound ("hookdeck ci", "hookdeck listen 3000 <source_name> --path /webhooks", "npx skills add hookdeck/webhook-skills --skill {provider}-webhooks -y -g", "hookdeck gateway connection upsert --help") with a decision procedure for CLI vs API vs Dashboard. Minor gaps: the runnable example codebases (examples/express/, examples/nextjs/, examples/fastapi/) are referenced as canonical implementations but do not exist in the bundle.

4 / 5

Workflow Clarity

Workflow Stages 01–04 are clearly sequenced with explicit checkpoints (provider checklist "before scaffolding", whoami + user confirmation "before any queries or metrics", run --help before prescribing interfaces). Not a 5 because the checkpoints are restated inconsistently across sections rather than presented as one coherent validate-then-proceed loop, and error-recovery detail is deferred to references.

4 / 5

Progressive Disclosure

Good structure: 14 one-level-deep reference files, all of which exist, clearly signaled via "When to use" tables and numbered stage links. Kept from 5 by the broken examples/ directories cited as reference implementations and by long inline sections (the CLI/API/Dashboard decision guide, Production options paragraph) that read like reference material inlined into the overview.

4 / 5

Total

15

/

20

Passed

Description

95%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 description: explicit what/when with comprehensive natural trigger terms and clear boundary guidance against provider-webhook skills. The only weakness is the fluffy "Comprehensive guide" opener and a few topic-label capability items that keep specificity just below the top anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete capability areas ("receiving, routing, and delivering webhooks and events", "setup, connections, authentication, local development, monitoring, and API automation"), though the opener "Comprehensive guide" is mild fluff and some coverage items ("API automation") are topic names rather than concrete actions — minor gaps versus the fully comprehensive anchor.

4 / 5

Completeness

Explicitly answers both what ("receiving, routing, and delivering webhooks and events... Covers setup, connections, authentication...") and when ("Use when receiving webhooks... or local webhook development") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

The "Use when" clause comprehensively enumerates natural phrases users would say ("receiving webhooks", "setting up webhook endpoints", "testing webhooks locally", "webhook retry", "webhook monitoring", "event routing", "local webhook development") plus provider names (Stripe, Shopify, GitHub), covering synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

Clear niche (Hookdeck Event Gateway) with distinct triggers, and it explicitly disambiguates the closest conflict — provider-specific webhook skills — by directing composition with hookdeck/webhook-skills rather than overlap.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 6 missing

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

hookdeck/agent-skills

Path

skills/event-gateway/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.