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".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

80%

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

The body is highly actionable and lean, with complete executable TypeScript across the full webhook pipeline. Its weaknesses are missing explicit validation feedback loops for destructive/batch operations and a bundle file (implementation-guide.md) that is present but never linked from SKILL.md.

Suggestions

Add an explicit validate->fix->retry checkpoint in the webhook setup workflow, e.g. a step to send a test event and confirm signature verification + handler routing before going live.

Reference references/implementation-guide.md from the body (e.g. a 'Full implementation guide' pointer) so the bundled detail is discoverable rather than orphaned, or move the inline code blocks into that file.

Add a short validation step before suppressing users on bounce/spam (e.g. confirm the event_id is not already suppressed) to guard the destructive batch operation.

Dimension	Reasoning	Score
Conciseness	Lean prose with no padding explaining concepts Claude already knows; nearly all content is executable code or actionable tables, and every section earns its place. Not a 2 because there is no unnecessary explanatory filler to tighten.	3 / 3
Actionability	Provides complete, copy-paste-ready TypeScript for types, signature verification, routing handlers, Express setup, and BigQuery streaming, with real header names and env vars.	3 / 3
Workflow Clarity	Steps 1-5 are clearly sequenced, but there are no explicit validation/feedback-loop checkpoints for risky batch operations (user suppression, dedup), only an after-the-fact Error Handling table. Not a 3 because the rubric caps workflow clarity at 2 when destructive/batch workflows lack validate->fix->retry loops; not a 1 because the sequence is present and unambiguous.	2 / 3
Progressive Disclosure	Sections are organized, but the entire implementation is inlined in SKILL.md while a bundle file (references/implementation-guide.md) exists but is never referenced or signaled from the body. Not a 3 because the reference is not one-level-deep and clearly linked; not a 1 because there is reasonable section structure rather than a monolithic wall.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 well-triggered with natural keywords and an explicit Use-when clause. Third-person/imperative voice is used correctly throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: 'webhook and reporting event handling', 'processing email delivery events, click/open tracking, bounce handling', and 'streaming to a data warehouse', matching the score-3 anchor that lists several specific concrete actions.	3 / 3
Completeness	Explicitly answers both what ('Implement Customer.io webhook and reporting event handling') and when via a clear 'Use when...' clause plus an explicit 'Trigger:' list.	3 / 3
Trigger Term Quality	Provides natural terms a user would say ('customer.io webhook', 'customer.io events', 'customer.io bounces', 'customer.io open tracking', 'delivery status') with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Scoped narrowly to Customer.io webhook/event handling with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 02d6341

Reviewed: 5 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.