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.

76

Quality

96%

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

92%Weight 40%Scale 1-3

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

The body is highly actionable with executable commands and clear, validated workflows, and it correctly delegates the detailed checklist to a one-level reference. Minor redundancy in signature details across multiple sections is the main token-efficiency concern.

Suggestions

Consolidate the per-provider signature details so they live in one table only (the 'Signature Algorithms by Provider' section) and have the 'Current Providers' and 'Gotchas' sections reference it rather than restate it.

Consider moving the per-service registration steps (Vercel/GitHub/Todoist/Front) into the new-provider-checklist reference to keep the overview lean.

DimensionReasoningScore

Conciseness

The body is dense and free of generic concept explanations, but signature details are restated across the providers table, the dedicated signature-algorithms table, the gotchas, and the checklist, adding redundant tokens.

2.5 / 3

Actionability

Provides concrete, copy-paste-ready shell commands (openssl HMAC, curl, joelclaw gateway/logs/runs) and exact repository file paths, fully executable rather than pseudocode.

3 / 3

Workflow Clarity

The 8-step add-provider checklist is explicitly sequenced with a terminal 'Verify E2E with curl + real webhook' checkpoint, and the debugging section gives validate-then-retry feedback for signature failures.

3 / 3

Progressive Disclosure

SKILL.md is a concise overview that links to a single, well-signaled one-level reference (references/new-provider-checklist.md, a real file) for the full checklist, with content appropriately split and easy to navigate.

3 / 3

Total

11.5

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 highly specific, action-oriented, and rich with natural trigger phrases, clearly answering both what the skill does and when to use it. It occupies a distinct niche with low conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Add, debug, and manage webhook providers', 'debugging webhook signature failures', 'checking webhook delivery', 'testing webhook endpoints', 'registering webhooks with external services' — matching the top anchor.

3 / 3

Completeness

Explicitly answers both 'what' (add/debug/manage webhook providers in the gateway) and 'when' via a clearly labeled 'Use when:' clause and a 'Triggers on:' list.

3 / 3

Trigger Term Quality

Strong coverage of natural phrasings a user would say: 'add a webhook', 'webhook not working', 'webhook signature failed', 'register webhook', 'webhook debug', 'verify webhook', 'webhook 401', 'test webhook endpoint'.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to the joelclaw webhook gateway and signature/delivery specifics; unlikely to trigger for unrelated skills.

3 / 3

Total

12

/

12

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.