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.
93
92%
Does it follow best practices?
Impact
Pending
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 clearly defines its scope (webhook management in a specific gateway), lists concrete actions, and provides comprehensive trigger terms covering both user intent phrases and specific error scenarios. The explicit 'Use when' and 'Triggers on' sections make it highly actionable for skill selection. The description is well-structured and distinctive enough to avoid conflicts with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: add, debug, and manage webhook providers, debug signature failures, check delivery, test endpoints, register webhooks with external services, and review 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 and a detailed 'Triggers on:' section listing specific scenarios and 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 a webhook', 'test webhook endpoint', and named services like GitHub, Stripe, Vercel. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — scoped specifically to the 'joelclaw webhook gateway' with webhook-specific terminology and actions. Unlikely to conflict with general API, HTTP, or integration skills due to the named system and webhook-specific triggers. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%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, well-structured skill that provides highly actionable guidance for webhook gateway operations. It excels at workflow clarity with clear debugging sequences and provider registration steps, and makes good use of progressive disclosure by referencing detailed checklists externally. Minor conciseness improvements could be made by consolidating the two provider/signature tables, but overall the content is dense with useful, project-specific information.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient and project-specific, but some sections like the full signature algorithms table partially duplicate the current providers table. The architecture diagram and key files table are dense but earn their place. Some minor redundancy exists but overall it respects Claude's intelligence. | 2 / 3 |
Actionability | Provides fully executable bash commands for debugging (curl, openssl HMAC generation), registering webhooks with specific services (Vercel API call), and concrete file paths for every operation. The quick summary steps reference specific filenames and commands. | 3 / 3 |
Workflow Clarity | The new provider workflow is clearly sequenced (8 steps with a reference to full checklist), debugging has a clear diagnostic flow (check arrival → check signature → check Inngest → check gateway), and the signature verification section includes explicit error recovery guidance for common failures. | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview with the full 8-step checklist delegated to references/new-provider-checklist.md, references ADR-0048 for architectural decisions, and links to the gateway skill for delivery patterns. Content is well-organized into logical sections without being monolithic. | 3 / 3 |
Total | 11 / 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
825972c
- 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.