Receive and verify Chargebee webhooks. Use when setting up Chargebee webhook handlers, debugging Basic Auth verification, or handling subscription billing events.
88
81%
Does it follow best practices?
Impact
100%
1.08xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with explicit trigger guidance and good keyword coverage for the Chargebee domain. The main weakness is that the capability description could be more specific about concrete actions beyond 'receive and verify'. The distinctiveness is excellent due to the specific product name and authentication method mentioned.
Suggestions
Expand the capabilities with more concrete actions like 'parse event payloads', 'validate webhook signatures', or 'handle subscription lifecycle events (created, renewed, cancelled)'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Chargebee webhooks) and some actions (receive, verify, handling), but lacks comprehensive concrete actions like 'parse event payloads', 'validate signatures', or 'process subscription changes'. | 2 / 3 |
Completeness | Clearly answers both what (receive and verify Chargebee webhooks) and when (explicit 'Use when' clause covering setup, debugging, and handling scenarios). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms: 'Chargebee', 'webhooks', 'webhook handlers', 'Basic Auth', 'subscription billing events'. These are terms users would naturally use when working with Chargebee integrations. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche with 'Chargebee' as a distinct product name, combined with 'Basic Auth verification' and 'subscription billing events'. Unlikely to conflict with generic webhook or billing skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent actionability - providing complete, executable code for three major frameworks. The progressive disclosure is strong with clear navigation to reference materials and examples. However, it could be more concise by trimming the verbose warning box and extensive related skills list, and would benefit from an explicit setup/testing workflow with validation steps.
Suggestions
Condense the event types warning into a single line like '⚠️ Verify exact event names in your Chargebee dashboard - names vary by API version'
Add a brief numbered workflow for initial setup: 1. Set env vars, 2. Deploy handler, 3. Configure in Chargebee dashboard, 4. Test with Hookdeck CLI, 5. Verify events received
Consider moving the extensive 'Related Skills' section to a separate file or trimming to just the most relevant 2-3 skills
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary verbosity like the lengthy warning box about event names and extensive related skills list that could be trimmed. The inline comments explaining Basic Auth vs HMAC are helpful but slightly verbose. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code for three frameworks (Express.js, Next.js, FastAPI). Includes complete implementations with proper error handling, environment variable setup, and local development commands. | 3 / 3 |
Workflow Clarity | The code examples show clear verification flow, but there's no explicit multi-step workflow for setting up webhooks end-to-end. Missing validation checkpoints for testing the webhook handler works correctly before deploying. | 2 / 3 |
Progressive Disclosure | Excellent structure with quick-start code upfront, clear references to detailed materials (overview, setup, verification), framework-specific examples in separate directories, and well-organized related skills section. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
f8a4801
Table of Contents
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.