CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

commercelayer-webhooks

Receive and verify Commerce Layer webhooks. Use when setting up Commerce Layer webhook handlers, debugging X-CommerceLayer-Signature verification, or handling commerce events like orders.place, orders.approve, orders.pay, or shipments.ship.

Quality

78%

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 ./skills/commercelayer-webhooks/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 well-structured, highly actionable skill whose core verification guidance is excellent and lean. The main weaknesses are dead examples/ links, an implicit rather than explicit handler workflow, and roughly 30% of the body spent on attribution boilerplate and cross-promotional link lists rather than instruction.

Suggestions

Remove the 'Attribution' section and trim the 'Recommended' and 'Related Skills' sections (16 lines of external cross-promotion) to a single line each, cutting non-instructional padding and reducing duplication with the event table already in references/overview.md.

Add an explicit numbered handler workflow in the body: 1) read the raw request body, 2) verify X-CommerceLayer-Signature, 3) reject with an error status on verification failure, 4) dispatch on X-CommerceLayer-Topic, 5) return 2xx within 5 seconds and offload slow work asynchronously.

Fix or remove the dangling references to examples/express/, examples/nextjs/, and examples/fastapi/ — these directories do not exist in the bundle, so users following the 'complete handlers' pointer hit a dead end.

DimensionReasoningScore

Conciseness

Core sections (verification code, environment variables, tunnel command, reliability facts) are tight and high-value, but roughly 30% of the body is boilerplate or duplication: an 8-line 'Attribution' section, 7 lines of 'Recommended' cross-promotion, a 10-line 'Related Skills' directory of 9 external links, and an event table duplicated nearly verbatim in references/overview.md. This goes beyond the 'minor instances' of anchor 4 but is not severely verbose throughout, so anchor 3 fits best.

3 / 5

Actionability

The Node and Python verification functions are complete, executable, and copy-paste ready, and the hookdeck-cli tunnel command is exact. It falls short of anchor 5 because the pointer to 'complete handlers with route wiring, event dispatch, and tests' references examples/express/, examples/nextjs/, and examples/fastapi/ directories that do not exist in the bundle, leaving a real gap for the most common use case.

4 / 5

Workflow Clarity

The handler workflow (receive raw body, verify signature, dispatch on X-CommerceLayer-Topic, return 2xx within 5 seconds) is implied by section order and the 'Verify fast, then do slow work asynchronously' line, but is never explicitly sequenced, and failure/debug checkpoints only exist in references/verification.md rather than the body. This matches anchor 3 (sequence present but checkpoints implicit) and lacks the explicit ordered steps of anchor 4.

3 / 5

Progressive Disclosure

All three bundle reference files (overview.md, setup.md, verification.md) are real, exactly one level deep, and clearly signaled with one-line descriptions both inline and in the 'Reference Materials' section. It misses anchor 5 because the body links to nonexistent examples/ directories and the event table duplicates content that already lives in references/overview.md.

4 / 5

Total

14

/

20

Passed

Description

87%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 strong description that clearly states what the skill does and when to use it, with concrete provider-specific trigger terms and event names. Third-person voice is used correctly. Only minor improvements are available: adding setup-side actions (creating the webhook, shared_secret retrieval) and a few natural synonyms like 'callback endpoint'.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'Receive and verify Commerce Layer webhooks', 'setting up Commerce Layer webhook handlers', 'debugging X-CommerceLayer-Signature verification', 'handling commerce events like orders.place, orders.approve, orders.pay, or shipments.ship'. Falls short of anchor 5 because setup coverage has a minor gap: creating the webhook and retrieving its shared_secret (a key part of setup) is not mentioned.

4 / 5

Completeness

Clearly answers both parts: 'Receive and verify Commerce Layer webhooks' states what the skill does, and 'Use when setting up Commerce Layer webhook handlers, debugging X-CommerceLayer-Signature verification, or handling commerce events like orders.place...' gives explicit, concrete trigger phrases. This matches the anchor 5 example structure exactly.

5 / 5

Trigger Term Quality

Good coverage of natural phrases users would say: 'Commerce Layer webhooks', 'webhook handlers', 'X-CommerceLayer-Signature verification', and concrete event names. Below anchor 5 because a few natural variations are missing, such as 'callback endpoint', 'callback URL', or generic 'webhook signature' phrasing.

4 / 5

Distinctiveness Conflict Risk

The Commerce Layer brand is named throughout, along with provider-specific details (X-CommerceLayer-Signature header, orders.place/shipments.ship topics), giving it a clear niche with minimal overlap risk against other webhook skills (Stripe, Shopify, etc.).

5 / 5

Total

18

/

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/commercelayer-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.