CtrlK
BlogDocsLog inGet started
Tessl Logo

aiprise-webhooks

Receive and verify AiPrise webhooks (callbacks). Use when setting up AiPrise identity/KYC/KYB callback handlers, debugging X-HMAC-SIGNATURE verification, or handling verification results like APPROVED, DECLINED, REVIEW, and UNKNOWN.

67

Quality

81%

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

75%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 well-structured and actionable, leading with a complete verification code sample and deferring deeper detail to one-level-deep reference files. The main gaps are the missing example directories referenced in the body and the multi-step handler workflow being externalized rather than sequenced inline.

Suggestions

Either include the referenced examples/express, examples/nextjs, and examples/fastapi directories in the bundle or remove/qualify those links so navigation is not broken.

Add a brief inline verify → parse → handle-idempotently sequence (or a short checklist) rather than relying entirely on the external webhook-handler-patterns skill for the core workflow.

Trim the Attribution and Recommended/Related Skills sections or move them to a single consolidated footer to push the body closer to fully lean.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence ('AiPrise signs every callback with HMAC-SHA256 over the raw request body'), with inline comments that earn their place; minor extras like the attribution block keep it just shy of the fully lean anchor 5.

4 / 5

Actionability

Provides a complete, copy-paste-ready verifyAiPriseWebhook implementation with timingSafeEqual and error handling, plus concrete env-var and tunnel commands; route wiring and event dispatch are deferred to external examples rather than shown inline.

4 / 5

Workflow Clarity

The core verify-then-compare flow is clear with an explicit failure path (catch returning false), and the handler sequence is pointed to via the recommended webhook-handler-patterns skill; the multi-step verify→parse→handle-idempotently sequence is not laid out inline, leaving minor checkpoint gaps.

4 / 5

Progressive Disclosure

SKILL.md is a well-signaled overview pointing one level deep to real files (references/overview.md, setup.md, verification.md); however the body also links examples/express, examples/nextjs, and examples/fastapi which are not present in the bundle, a minor organization gap.

4 / 5

Total

16

/

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.

The description is third-person, concise, and cleanly answers both what the skill does and when to use it with concrete, brand-specific triggers. It is strong across all four dimensions with only minor coverage gaps in specificity and trigger terms.

DimensionReasoningScore

Specificity

Quotes 'Receive and verify AiPrise webhooks (callbacks)' plus 'setting up... callback handlers, debugging X-HMAC-SIGNATURE verification, or handling verification results' name several concrete actions; minor gaps versus the fully comprehensive anchor 5.

4 / 5

Completeness

Explicit 'what' ('Receive and verify AiPrise webhooks') paired with an explicit 'Use when...' clause listing concrete triggers, satisfying the anchor for clearly answering both what and when.

5 / 5

Trigger Term Quality

Includes natural synonyms 'webhooks (callbacks)', 'X-HMAC-SIGNATURE', 'KYC/KYB', and the result enum 'APPROVED, DECLINED, REVIEW, UNKNOWN'; good coverage but a few natural phrasings users might say are absent, so not a 5.

4 / 5

Distinctiveness Conflict Risk

Tied to the specific AiPrise brand and its bespoke 'X-HMAC-SIGNATURE' header with KYC/KYB result enum, giving a clear niche with minimal overlap risk against other 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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 missing

Warning

Total

15

/

16

Passed

Repository
hookdeck/webhook-skills
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.