Implement Exa reliability patterns including circuit breakers, idempotency, and graceful degradation. Use when building fault-tolerant Exa integrations, implementing retry strategies, or adding resilience to production Exa services. Trigger with phrases like "exa reliability", "exa circuit breaker", "exa idempotent", "exa resilience", "exa fallback", "exa bulkhead".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill exa-reliability-patterns84
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 (circuit breakers, idempotency, graceful degradation), provides explicit 'Use when' guidance, and includes comprehensive trigger phrases. The Exa-specific focus creates a distinct niche with minimal conflict risk.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'circuit breakers, idempotency, and graceful degradation' along with 'retry strategies' and 'resilience to production Exa services'. These are concrete, actionable patterns. | 3 / 3 |
Completeness | Clearly answers both what ('Implement Exa reliability patterns including circuit breakers, idempotency, and graceful degradation') and when ('Use when building fault-tolerant Exa integrations, implementing retry strategies, or adding resilience') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'exa reliability', 'exa circuit breaker', 'exa idempotent', 'exa resilience', 'exa fallback', 'exa bulkhead'. Good coverage of domain-specific terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Exa reliability patterns with distinct triggers like 'exa circuit breaker' and 'exa bulkhead'. The Exa-specific focus and reliability engineering niche make it unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides excellent, production-ready code examples for multiple reliability patterns with good organization and external references. However, it could be more concise by removing the Prerequisites section and redundant Instructions, and would benefit from explicit validation/testing steps for each pattern implementation.
Suggestions
Remove the Prerequisites section - Claude understands circuit breakers and doesn't need to be told about library installation
Replace the generic 'Instructions' section with pattern-specific validation steps (e.g., 'Test circuit breaker: call with failing function, verify circuit opens after threshold')
Add a brief testing/verification example showing how to confirm each pattern is working correctly
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary sections like the Prerequisites list (Claude knows what circuit breakers are) and the verbose 'Instructions' section that merely restates what the code already demonstrates. | 2 / 3 |
Actionability | Provides fully executable TypeScript code for each pattern - circuit breaker, idempotency, bulkhead, DLQ, and health checks. Code is copy-paste ready with proper imports and realistic configurations. | 3 / 3 |
Workflow Clarity | The 'Instructions' section lists steps but lacks validation checkpoints. For reliability patterns involving production systems, there should be explicit verification steps (e.g., 'Test circuit breaker by simulating failures', 'Verify DLQ processing with test entries'). | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections for each pattern, a concise overview, and appropriate external references (Martin Fowler, Opossum docs, Exa guide). Links to related skill (exa-policy-guardrails) for next steps. | 3 / 3 |
Total | 10 / 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 | |
Table of Contents
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.