CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agentline-webhooks

Receive and verify AgentLine webhooks. Use when setting up AgentLine (AI phone agent) webhook handlers, debugging X-Webhook-Signature verification, or handling events like call.received, call.utterance, call.completed and sms.received.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/agentline-webhooks/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 tight, vendor-fact-rich skill with genuinely executable verification code and well-organized one-level references. The main defects are broken navigation: the examples/ directories it repeatedly points to are absent from the bundle, and the core verification code and event table are duplicated between SKILL.md and the references files.

Suggestions

Ship the examples/express/, examples/nextjs/, and examples/fastapi/ directories in the bundle, or remove those links — the body leans on them four times ("For complete handlers with tests") and they currently dead-end.

De-duplicate content between SKILL.md and the references: keep only the single canonical verification snippet and a condensed event-type summary in the body, pointing to references/verification.md and references/overview.md for the rest.

Trim the Related Skills section (10 items) and the four external webhook-handler-patterns links to a short list, and make Setup an explicit step-by-step sequence (create webhook -> save secret -> verify -> webhook.test) so the workflow order is unambiguous.

DimensionReasoningScore

Conciseness

The body is dense with provider-specific facts Claude cannot know ("bare hex digest (no prefix, no timestamp)", "secret is returned in full once... masked on later reads", "Hookdeck's AgentLine source only checks X-Webhook-Signature") and never explains generic concepts like HMAC or webhooks. It falls short of 5 because the full event table and both verification functions are duplicated verbatim in references/overview.md and references/verification.md, and the ten-item Related Skills list plus the four external webhook-handler-patterns links add tokens that could be trimmed.

4 / 5

Actionability

Copy-paste-ready verification code in both Node and Python with real edge-case handling (hex-shape pre-check before Buffer.from, timingSafeEqual, compare_digest on bytes), an exact `npx hookdeck-cli listen 3000 agentline --path /webhooks/agentline` command, and env vars. Not 5: setup is described as a prose API call ("POST /v1/webhooks (agent_id, url, optional `secret`)") rather than an executable command, and the promoted complete examples point to example directories that are not present in the bundle.

4 / 5

Workflow Clarity

Sections form a coherent implicit sequence (verify -> handle events -> env vars -> setup -> local test) and the verification section embeds explicit checkpoints (shape check first, timing-safe compare, "Log a real webhook.test delivery to confirm"). Not 5: there is no explicit ordered setup-first workflow with a validation gate before handling events, and the debugging feedback loop lives only in references/verification.md rather than being surfaced as a step.

4 / 5

Progressive Disclosure

The three references files (overview.md, setup.md, verification.md) exist, are one level deep, and are clearly signaled with descriptions in a Resources section — good 4-level structure. However, the body promotes "complete handlers with tests" at examples/express/, examples/nextjs/, and examples/fastapi/ (referenced four times), and none of these paths exist in the bundle, leaving navigation broken for the primary detailed material. Confirmed below anchor 4 ('minor organization gaps') because dead-end links to the main example implementations are a structural gap, and above anchor 2/3's inlining problem since the overview/reference split itself is well done.

3 / 5

Total

15

/

20

Passed

Description

82%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 well-constructed: concrete what + explicit when, third person, vendor-specific trigger terms, and event names that users would naturally mention. Its only weakness is modest action coverage — 'receive and verify' understates the setup, event-handling, and testing guidance the skill actually provides.

Suggestions

Expand the 'what' clause with one or two more concrete actions to lift specificity, e.g. 'Receive and verify AgentLine webhooks, set up webhook endpoints, and handle call and SMS events.'

Consider adding a natural trigger phrase for the debugging scenario users actually voice, such as 'webhook signature verification failing', which currently only appears in the body's When-to-Use section.

DimensionReasoningScore

Specificity

"Receive and verify AgentLine webhooks" names the domain with two concrete actions, matching the anchor for 1-2 concrete actions without comprehensive coverage (setup, event handling, and testing from the body are only hinted at via the 'when' clause). It does not reach 4 because no additional specific actions beyond receive/verify are listed, and is above 2 because the actions are concrete rather than generic.

3 / 5

Completeness

Explicitly answers both: what ("Receive and verify AgentLine webhooks") and when ("Use when setting up AgentLine (AI phone agent) webhook handlers, debugging X-Webhook-Signature verification, or handling events like...") with concrete trigger phrases. This matches anchor 5 directly; anchor 4's weaker 'when could be more explicit' does not apply given the three specific trigger scenarios.

5 / 5

Trigger Term Quality

Strong natural keywords: "AgentLine webhooks", "AI phone agent", "webhook handlers", "X-Webhook-Signature verification", and concrete event names "call.received, call.utterance, call.completed and sms.received". A few natural phrases users might say are missing (e.g. "webhook secret", "signature verification failing", "test webhook"), so it falls just short of the comprehensive-synonyms anchor 5 but is clearly above anchor 3's 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

"AgentLine" is a distinct product name and the event names plus "X-Webhook-Signature" are AgentLine-specific triggers, giving a clear niche with minimal conflict risk even among the sibling telephony webhook skills. Confirmed against anchor 4: the overlap risk is not merely 'minor' — the vendor-specific identifiers make wrong-skill triggering unlikely.

5 / 5

Total

17

/

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: 6 missing

Warning

Total

15

/

16

Passed

Repository

hookdeck/webhook-skills

Path

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