CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

webhooks

Webhook management with HMAC signing and rate limiting

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/webhooks/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%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.

This is a strong, lean command-reference skill: exact syntax for every command, executable examples, and no filler. The one weakness is the absence of any validation or confirmation guidance around the destructive unregister (and disable) operations, which both caps workflow clarity and leaves the riskiest action unguarded.

Suggestions

Add a verification step before destructive commands, e.g. "Before unregistering, run `/webhooks get <id>` to confirm the path and trigger count, and confirm with the user before `/webhooks unregister`."

Document the feedback loop for failed signature validation (e.g. what happens to a request whose HMAC check fails) in the Security section.

Note whether registration is idempotent or what happens when registering an id that already exists, to remove ambiguity around the register/unregister cycle.

DimensionReasoningScore

Conciseness

The body is lean: a command table, copy-paste examples, a short list of what `get` shows, and a two-line security note. It never explains what webhooks or HMAC are, assumes Claude's competence, and every section adds information. Matches "Lean and efficient; assumes Claude's competence; every token earns its place"; the mild redundancy of the opening line restating the description is not enough to drop to 4.

5 / 5

Actionability

Full slash-command syntax is given for every operation ("/webhooks register <id> <path> --secret <key>", "/webhooks get <id>", etc.) and the Examples block shows copy-paste-ready invocations covering all common cases including registering with a secret. Matches "Fully executable; copy-paste ready code or commands; specific examples cover the common cases".

5 / 5

Workflow Clarity

Each individual command is unambiguous, but the skill includes a destructive operation — "/webhooks unregister <id>" removes a registration — with no validation or verification step (e.g. run `/webhooks get <id>` first or confirm before deleting). Per the judging guidelines, a destructive operation without validation caps workflow clarity at 3, and this cap takes precedence over the simple-skill exception. It is not a 2 because the command reference itself is coherent and well-sequenced.

3 / 5

Progressive Disclosure

The body is under 50 lines, single-purpose, and needs no external references (none exist in the bundle: references/, scripts/, and assets/ are absent). It is organized into clear sections (Commands, Examples, Webhook Details, Security), which per the guidelines earns a 5 for a short, self-contained skill.

5 / 5

Total

18

/

20

Passed

Description

53%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.

The description is concise and names a distinct, specific niche, but it stops at a domain-plus-features statement: the action verb is generic ("management"), natural trigger terms are thin, and there is no 'when to use' guidance. It reads as a competent but incomplete one-liner.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g. "Use when the user mentions webhooks, incoming endpoints, callbacks, or payload signature verification, or needs to register or inspect webhook endpoints."

Replace the generic "Webhook management" with concrete actions: "Register, list, enable/disable, and inspect incoming webhook endpoints with HMAC-SHA256 signature verification and rate limiting."

Include common synonyms users would naturally say (endpoints, callbacks, hooks) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

"Webhook management with HMAC signing and rate limiting" names the domain and two concrete technical features ("HMAC signing", "rate limiting"), but the core action "management" is generic — comparable to "Processes PDF files and extracts content". Not a 4 because it lists no concrete operations (register, inspect, verify signatures) and coverage is not comprehensive; not a 2 because the two named features go beyond a bare domain label.

3 / 5

Completeness

The 'what' is clearly stated ("Webhook management with HMAC signing and rate limiting") but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' is specific rather than vague; it cannot be 4 without any 'when' guidance at all.

3 / 5

Trigger Term Quality

"webhook" is a natural term users would say, and "HMAC" and "rate limiting" are relevant domain keywords, but common variations are missing — no "endpoints", "callbacks", "incoming requests", or "register". This matches "Some relevant keywords but missing common variations or synonyms"; a 4 would require broader natural-term coverage.

3 / 5

Distinctiveness Conflict Risk

Webhooks with HMAC signing and rate limiting is a fairly clear niche with minimal overlap risk against generic skills; only closely related API/HTTP-endpoint skills could compete. Matches "Mostly distinct; minor overlap risk with closely related skills"; not a 5 because without trigger phrases it could still fire for general HTTP-request or API-management tasks.

4 / 5

Total

13

/

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.

Validation — 15 / 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

alsk1992/CloddsBot

Path

src/skills/bundled/webhooks/SKILL.md

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.