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".
89
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is a well-crafted skill description that clearly defines its scope (fault-tolerant Clay integrations), lists specific capabilities (circuit breakers, dead letter queues, graceful degradation), and provides explicit trigger guidance with both 'Use when' and 'Trigger with' clauses. It occupies a distinct niche that minimizes conflict risk with other skills. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'circuit breakers', 'dead letter queues', 'graceful degradation', 'retry strategies', and 'fault tolerance to enrichment workflows'. These are concrete, well-defined technical capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' (build fault-tolerant Clay integrations with circuit breakers, dead letter queues, graceful degradation) and 'when' (when building production Clay pipelines that need resilience, implementing retry strategies, or adding fault tolerance). Includes explicit 'Use when' and 'Trigger with' clauses. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger phrases like 'clay reliability', 'clay circuit breaker', 'clay resilience', 'clay fallback', 'clay fault tolerance', 'clay dead letter queue'. Also includes natural terms like 'retry strategies', 'production Clay pipelines', and 'resilience'. Good coverage of terms a user would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: fault tolerance specifically for Clay integrations. The combination of 'Clay' + resilience/fault-tolerance patterns creates a clear, narrow domain that is unlikely to conflict with general resilience skills or general Clay skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with complete executable TypeScript implementations for all reliability patterns. Its main weakness is verbosity — the full class implementations for relatively standard patterns (DLQ, health monitor, circuit breaker) consume significant tokens that could be reduced by providing briefer implementations or referencing separate files. The workflow progression from individual components to combined pipeline is clear and well-organized.
Suggestions
Consider moving full class implementations to separate referenced files (e.g., circuit-breaker.ts, dlq.ts) and keeping only the key interface/usage patterns inline in SKILL.md to improve conciseness.
Trim the WebhookHealthMonitor section significantly — it's a standard pattern that Claude can generate from a brief description of the thresholds (95% healthy, 80% degraded).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill provides substantial executable code which is valuable, but is quite lengthy (~250 lines of TypeScript). Some classes like WebhookHealthMonitor are straightforward patterns Claude could generate from a brief description. The overview paragraph explaining what Clay is could be trimmed since the skill assumes production Clay usage. | 2 / 3 |
Actionability | All code examples are fully executable TypeScript with complete class implementations, concrete method signatures, and a final integration example showing how all patterns combine. The code is copy-paste ready with realistic defaults (500 credits/day, 15-minute cooldown, 5-minute health windows). | 3 / 3 |
Workflow Clarity | The 5-step sequence is logically ordered from individual patterns to combined pipeline. Each step builds on the previous, and validation/feedback loops are embedded in the code itself (circuit breaker state transitions, DLQ retry with max retries, health score thresholds). The error handling table provides clear diagnosis-to-solution mapping. | 3 / 3 |
Progressive Disclosure | The skill references external resources (clay-observability, clay-policy-guardrails) appropriately, but the main content is monolithic — all patterns are fully inlined rather than being summarized with links to separate detailed files. The DLQ and fallback implementations could be referenced rather than fully embedded. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
4dee593
- Reviewed
Table of Contents
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.