customerio-common-errors

Diagnose and fix Customer.io common errors. Use when troubleshooting API errors, delivery failures, campaign issues, or SDK exceptions. Trigger: "customer.io error", "customer.io not working", "debug customer.io", "customer.io 401", "customer.io 429".

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.

A highly actionable, concise troubleshooting reference with excellent code examples and checklists. Its main gaps are the absence of a single explicit end-to-end diagnostic workflow and the failure to link the existing reference bundle files from SKILL.md.

Suggestions

Add a short top-level 'Diagnostic workflow' section (e.g., 1. Reproduce error 2. Read HTTP status code 3. Match to status table / error section 4. Apply fix 5. Verify with curl) to give an explicit sequenced flow with checkpoints.

Link the existing bundle files from SKILL.md (e.g., 'See [implementation.md](references/implementation.md) for the error classification map and [implementation-guide.md](references/implementation-guide.md) for per-error cause/solution details') so the progressive disclosure structure is actually navigable.

Reconcile the 'Next Steps' pointer to customerio-debug-bundle with the real bundle files present, or move that detail into a referenced file one level deep.

Dimension	Reasoning	Score
Conciseness	The body is lean: a compact HTTP status table, WRONG/CORRECT code blocks, and brief fix notes with no padding explaining what Customer.io is or basic concepts, so every token earns its place as in the score-3 anchor.	3 / 3
Actionability	It provides fully executable TypeScript snippets, copy-paste curl diagnostic commands, and a ready-to-use withBackoff retry function, matching the score-3 "copy-paste ready" anchor.	3 / 3
Workflow Clarity	Strong checklists (Error 3, Error 7), verification curl commands, and a retry feedback loop exist, but the skill is organized as an error catalog with no single explicit top-level diagnostic sequence tying the steps together, fitting the score-2 anchor where checkpoints are present but the overall sequence is implicit.	2 / 3
Progressive Disclosure	The body is well-sectioned, but the two provided bundle files in references/ (implementation.md, implementation-guide.md) are never linked or signaled from SKILL.md, and detailed content that could be split out remains inline, matching the score-2 anchor of structure present but references not clearly signaled.	2 / 3
	Total	10 / 12 Passed

Description

90%

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, third-person description with explicit trigger guidance and a clear what/when structure. The only weakness is that the capability verbs (diagnose/fix) are limited rather than a rich list of concrete actions.

Dimension	Reasoning	Score
Specificity	"Diagnose and fix Customer.io common errors" names the domain and two actions and enumerates error categories (API errors, delivery failures, campaign issues, SDK exceptions), but it is not a list of multiple distinct concrete actions like the score-3 anchor, so it sits at the score-2 anchor.	2 / 3
Completeness	It states what ("Diagnose and fix Customer.io common errors") and explicitly when ("Use when troubleshooting API errors, delivery failures, campaign issues, or SDK exceptions") plus a Trigger clause, clearly answering both what and when.	3 / 3
Trigger Term Quality	The explicit Trigger clause lists natural user phrasings ("customer.io error", "customer.io not working", "debug customer.io", "customer.io 401", "customer.io 429") giving good coverage of terms users would actually say, matching the score-3 anchor.	3 / 3
Distinctiveness Conflict Risk	All triggers are prefixed with "customer.io" and scoped to a specific SaaS platform, carving a clear niche that is unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 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: about 18 hours 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.