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.
72
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
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 covers all dimensions thoroughly. It provides specific actions, comprehensive trigger terms including error scenarios and service names, explicit 'Use when' and 'Triggers on' clauses, and is scoped to a distinct system. The description is well-structured and uses third person voice appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: add, debug, and manage webhook providers, debugging signature failures, checking delivery, testing endpoints, registering webhooks, and reviewing 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 error scenarios ('webhook 401', 'webhook signature failed'), action phrases ('add a webhook', 'register webhook'), and named services ('GitHub', 'Stripe', 'Vercel'). These are highly natural phrases a user would actually type. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — scoped to a specific system ('joelclaw webhook gateway') and a specific domain (webhook provider management). The named system and specific webhook-related triggers make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
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 with concrete commands, specific file paths, and clear workflows for a complex webhook gateway system. Its main weakness is moderate verbosity — some tables contain overlapping information and the registration section mixes project-specific gotchas with generic service setup steps. Progressive disclosure is partially implemented with one reference file, but the skill carries substantial inline detail that could benefit from further splitting.
Suggestions
Consider extracting the 'Registering Webhooks with Services' and 'Signature Algorithms by Provider' sections into a separate reference file to reduce the main skill's token footprint and avoid duplication with the Current Providers table.
Ensure the referenced 'references/new-provider-checklist.md' file actually exists in the bundle, or inline the critical steps if it doesn't.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient and project-specific, but includes some information that could be tightened — the Signature Algorithms table largely duplicates data already in the Current Providers table, and some registration instructions (GitHub, Vercel) are fairly generic. However, most content is domain-specific and earns its place. | 2 / 3 |
Actionability | Provides fully executable bash commands for debugging (HMAC generation, curl tests, log watching), concrete file paths for every key component, specific CLI commands for deployment and verification, and exact header names and encoding formats. Copy-paste ready throughout. | 3 / 3 |
Workflow Clarity | The 'Adding a New Provider' section has a clear 8-step sequence with deployment and E2E verification at the end. Debugging workflows are well-sequenced (check arrival → check signature → check Inngest → check gateway). The checklist reference and explicit verification steps demonstrate good feedback loops. | 3 / 3 |
Progressive Disclosure | References the detailed checklist at 'references/new-provider-checklist.md' which is good progressive disclosure, but no bundle files were provided to confirm it exists. The main file itself is fairly long (~150 lines of substantive content) with the signature algorithms table and registration details that could potentially be split into reference files. The single reference is well-signaled though. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%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
03f0a59
- 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.