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

82%

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

65%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 highly actionable with complete, executable code and a clear step sequence, but it is longer than necessary for a SKILL.md overview: full implementations are inlined while two reference files go unmentioned, and the batch/retry workflows lack explicit validation checkpoints.

Suggestions

Move the full class implementations into references/implementation.md and reference them from SKILL.md, keeping only concise snippets and the combined pipeline inline to improve progressive disclosure and conciseness.

Add explicit validation checkpoints to the batch/risky workflows — e.g., verify circuit state before each batch, confirm DLQ retry results, and a validate→fix→retry loop for failed submissions.

Link the existing references/implementation-guide.md and references/implementation.md from the body (e.g., in a Resources or Advanced section) so the bundle structure is actually navigable.

Dimension	Reasoning	Score
Conciseness	The body is ~325 lines of mostly executable TypeScript with brief intent statements and no conceptual padding, but five full classes are inlined in SKILL.md when the bundle's references/ files suggest this implementation could be split out — fitting 'mostly efficient but could be tightened'.	2 / 3
Actionability	Provides complete, executable TypeScript classes (CreditCircuitBreaker, ClayDLQ, WebhookHealthMonitor, ClayWithFallback, reliableEnrich) using real APIs (fetch, AbortSignal.timeout) — copy-paste ready with specific parameters.	3 / 3
Workflow Clarity	Steps are clearly numbered (Step 1–5) culminating in a combined pipeline, but batch/risky operations (DLQ retries, credit spending) lack explicit validation checkpoints or validate→fix→retry feedback loops, which caps workflow clarity at 2 per the batch-operations guideline.	2 / 3
Progressive Disclosure	The body inlines five full classes and never signals the two existing references/ files (implementation-guide.md, implementation.md), matching the score-2 anchor 'content that should be separate is inline' and 'references present but not clearly signaled'.	2 / 3
	Total	9 / 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 strong: third-person voice, concrete capabilities, an explicit 'Use when' clause, and a list of natural trigger phrases scoped to a distinct clay-reliability niche. It cleanly answers what the skill does and when to use it.

Dimension	Reasoning	Score
Specificity	Names the Clay reliability domain and lists multiple concrete techniques — 'circuit breakers, dead letter queues, and graceful degradation' — matching the score-3 anchor for multiple specific concrete actions.	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 to enrichment workflows').	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would say — 'clay reliability', 'clay circuit breaker', 'clay resilience', 'clay fallback', 'clay fault tolerance', 'clay dead letter queue' — with good coverage of variations for the niche.	3 / 3
Distinctiveness Conflict Risk	All triggers are clay-prefixed and target a specific reliability niche, making it clearly distinguishable and unlikely to fire for the wrong skill.	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/clay-pack/skills/clay-reliability-patterns/SKILL.md
Commit: 4c47e33

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