Name: webhook
Rating: 53.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

webhook

Webhook integration. Manage Recordses. Use when the user wants to interact with Webhook data.

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/webhook/SKILL.md

Quality

Content

63%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 content is highly actionable, with executable Membrane CLI commands and a clear, state-aware connection workflow including feedback loops. It is held back by an unnecessary introductory explanation of webhooks, a dangling 'Step 2' reference, an empty 'Popular actions' section, and the absence of any progressive-disclosure references despite ~140 lines of inline material.

Suggestions

Delete the opening paragraph defining webhooks and the vague 'Webhook Overview / Use action names and parameters as needed' filler; Claude already knows what webhooks are.

Fix the dangling 'skip to Step 2' references by labeling the steps or removing the cross-references so the connection workflow is self-contained.

Move the proxy options table and the full clientAction state schema into a references/ file (e.g. references/connection-states.md) and link to it from SKILL.md to keep the body a lean overview.

Dimension	Reasoning	Score
Conciseness	The body opens by explaining what webhooks are ('Webhooks are automated messages sent from apps when something happens') and includes a vague 'Webhook Overview' with 'Use action names and parameters as needed' — concepts Claude already knows — so it is mostly efficient but carries unnecessary explanation, matching the level-3 anchor rather than the leaner level-4.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands throughout (npm install, membrane login, connection ensure, action list/run, request) with a clear options table, but leaves placeholders like CONNECTION_ID unfilled and the 'Popular actions' section only points to discovery rather than listing actual actions, giving 'mostly executable with minor gaps' rather than fully comprehensive level-5.	4 / 5
Workflow Clarity	The connection flow is well-sequenced with explicit state checks (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a poll-after-action feedback loop, but it references a 'Step 2' that is never labeled, leaving a minor navigation gap; this fits 'clear sequence with most checkpoints, minor validation gaps' rather than the fully-checkpointed level-5.	4 / 5
Progressive Disclosure	The skill has no bundle files and keeps all content inline in SKILL.md with decent section headers, but material that could live one level deep (the proxy options table, the full clientAction schema) is inlined and there are no signaled references to separate files, matching 'some structure but could be better organized' rather than the well-split level-4.	3 / 5
	Total	14 / 20 Passed

Description

57%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 correctly uses third person and includes an explicit 'Use when' trigger clause, so it avoids the completeness cap and is reasonably distinct. Its main weakness is the vague/garbled action list ('Manage Recordsse') and thin trigger-term coverage, which keep specificity and trigger quality at the lower-middle band.

Suggestions

Replace the garbled 'Manage Recordsse' with concrete, correctly-spelled actions, e.g. 'Create, list, and deliver webhook events and manage webhook endpoints'.

Broaden trigger terms to natural phrasings users actually say, such as 'set up a webhook', 'webhook delivery', 'register a webhook endpoint', and 'receive webhook events'.

Make the 'when' clause more specific by naming scenarios, e.g. 'Use when the user wants to send or receive webhook events from an external app via Membrane'.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Webhook integration") and one minimal/garbled action ("Manage Recordsse"), but does not list several concrete, correctly-stated actions; this matches the anchor that names the domain with minimal or generic actions rather than the level above which lists 1-2 clear concrete actions.	2 / 5
Completeness	It provides both a 'what' ("Webhook integration. Manage Recordsse.") and an explicit 'when' trigger clause ("Use when the user wants to interact with Webhook data"), satisfying the 'Use when' requirement; the 'when' is present but could be more specific, matching the level-4 anchor rather than the fully-explicit level-5 example.	4 / 5
Trigger Term Quality	It repeats the keyword "Webhook" and offers the phrase "interact with Webhook data", giving some relevant keywords, but it misses common natural variations and synonyms a user would actually say (e.g. "set up a webhook", "webhook delivery", "register an endpoint"), fitting the 'some relevant keywords but missing synonyms' anchor.	3 / 5
Distinctiveness Conflict Risk	Webhooks are a recognizable niche and the trigger ("interact with Webhook data") is mostly distinct from other skills, with only minor overlap risk against generic integration skills; this fits 'mostly distinct; minor overlap risk' better than the broader level-3 anchor.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/webhook/SKILL.md
Commit: f484c82

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.