circuit-breaker-setup
Circuit Breaker Setup - Auto-activating skill for API Integration. Triggers on: circuit breaker setup, circuit breaker setup Part of the API Integration skill category.
36
3%
Does it follow best practices?
Impact
100%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/16-api-integration/circuit-breaker-setup/SKILL.mdQuality
Discovery
7%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 description is essentially a title repeated as a trigger term with no substantive content. It fails to describe what the skill actually does (e.g., configure failure thresholds, implement half-open states, wrap API calls), and provides no meaningful guidance for when Claude should select it over other API-related skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Implements circuit breaker patterns for API calls, configures failure thresholds, manages open/half-open/closed states, and adds fallback responses for failing services.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about handling API failures, fault tolerance, retry logic, service resilience, or preventing cascading failures in distributed systems.'
Remove the duplicate trigger term and replace with varied natural language terms users might actually say, such as 'fault tolerance', 'API retry', 'failure handling', 'resilience pattern', 'cascading failure prevention'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the concept 'Circuit Breaker Setup' without describing any concrete actions. There are no specific capabilities listed such as configuring thresholds, handling failures, implementing retry logic, or monitoring states. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' guidance is essentially just restating the skill name as a trigger. There is no explicit 'Use when...' clause with meaningful context. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'circuit breaker setup' repeated twice. There are no natural variations users might say like 'fault tolerance', 'retry pattern', 'API failure handling', 'resilience pattern', or 'service degradation'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'circuit breaker' is a somewhat specific pattern, the description is so vague that it could overlap with other API integration skills. The mention of 'API Integration skill category' provides some context but doesn't clearly carve out a distinct niche. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a placeholder with no substantive content. It describes what it would do in abstract terms but provides zero actionable guidance on circuit breaker implementation—no code, no patterns (e.g., states, thresholds, fallback strategies), no configuration examples, and no workflow. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples showing circuit breaker implementation (e.g., using a library like pybreaker, resilience4j, or a custom implementation with states: closed, open, half-open).
Define a clear workflow: 1) Configure thresholds (failure count, timeout), 2) Implement state transitions, 3) Add fallback handlers, 4) Validate with test scenarios simulating failures.
Remove all meta-description sections (Purpose, When to Use, Example Triggers, Capabilities) and replace with actual technical content—configuration parameters, code patterns, and integration examples.
Add references to advanced topics like monitoring circuit breaker state, tuning thresholds, and combining with retry/backoff patterns, either inline or via linked files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is almost entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are empty padding that teach Claude nothing it doesn't already know. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No code examples, no specific commands, no actual circuit breaker implementation patterns, no configuration snippets. The entire skill describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow steps are defined at all. Despite claiming to provide 'step-by-step guidance,' the skill contains no actual steps, no sequence, and no validation checkpoints for implementing a circuit breaker. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic description with no meaningful structure. There are no references to detailed materials, no links to implementation guides, and the sections that exist (Purpose, When to Use, Capabilities) are all meta-information rather than organized technical content. | 1 / 3 |
Total | 4 / 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
b8a3b3e
- 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.