CtrlK
BlogDocsLog inGet started
Tessl Logo

webhooks

Add, debug, and manage webhook providers in the joelclaw webhook gateway. Use when: adding a new webhook integration (GitHub, Stripe, Vercel, etc.), debugging webhook signature failures, checking webhook delivery, testing webhook endpoints, registering webhooks with external services, or reviewing webhook provider implementations. Triggers on: 'add a webhook', 'new webhook provider', 'webhook not working', 'webhook signature failed', 'register webhook', 'webhook debug', 'verify webhook', 'add Vercel/GitHub/Stripe webhook', 'webhook 401', 'test webhook endpoint', or any external service webhook integration task.

74

Quality

93%

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

86%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 dense, executable operations skill with concrete commands, a sequenced provider-onboarding workflow, and a properly signaled one-level reference for the detailed checklist. The main weakness is minor redundancy between the two signature-related tables.

Suggestions

Consolidate the 'Current Providers' signature column and the 'Signature Algorithms by Provider' table into one table to remove duplicated header/algorithm info and save tokens.

Add an explicit validate-then-retry loop to the inline add-provider summary (e.g., 'if signature verification fails, see Debugging Webhooks and re-run step 8') so the workflow stands alone without the referenced checklist.

Consider moving the per-service registration instructions (Vercel/GitHub/Todoist/Front) into the new-provider-checklist reference, keeping only the generic registration pattern inline.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence (no explanations of webhooks, HMAC, or libraries), but signature/header info is duplicated between the 'Current Providers' table and the later 'Signature Algorithms by Provider' table, a redundancy that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready curl and openssl HMAC commands, concrete joelclaw CLI invocations, and exact file paths covering the common debug and registration cases — fully executable guidance.

5 / 5

Workflow Clarity

The 8-step add-provider sequence is clearly ordered with a terminal 'Verify E2E with curl + real webhook' checkpoint and a migration guard, but the inline quick summary lacks an explicit validate-then-fix retry loop compared to the referenced full checklist.

4 / 5

Progressive Disclosure

Body is a well-organized overview that defers the full checklist to references/new-provider-checklist.md (a verified, real, one-level-deep reference) while keeping operational quick-reference tables inline, matching the clear-navigation anchor.

5 / 5

Total

18

/

20

Passed

Description

100%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, third-person description that pairs concrete capability verbs with extensive natural trigger phrases and provider-specific scope. It cleanly answers both what the skill does and when to invoke it with negligible conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Add, debug, and manage webhook providers' plus 'debugging webhook signature failures', 'checking webhook delivery', 'testing webhook endpoints', 'registering webhooks' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' ('Add, debug, and manage webhook providers in the joelclaw webhook gateway') and 'when' (a 'Use when' list plus a 'Triggers on' list with concrete trigger phrases), the top anchor.

5 / 5

Trigger Term Quality

The 'Triggers on' clause supplies natural user phrases ('add a webhook', 'webhook not working', 'webhook signature failed', 'webhook 401', 'test webhook endpoint') including named provider variants, matching the comprehensive-synonyms anchor.

5 / 5

Distinctiveness Conflict Risk

Scoped to the joelclaw webhook gateway with named providers (GitHub, Stripe, Vercel, Todoist, Front), giving a clear niche with minimal overlap risk against generic skills.

5 / 5

Total

20

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
joelhooks/joelclaw
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.