customerio-reliability-patterns

Implement Customer.io reliability and fault-tolerance patterns. Use when building circuit breakers, fallback queues, idempotency, or graceful degradation for Customer.io integrations. Trigger: "customer.io reliability", "customer.io resilience", "customer.io circuit breaker", "customer.io fault tolerance".

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

Executable, lean code examples make this highly actionable and token-efficient, but all six patterns live inline in SKILL.md and the available reference files are never signaled from the body. Adding a validate→retry loop and offloading detail to the existing references would lift the weaker dimensions.

Suggestions

Link the existing references/ files from the body (e.g., 'For an alternative opossum-based circuit breaker and dead-letter/WAL patterns, see [implementation.md](references/implementation.md)') so the bundle is actually discoverable and the body can stay an overview.

Add an explicit validation/feedback loop to the resilience workflow — e.g., a numbered sequence showing how to verify the circuit recovered, drain the fallback queue, and confirm no duplicate events — to satisfy the workflow_clarity checkpoint requirement.

Trim or relocate the per-pattern full implementations into references/ and keep SKILL.md as a pattern catalog with short signatures plus the selection guide, improving progressive disclosure without losing actionability.

Dimension	Reasoning	Score
Conciseness	The body is code-forward with a single-sentence Overview and no padding explaining what a circuit breaker or Customer.io is; the Pattern Selection Guide and Reliability Checklist each earn their tokens.	3 / 3
Actionability	Each of the six patterns is a complete, copy-paste-ready TypeScript implementation (classes, imports, env usage) rather than pseudocode, with the ResilientCioClient composing them concretely.	3 / 3
Workflow Clarity	A Pattern Selection Guide and a Reliability Checklist give structure, but the body never sequences a validate→fix→retry feedback loop, which the rubric caps at 2 for batch/retry operations like the fallback queue.	2 / 3
Progressive Disclosure	Six full implementations are inlined in SKILL.md while two bundle files exist in references/ that the body never links to, matching the 'content that should be separate is inline / references not clearly signaled' anchor.	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.

A tight, third-person description that states concrete capabilities and pairs them with explicit use-when triggers scoped to Customer.io reliability. It hits all four dimensions at the top of the scale.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'circuit breakers, fallback queues, idempotency, or graceful degradation' — alongside the framing action 'Implement Customer.io reliability and fault-tolerance patterns'.	3 / 3
Completeness	Clearly answers what ('Implement Customer.io reliability and fault-tolerance patterns...') and when ('Use when building circuit breakers...') with an explicit Trigger clause, satisfying both halves.	3 / 3
Trigger Term Quality	The 'Trigger:' line gives natural phrases a user would actually say ('customer.io reliability', 'customer.io resilience', 'customer.io circuit breaker', 'customer.io fault tolerance').	3 / 3
Distinctiveness Conflict Risk	Every trigger is 'customer.io'-prefixed and scoped to reliability, carving a clear niche 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
Path: plugins/saas-packs/customerio-pack/skills/customerio-reliability-patterns/SKILL.md
Commit: 0540a62

Reviewed: about 9 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.