chargebee-webhooks

Receive and verify Chargebee webhooks. Use when setting up Chargebee webhook handlers, debugging Basic Auth verification, or handling subscription billing events.

Quality

79%

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/chargebee-webhooks/SKILL.md

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.

Highly actionable content with three complete runnable implementations and good reference structure, weakened by triplicated auth logic across frameworks and broken example-directory links. Conciseness is the main drag from otherwise strong execution.

Suggestions

Consolidate the three framework implementations: show one full Basic Auth example and summarize only the framework-specific differences for Next.js and FastAPI to remove duplicated logic.

Remove the tangential 'If you later need raw body access (e.g., for HMAC signature verification with other providers)' block, since it describes a different provider's pattern and is not relevant to Chargebee's Basic Auth.

Create the referenced examples/express, examples/nextjs, and examples/fastapi directories (or remove the Examples links), so no progressive-disclosure pointers are broken.

Dimension	Reasoning	Score
Conciseness	Three near-identical full Basic Auth implementations (Express, Next.js, FastAPI) plus a tangential HMAC note for 'other providers' duplicate the same logic and pad the body, fitting 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the lean 4.	3 / 5
Actionability	Provides three complete, copy-paste-ready implementations plus env var config, a local-dev command, and an event-type table, matching 'fully executable; copy-paste ready code covering the common cases.'	5 / 5
Workflow Clarity	The verify-auth-then-process sequence is unambiguous in each example with an explicit 401 checkpoint, but no abstracted numbered workflow and idempotency/error feedback loops are delegated to another skill, fitting 'clear sequence with most checkpoints present; minor validation gaps.'	4 / 5
Progressive Disclosure	Clear overview with well-signaled, one-level-deep references to real files (overview.md, setup.md, verification.md), but the 'Examples' section links to examples/express\|nextjs\|fastapi/ directories that do not exist, a minor organization gap that keeps it below 5.	4 / 5
	Total	16 / 20 Passed

Description

83%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, well-constructed description that states concrete capabilities and provides an explicit 'Use when...' trigger clause covering setup, debugging, and event handling. Its only weakness is minor overlap risk with other billing-provider webhook skills on shared 'billing events' language.

Dimension	Reasoning	Score
Specificity	Names the Chargebee webhook domain and several concrete actions ('setting up Chargebee webhook handlers, debugging Basic Auth verification, or handling subscription billing events'), matching the 'lists several specific actions; minor gaps' anchor rather than the comprehensive 5 or the 1-2-action 3.	4 / 5
Completeness	Explicitly answers both what ('Receive and verify Chargebee webhooks') and when ('Use when setting up Chargebee webhook handlers, debugging Basic Auth verification, or handling subscription billing events') with concrete trigger phrases, matching the 5 anchor.	5 / 5
Trigger Term Quality	Includes natural terms users would say ('Chargebee webhooks', 'webhook handlers', 'Basic Auth verification', 'subscription billing events'); good coverage but not the comprehensive synonym/extension breadth of the 5 anchor, and stronger than the 'some relevant keywords' 3.	4 / 5
Distinctiveness Conflict Risk	The named provider 'Chargebee' gives a clear niche, but the shared 'subscription billing events' trigger language overlaps sibling billing-webhook skills (stripe, paddle), fitting 'mostly distinct; minor overlap risk' rather than the minimal-conflict 5.	4 / 5
	Total	17 / 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/chargebee-webhooks/SKILL.md
Commit: daaf3db

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.