clay-reliability-patterns
Implement Clay reliability patterns including circuit breakers, idempotency, and graceful degradation. Use when building fault-tolerant Clay integrations, implementing retry strategies, or adding resilience to production Clay services. Trigger with phrases like "clay reliability", "clay circuit breaker", "clay idempotent", "clay resilience", "clay fallback", "clay bulkhead".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill clay-reliability-patterns81
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 excels across all dimensions. It clearly specifies concrete reliability patterns, provides explicit 'Use when' guidance, and includes a comprehensive list of natural trigger phrases. The Clay-specific terminology throughout ensures distinctiveness from generic reliability or resilience skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'circuit breakers, idempotency, and graceful degradation' as well as 'retry strategies' and 'resilience to production Clay services'. These are concrete, actionable patterns. | 3 / 3 |
Completeness | Clearly answers both what ('Implement Clay reliability patterns including circuit breakers, idempotency, and graceful degradation') and when ('Use when building fault-tolerant Clay integrations, implementing retry strategies, or adding resilience'). Includes explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'clay reliability', 'clay circuit breaker', 'clay idempotent', 'clay resilience', 'clay fallback', 'clay bulkhead'. Good coverage of domain-specific terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to 'Clay' platform reliability patterns with distinct triggers like 'clay circuit breaker' and 'clay bulkhead'. The Clay-specific prefix on all triggers makes conflicts with generic reliability skills unlikely. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive, executable reliability patterns for Clay integrations with strong actionability through complete TypeScript implementations. However, it's somewhat verbose for a skill file, includes unnecessary prerequisite explanations, and the workflow section lacks validation checkpoints critical for implementing production reliability patterns.
Suggestions
Remove the Prerequisites section - Claude already understands circuit breaker patterns and library requirements can be inferred from imports
Add validation checkpoints to the Instructions section, e.g., 'Test circuit breaker by simulating failures before proceeding to Step 2'
Consider moving detailed implementations (DLQ, Health Check) to a separate CLAY-RELIABILITY-ADVANCED.md file, keeping SKILL.md as a concise overview with the most essential patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary elements like the Prerequisites section explaining concepts Claude already knows (circuit breaker pattern understanding) and some verbose comments in code that could be trimmed. | 2 / 3 |
Actionability | Provides fully executable TypeScript code for each pattern - circuit breaker, idempotency, bulkhead, timeout, graceful degradation, and DLQ. Code is copy-paste ready with proper imports and complete implementations. | 3 / 3 |
Workflow Clarity | The Instructions section provides a 4-step sequence but lacks validation checkpoints between steps. For reliability patterns involving production systems, there should be explicit verification steps (e.g., 'test circuit breaker triggers correctly before proceeding'). | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is quite long (~200 lines of code) and could benefit from splitting detailed implementations into separate reference files. The Resources section provides good external links, and Next Steps points to related skills. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.