CtrlK
BlogDocsLog inGet started
Tessl Logo

customerio-webhooks-events

Implement Customer.io webhook and reporting event handling. Use when processing email delivery events, click/open tracking, bounce handling, or streaming to a data warehouse. Trigger: "customer.io webhook", "customer.io events", "customer.io delivery status", "customer.io bounces", "customer.io open tracking".

72

Quality

90%

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

80%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is lean and highly actionable with executable code throughout, but it under-serves progressive disclosure by not referencing its own implementation-guide.md and caps workflow clarity by omitting validation feedback loops for destructive batch operations.

Suggestions

Link to references/implementation-guide.md from the body (e.g., "See implementation-guide.md for the BullMQ queue and reporting API") so the bundle is clearly signaled.

Add an explicit validate→fix→retry checkpoint around suppression/profile mutations (e.g., retry failed cio.suppress calls with backoff, and verify suppression succeeded) to support the destructive batch operations.

Replace the static Error Handling table with a feedback loop that re-verifies the signature and re-processes failed events rather than only listing one-shot fixes.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence: code carries load-bearing comments ("Respond 200 immediately — process async to avoid timeouts", "MUST be before any JSON body parser") and never explains what webhooks or HMAC are, so every token earns its place.

3 / 3

Actionability

All five steps provide fully executable TypeScript with real imports, concrete env vars, and route paths — copy-paste ready rather than pseudocode, matching the top anchor.

3 / 3

Workflow Clarity

Steps are clearly sequenced, but batch/destructive operations (suppression on bounce/spam, profile mutation, async processing) lack a validate→fix→retry feedback loop and the dedup pruning is incomplete, capping clarity at 2 per the destructive-operations guideline.

2 / 3

Progressive Disclosure

A references/implementation-guide.md bundle exists but is never linked or signaled from the body, and the ~300-line body is largely inline rather than an overview pointing to it — structure exists but navigation is not clearly signaled.

2 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 specific, complete, and distinctive, covering concrete actions with explicit "Use when" and "Trigger" guidance. It cleanly satisfies all four dimensions.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Implement Customer.io webhook and reporting event handling", "processing email delivery events, click/open tracking, bounce handling, or streaming to a data warehouse" — matching the anchor for listing several specific concrete actions.

3 / 3

Completeness

Clearly answers both what ("Implement Customer.io webhook and reporting event handling") and when ("Use when processing email delivery events...") with explicit triggers, matching the top anchor.

3 / 3

Trigger Term Quality

An explicit "Trigger:" clause gives natural phrases users would say ("customer.io webhook", "customer.io events", "customer.io delivery status", "customer.io bounces", "customer.io open tracking"), with good coverage rather than jargon.

3 / 3

Distinctiveness Conflict Risk

The Customer.io-specific niche and its distinct triggers make it unlikely to fire for an unrelated skill, matching the clear-niche anchor.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-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.