CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

acuity-scheduling-webhooks

Receive and verify Acuity Scheduling webhooks. Use when setting up Acuity Scheduling webhook handlers, debugging X-Acuity-Signature verification, or handling appointment actions like scheduled, rescheduled, canceled, changed, and order.completed.

Quality

87%

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

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.

High-quality body: exemplary verification guidance with executable code, a useful event table, and clean one-level reference files. The main issues are dangling examples/ links, a handler workflow that leans on an external skill's links instead of inline steps, and cross-promotional sections that cost tokens without aiding the task.

Suggestions

Fix or remove the examples/express/, examples/nextjs/, and examples/fastapi/ links — these directories are absent from the bundle, so the promised "complete handlers with tests" are unreachable.

Inline a short numbered handler sequence (verify raw body -> parse form body -> dispatch on action -> fetch appointment by id) with the duplicate-request check as an explicit checkpoint, instead of deferring the sequence to the linked webhook-handler-patterns skill.

Trim the "Related Skills" list and "Recommended" section to a line or two each (or move them to a reference file) to reduce non-task token spend.

DimensionReasoningScore

Conciseness

The technical core (verification, event table, env vars, tunnel command) is dense and assumes competence — no padding explaining what webhooks or HMAC are. However, the "Related Skills" list (7 entries), the "Recommended" cross-promotion section, and the "When to Use" section duplicating the frontmatter description are trimmable non-task content.

4 / 5

Actionability

The inline verification function is complete and copy-paste ready (constant-time comparison, missing-header guard), and the body adds the exact Express middleware config, the env var, a runnable tunnel command, the form-field payload shape, and the fetch-full-appointment guidance — covering the common cases for this skill.

5 / 5

Workflow Clarity

Key ordering is explicit ("Parse it only after verifying", using the raw body before form parsing) plus a dispatch table and a duplicate-request/idempotency warning. But the full handler sequence is only described in the linked webhook-handler-patterns skill's bullet list rather than as inline sequenced steps with checkpoints, so it falls short of the top anchor.

4 / 5

Progressive Disclosure

Good structure: a lean overview with three real, well-signaled, one-level-deep reference files (overview.md, setup.md, verification.md) listed with descriptions. However, the body links examples/express/, examples/nextjs/, and examples/fastapi/ for "complete handlers with tests", and none of those paths exist in the bundle, which is more than a minor organization gap and prevents a 5.

4 / 5

Total

17

/

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: concrete capabilities, an explicit 'Use when' clause with real trigger scenarios, and provider-specific terms that make it highly distinguishable. The only improvement space is slightly broader natural-language synonym coverage.

DimensionReasoningScore

Specificity

"Receive and verify Acuity Scheduling webhooks" plus "setting up... webhook handlers", "debugging X-Acuity-Signature verification", and "handling appointment actions like scheduled, rescheduled, canceled, changed, and order.completed" lists several concrete actions with exact header and event names. It sits above the 1-2-action anchor but is not fully comprehensive (e.g., no mention of replying/responding or fetching appointment details), so not a 5.

4 / 5

Completeness

It explicitly answers what ("Receive and verify Acuity Scheduling webhooks") and when ("Use when setting up... handlers, debugging X-Acuity-Signature verification, or handling appointment actions like...") with concrete trigger phrases, matching the top anchor's pattern exactly.

5 / 5

Trigger Term Quality

Natural phrases users would say are present: "webhook handlers", "X-Acuity-Signature verification", "signature verification failing" context, and the five event action names. A few natural variations (e.g., "booking notifications", "appointment webhook") are missing, keeping it below the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

"Acuity Scheduling" names a specific SaaS provider with provider-specific triggers (X-Acuity-Signature, Acuity event actions), giving it a clear niche with minimal conflict risk against related scheduling/webhook skills.

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/acuity-scheduling-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.