CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-api-webhooks-catalog

api/webhooks — 15 abstractions.

55

Quality

61%

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/user-skills/generated/api/webhooks/SKILL.md
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.

The body is a well-structured, token-efficient catalog that gives concrete imports and source paths for 15 abstractions with a clear usage workflow. Its main gap is the absence of executable usage examples, which are deferred to source files and sibling pattern skills.

DimensionReasoningScore

Conciseness

The body is a lean catalog: each entry is just Name/Kind/Import/Source with no padding, no explanation of what webhooks are, and a single terse 'How to Use' block — every token earns its place and it assumes Claude's competence, matching the 'lean and efficient' anchor.

5 / 5

Actionability

Each entry gives a copy-paste-ready import statement and an exact source path, and the workflow shows the import template, but no usage example (calling createWebhooks, dispatching, verifying) is shown — details are deferred to source files, fitting 'mostly executable guidance; minor gaps' rather than fully copy-paste-ready usage at 5.

4 / 5

Workflow Clarity

The 'How to Use' section gives a clear 4-step sequence (find → read source → import → consult pattern skills) for this simple lookup skill; no validation checkpoints are needed for a non-destructive catalog, fitting 'clear sequence with most checkpoints present' — not 5 because it is a multi-step list rather than a single unambiguous action.

4 / 5

Progressive Disclosure

Content is organized into clear 'How to Use' and 'Abstractions' sections with a consistent per-entry format, and references to source paths and two related skills are clearly signaled; no bundle files exist so structure is flat and one-level, fitting 'good structure; most content appropriately placed; minor organization gaps' rather than the idealized multi-reference 5.

4 / 5

Total

17

/

20

Passed

Description

40%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 an extremely terse catalog label: it names a narrow domain and a count but states no actions and gives no usage trigger, so it fails to tell Claude when to invoke it. It is distinctive but incomplete and only weakly specific.

Suggestions

Add a 'Use when ...' clause naming concrete triggers, e.g. 'Use when implementing or debugging Webiny webhook delivery, signing, or dispatch in api/webhooks.'

Replace the bare count with 2-3 concrete actions, e.g. 'Catalogs the createWebhooks, WebhookDispatcher, and payload sign/verify abstractions for Webiny api/webhooks.'

Include natural synonyms users might say (webhooks, webhook delivery, payload signing) rather than only the package path and the word 'abstractions'.

DimensionReasoningScore

Specificity

The phrase 'api/webhooks — 15 abstractions' names the domain and counts entries but describes no concrete actions (e.g. 'send', 'verify', 'route' webhooks), matching the 'Names the domain but actions are minimal or generic' anchor rather than the entirely-vague 1.

2 / 5

Completeness

There is only a vague 'what' (a catalog of 15 abstractions) and no 'when/Use when' trigger guidance at all, hitting the 'vague what and no when' anchor; the missing trigger clause also caps completeness at 3 per guidelines, and this lands below it.

2 / 5

Trigger Term Quality

The word 'webhooks' is the natural term users would say, but it is wrapped in technical package-path notation ('api/webhooks') and jargon ('abstractions'), with no synonyms like 'delivery', 'payload', or 'sign' — matching 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

'api/webhooks' is a narrow, specific niche with minimal overlap risk against other skills, fitting 'mostly distinct; minor overlap risk with closely related skills'; not a 5 because the terse description does not establish distinct trigger phrases.

4 / 5

Total

11

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
webiny/webiny-js
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.