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.

Quality

88%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, highly actionable skill that provides concrete commands, file paths, and debugging workflows for a complex webhook gateway system. Its main strength is the executable examples and clear diagnostic sequences. Minor weaknesses include some content duplication between tables and the lack of bundle files to support the referenced checklist, plus the overall length could benefit from splitting registration and signature details into separate reference files.

Suggestions

Consider splitting the 'Registering Webhooks with Services' and 'Signature Algorithms by Provider' sections into a separate reference file to reduce the main skill's token footprint.

Ensure the referenced 'references/new-provider-checklist.md' file actually exists in the bundle, or inline the checklist if no bundle structure is planned.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient and project-specific, but includes some information that could be trimmed — the full signature algorithms table partially duplicates the current providers table, and some sections like the Gotchas list mix critical operational knowledge with things Claude could infer. Overall reasonably lean for the complexity covered.	2 / 3
Actionability	Highly actionable throughout: executable bash commands for debugging, curl examples for registration, specific file paths for implementation, concrete secret storage commands, and exact header names and encoding formats. Nearly everything is copy-paste ready.	3 / 3
Workflow Clarity	The 8-step new provider workflow is clearly sequenced with a quick summary and reference to a full checklist. Debugging workflows have clear diagnostic sequences (check arrival → check signature → check Inngest → check gateway). The architecture diagram provides clear mental model of the request flow.	3 / 3
Progressive Disclosure	References the full checklist at 'references/new-provider-checklist.md' which is good progressive disclosure, but no bundle files are provided to verify this exists. The SKILL.md itself is fairly long (~150 lines of substantive content) and the signature algorithms table and registration details could potentially be split into reference files. The single reference is well-signaled though.	2 / 3
	Total	10 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an excellent skill description that hits all the marks. It provides specific concrete actions, comprehensive natural trigger terms, explicit 'Use when' and 'Triggers on' clauses, and is scoped to a clearly identifiable system. The description is thorough without being padded, and uses proper third-person voice throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Add, debug, and manage webhook providers', 'adding a new webhook integration', 'debugging webhook signature failures', 'checking webhook delivery', 'testing webhook endpoints', 'registering webhooks with external services', 'reviewing webhook provider implementations'.	3 / 3
Completeness	Clearly answers both 'what' (add, debug, manage webhook providers in the joelclaw webhook gateway) and 'when' with an explicit 'Use when:' clause listing specific scenarios, plus a 'Triggers on:' section with concrete trigger phrases.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms users would say, including specific phrases like 'webhook not working', 'webhook signature failed', 'webhook 401', 'add Vercel/GitHub/Stripe webhook', and 'test webhook endpoint'. These are realistic phrases a user would naturally type.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive — scoped to a specific system ('joelclaw webhook gateway') and a specific domain (webhook provider management). The combination of the named system and webhook-specific terminology makes it very unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: joelhooks/joelclaw
Commit: 2ca3686

Reviewed: 10 days ago

Table of Contents

Discovery Implementation Validation

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.