CtrlK
BlogDocsLog inGet started
Tessl Logo

openai-webhooks

Receive and verify OpenAI webhooks. Use when setting up OpenAI webhook handlers for fine-tuning jobs, batch completions, or async events like fine_tuning.job.completed, batch.completed, or realtime.call.incoming.

64

Quality

77%

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/openai-webhooks/SKILL.md
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 content is highly actionable with complete signature-verification code in two languages and a clear receive-verify-parse-handle workflow. Weaker spots are token padding from the duplicated event table and long related-skills link list, plus a Python example that stops short of full event handling.

Suggestions

Trim the 10-item "Related Skills" list to the 2-3 most relevant siblings (e.g. webhook-handler-patterns and one billing provider) to reclaim tokens.

Either complete the Python/FastAPI event-dispatch switch to match the Express example or explicitly note it is abbreviated, so the secondary example is not misleading.

Remove the standalone "Common Event Types" table or replace it with a pointer to references/overview.md, since the same events are already enumerated in the Express switch.

DimensionReasoningScore

Conciseness

The body is mostly efficient code, but includes unnecessary padding such as a 10-link "Related Skills" list and a "Common Event Types" table that duplicates the cases already handled in the Express switch statement.

3 / 5

Actionability

Provides two concrete, mostly copy-paste-ready implementations (Express, FastAPI) plus specific commands (npx hookdeck-cli) and env vars; a minor gap is the Python example trailing off with "# Handle event..." instead of a full handler.

4 / 5

Workflow Clarity

The handler sequence is clear (raw body -> verify signature with timestamp replay check -> parse -> dispatch), with an explicit validation checkpoint before parsing and 400 responses on failure; falls short of 5 because retry/error-recovery feedback loops are delegated to another skill rather than shown inline.

4 / 5

Progressive Disclosure

Good structure with real one-level-deep references (overview.md, setup.md, verification.md) clearly signaled in a "Reference Materials" section, and core code kept inline; minor gaps are the two full implementations inlined and the "examples/" links pointing to non-existent bundle paths.

4 / 5

Total

15

/

20

Passed

Description

87%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 strong: it clearly states what the skill does and when to use it with concrete, provider-specific trigger phrases and event names. Its only weakness is modest action-verb variety (receive/verify) rather than a richer enumeration of capabilities.

DimensionReasoningScore

Specificity

"Receive and verify OpenAI webhooks" names two concrete actions and enumerates specific operations (fine-tuning jobs, batch completions, realtime events); not quite a 5 since the action verbs are limited to receive/verify even though coverage of event types is broad.

4 / 5

Completeness

Explicitly answers both what ("Receive and verify OpenAI webhooks") and when ("Use when setting up OpenAI webhook handlers for fine-tuning jobs, batch completions, or async events like...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural developer keywords ("OpenAI webhooks", "webhook handlers", "fine-tuning jobs", "batch completions") plus concrete event names users would cite; falls short of 5 because it lacks synonyms/file-extension style coverage and leans on technical event identifiers.

4 / 5

Distinctiveness Conflict Risk

"OpenAI webhooks" is a clear niche with provider-specific event types (fine_tuning.job.completed, batch.completed, realtime.call.incoming), giving it distinct triggers and minimal conflict risk with sibling webhook skills.

5 / 5

Total

18

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 missing

Warning

Total

15

/

16

Passed

Repository
hookdeck/webhook-skills
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.