clay-reliability-patterns

Build fault-tolerant Clay integrations with circuit breakers, dead letter queues, and graceful degradation. Use when building production Clay pipelines that need resilience, implementing retry strategies, or adding fault tolerance to enrichment workflows. Trigger with phrases like "clay reliability", "clay circuit breaker", "clay resilience", "clay fallback", "clay fault tolerance", "clay dead letter queue".

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 content is highly actionable and concise, with complete executable TypeScript across five sequenced steps. Its weaknesses are a missing validation feedback loop in the batch workflow and under-signaled progressive disclosure — the bundled reference files exist but are not linked from the body.

Suggestions

Add an explicit validate-then-retry checkpoint to the reliable-enrich workflow (e.g. verify webhook delivery / credit accounting before marking a lead processed) to raise workflow_clarity.

Link the existing references/ files (implementation-guide.md, implementation.md) from the body with one-level-deep pointers, and move the full Step 1-4 class implementations into them so SKILL.md stays a concise overview.

Add brief inline comments or a checklist in Step 5 describing how to verify the combined pipeline end-to-end before production rollout.

Dimension	Reasoning	Score
Conciseness	The body is dense executable TypeScript with minimal prose padding and no explanation of concepts Claude already knows; every section adds concrete implementation detail. Not score 2 because it avoids unnecessary exposition and assumes competence throughout.	3 / 3
Actionability	Provides fully executable, copy-paste-ready TypeScript classes with file paths (e.g. 'src/clay/circuit-breaker.ts') and concrete integration in Step 5. Not score 2 because the code is complete rather than pseudocode.	3 / 3
Workflow Clarity	Steps 1-5 are clearly sequenced, but the batch submission/dead-letter workflow lacks explicit validation checkpoints or a validate-fix-retry feedback loop. Not score 3 because the guidelines cap workflow_clarity at 2 when batch operations omit validation steps; not score 1 because the sequence and error-handling table are present.	2 / 3
Progressive Disclosure	The body embeds ~250 lines of full class implementations inline that could live in separate files, and the existing references/ directory files (implementation-guide.md, implementation.md) are never signaled or linked from the body. Not score 3 because references are not clearly navigated and content that should be split is inline; not score 1 because the content is section-organized 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 well-crafted: concrete capabilities, explicit trigger guidance, and a distinctive Clay resilience niche. It scores at the top of every dimension with no fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions/patterns: 'circuit breakers, dead letter queues, and graceful degradation', matching the top anchor's 'multiple specific concrete actions'. Not score 2 because it goes beyond naming a domain plus a few actions into a comprehensive concrete list.	3 / 3
Completeness	Explicitly answers both 'what' ('Build fault-tolerant Clay integrations with circuit breakers, dead letter queues, and graceful degradation') and 'when' ('Use when building production Clay pipelines that need resilience, implementing retry strategies, or adding fault tolerance'). Not score 2 because the 'Use when' trigger guidance is explicit and present.	3 / 3
Trigger Term Quality	Provides natural trigger phrases users would say ('clay reliability', 'clay circuit breaker', 'clay resilience', 'clay fallback', 'clay fault tolerance', 'clay dead letter queue'), giving good coverage of common variations. Not score 2 because it covers multiple natural phrasings rather than a single keyword.	3 / 3
Distinctiveness Conflict Risk	Targets a clear Clay-specific niche with distinct clay-prefixed triggers, making conflict with unrelated skills unlikely. Not score 2 because the domain and triggers are specific enough to avoid overlap.	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: 6e3a65f

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