CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

community-webhooks

Receive and verify Community (community.com) SMS platform webhooks. Use when setting up a Community webhook handler, debugging `community-signature` HMAC-SHA256 verification, or handling message.inbound, message.outbound, member.created, member.updated, and member.deleted events.

Quality

92%

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

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

A strong, information-dense skill body: executable verification code, precise platform facts (delivery semantics, sparse member.deleted payloads, signature secret vs API token), and a well-signaled one-level reference structure. Weaknesses are minor: a promotional tail of related-skill links that costs tokens, and example directories referenced but absent from the bundle.

Suggestions

Trim the 'Recommended' and 'Related Skills' sections to 2-3 links each (or fold them into one line) — the ~20 lines of sibling-skill promotion dilute the core content and cost context tokens.

Either include the examples/ directories (express, nextjs, fastapi) in the bundle or reword the link to point at the GitHub repository URL, so the 'complete handlers with tests' pointer isn't a dead path.

Add a short numbered handler sequence in the Delivery Semantics section (parse header → verify HMAC → check dedup store → enqueue → return 2xx) so the workflow is fully self-contained instead of delegating sequence details to the external webhook-handler-patterns skill.

DimensionReasoningScore

Conciseness

The core is lean and fact-dense, assumes competence ("re-serializing the JSON changes the bytes and breaks the signature", sparse member.deleted field list, retry budget), but ~25 lines of cross-promotion ("Recommended: webhook-handler-patterns" with four external links, seven "Related Skills", and an Attribution section) are tokens that don't serve the task. Not 5 because of that padding; not 3 because nothing explains concepts Claude already knows.

4 / 5

Actionability

Fully executable guidance: a copy-paste Node.js verifyCommunitySignature function that parses the header without assuming field order and uses timingSafeEqual, the exact signed payload (`{timestamp}.{raw_body}`), a working `npx hookdeck-cli listen 3000 community --path /webhooks/community` command, env vars with dashboard navigation paths, and exact delivery rules (2xx within 15s, 5 retries over an hour, dedupe window of an hour). Covers the common cases completely.

5 / 5

Workflow Clarity

The handler sequence is explicit and prioritized — "verify, enqueue, return 2xx fast — never do the work inline" — with the signature check acting as a built-in validation checkpoint, and dedup guidance includes a concrete time window. Not 5: idempotency/error-handling/retry specifics are delegated to a separate skill rather than summarized as a numbered in-skill sequence, so a reader of this file alone gets direction, not a full step-by-step loop.

4 / 5

Progressive Disclosure

Good split: the core (verification, events, envelope, delivery semantics) is inline and the three referenced files (references/overview.md, setup.md, verification.md) exist in the bundle, are one level deep, and each has a descriptive one-line label. Not 5: the body links examples/express/, examples/nextjs/, and examples/fastapi/ for "complete handlers with tests", but no examples/ directory exists in the bundle, leaving dangling paths at the exact moment a user needs deeper material.

4 / 5

Total

17

/

20

Passed

Description

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

A model description: concrete actions, an explicit "Use when..." clause with three realistic triggers, and platform-specific terms that make conflict with other skills unlikely. Written in the imperative/third-person style consistent with the reference examples.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions with comprehensive coverage: "Receive and verify Community (community.com) SMS platform webhooks", "debugging `community-signature` HMAC-SHA256 verification", and handling all five documented event types (message.inbound, message.outbound, member.created, member.updated, member.deleted). Not 4: there are no minor gaps — the what (receive/verify) and sub-tasks (setup, debug, event handling) are all named.

5 / 5

Completeness

Explicitly answers both questions: the what is "Receive and verify Community (community.com) SMS platform webhooks" and the when is an explicit "Use when setting up a Community webhook handler, debugging ... verification, or handling ... events" with three concrete trigger phrases. Matches the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage: "Community webhooks", "community.com", "webhook handler", "community-signature", "HMAC-SHA256 verification", "SMS platform", plus every event-type name a user would paste verbatim when asking for help. Not 4: it includes the platform's distinctive terms and their natural variations rather than missing common phrasings.

5 / 5

Distinctiveness Conflict Risk

Clear niche: brand-anchored to community.com's SMS platform with platform-specific artifacts (`community-signature` header, exact event names), so it is distinguishable from generic community-forum products and only trivially overlaps with sibling SMS webhook skills. Not 4: the triggers are brand-unique, not merely "mostly distinct".

5 / 5

Total

20

/

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

relative_links

Relative link issues: 3 missing

Warning

Total

15

/

16

Passed

Repository

hookdeck/webhook-skills

Path

skills/community-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.