aircall-webhooks

Receive and verify Aircall webhooks. Use when setting up Aircall webhook handlers, debugging Aircall webhook token verification, or handling Aircall cloud phone events like call.created, call.answered, call.ended, message.received, contact.updated, or user.connected.v2. Aircall does NOT use an HMAC signature — verification is a timing-safe comparison of the `token` field inside the JSON body.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

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 highly actionable with executable verification code and concrete delivery-semantics guidance, well-structured with real one-level-deep references. It is slightly verbose in places and references non-existent examples/ directories, which are the main weaknesses.

Suggestions

Remove or fix the dangling links to examples/express/, examples/nextjs/, and examples/fastapi/ — these directories are not present in the bundle, so the pointers lead nowhere.

Trim the editorializing about incorrect third-party HMAC blog posts and the 12-item related-skills list to reduce token cost while preserving the core disambiguation.

Inline a brief numbered verify→parse→handle-idempotently sequence with a feedback checkpoint rather than only delegating it to the webhook-handler-patterns skill.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes competence (verification code, env vars, payload table), but the extended editorializing about wrong HMAC blog posts and the long 12-item related-skills list add tokens that could be trimmed. Not a 5 because of these padded stretches; not a 3 because the core is efficient and free of generic concept explanations.	4 / 5
Actionability	Provides copy-paste-ready executable verification code in both JavaScript and Python, a concrete env-var example with a real value, an inspection CLI command, and a concrete JSON payload example. Specific examples cover the common handler cases.	5 / 5
Workflow Clarity	The "Delivery Semantics" section gives a clear handler sequence (respond 200 immediately, at-least-once unordered, upsert on call.id, auto-disable) with verification and idempotency checkpoints. Not a 5 because the explicit numbered validate→fix→retry feedback loop is delegated to another skill rather than presented inline; not a 3 because idempotency and verification guidance are clearly present.	4 / 5
Progressive Disclosure	SKILL.md acts as an overview with one-level-deep, clearly signaled references to references/overview.md, setup.md, and verification.md, all of which exist in the bundle. Not a 5 because the body links examples/express/, examples/nextjs/, and examples/fastapi/ which do not exist in the bundle — a minor navigation gap.	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.

The description is concise, concrete, and complete: it states what the skill does, when to use it with natural trigger phrases, and even clarifies the non-HMAC verification mechanism. Third-person voice is used throughout. No suggestions needed.

Dimension	Reasoning	Score
Specificity	"Receive and verify Aircall webhooks" names the domain and multiple concrete actions (receive, verify, debug token verification, handle named events), with comprehensive coverage including a list of specific event types.	5 / 5
Completeness	Explicitly answers both what ("Receive and verify Aircall webhooks") and when ("Use when setting up Aircall webhook handlers, debugging... or handling Aircall cloud phone events") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural terms users would say are comprehensively covered — "Aircall webhooks", "Aircall webhook handlers", "Aircall webhook token verification", "Aircall cloud phone events", plus concrete event names like call.created and call.answered.	5 / 5
Distinctiveness Conflict Risk	Clearly scoped to Aircall webhooks with Aircall-specific event triggers, and explicitly disambiguates from HMAC-based providers, giving minimal conflict risk with other webhook skills.	5 / 5
	Total	20 / 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
relative_links	Relative link issues: 3 missing	Warning

	Total	15 / 16 Passed

Repository: hookdeck/webhook-skills
Path: skills/aircall-webhooks/SKILL.md
Commit: fb924f9

Reviewed: 1 day 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.