customerio-webhooks-events
Implement Customer.io webhook handling. Use when processing delivery events, handling callbacks, or integrating Customer.io event streams. Trigger with phrases like "customer.io webhook", "customer.io events", "customer.io callback", "customer.io delivery status".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill customerio-webhooks-events74
Quality
66%
Does it follow best practices?
Impact
89%
1.41xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/customerio-pack/skills/customerio-webhooks-events/SKILL.mdDiscovery
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 well-structured skill description with excellent trigger term coverage and clear 'Use when' guidance. The main weakness is that the capability descriptions are somewhat general ('handling callbacks', 'integrating event streams') rather than listing specific concrete actions the skill performs. The explicit trigger phrases section is a strong differentiator.
Suggestions
Add more specific concrete actions like 'parse webhook payloads', 'validate webhook signatures', 'handle bounce/open/click events', or 'map delivery statuses to internal states'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Customer.io webhook handling) and mentions some actions (processing delivery events, handling callbacks, integrating event streams), but lacks concrete specific actions like 'parse webhook payloads', 'validate signatures', or 'store event data'. | 2 / 3 |
Completeness | Clearly answers both what (implement webhook handling, process delivery events, handle callbacks, integrate event streams) and when (explicit 'Use when' clause plus 'Trigger with phrases' section providing clear activation guidance). | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'customer.io webhook', 'customer.io events', 'customer.io callback', 'customer.io delivery status'. Good coverage of variations users might naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific to Customer.io platform with distinct triggers. Unlikely to conflict with generic webhook skills or other marketing platform integrations due to explicit 'customer.io' prefix on all trigger terms. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable high-level workflow for Customer.io webhook implementation but critically lacks actionable code examples. The content describes what to build rather than showing how to build it, delegating all concrete implementation to an external reference file. The Examples section is particularly weak, offering only placeholder text with no actual examples.
Suggestions
Add at least one concrete, executable code example for signature verification (the most critical security step) directly in the skill body
Replace the placeholder Examples section with actual input/output examples showing webhook payload structure and expected handler responses
Add validation checkpoints between steps, such as 'Test signature verification with a sample payload before proceeding to Step 4'
Remove the redundant 'Output' section or convert it into a verification checklist with specific tests to confirm each component works
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary sections like the vague 'Examples' at the end that add no value, and the 'Output' section that just restates what the steps produce. | 2 / 3 |
Actionability | The skill describes what to do at a high level but provides no concrete code, commands, or executable examples. Steps like 'Implement HMAC-SHA256 signature verification' and 'Use BullMQ with Redis' are abstract instructions without actual implementation. | 1 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but there are no validation checkpoints or feedback loops for verifying webhook signatures work correctly or that events are being processed properly before moving to the next step. | 2 / 3 |
Progressive Disclosure | Good structure with a clear overview, well-organized sections, and appropriate reference to an external implementation guide for detailed code. The single-level reference to the implementation guide is well-signaled. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- 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.