circuit-breaker-setup
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill circuit-breaker-setupCircuit Breaker Setup - Auto-activating skill for API Integration. Triggers on: circuit breaker setup, circuit breaker setup Part of the API Integration skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without explaining what it does or when to use it. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance. The only redeeming quality is that 'circuit breaker' is a somewhat distinctive technical term.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Implements circuit breaker patterns to handle API failures gracefully, configure retry policies, set failure thresholds, and manage fallback responses.'
Include a 'Use when...' clause with natural trigger scenarios, e.g., 'Use when implementing fault tolerance, handling API timeouts, preventing cascade failures, or when the user mentions resilience patterns.'
Expand trigger terms to include variations users might naturally say: 'fault tolerance', 'API resilience', 'retry logic', 'failure handling', 'timeout management', 'fallback patterns'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only mentions 'Circuit Breaker Setup' without describing any concrete actions. It doesn't explain what the skill actually does - no verbs describing capabilities like 'implements', 'configures', 'monitors', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' guidance is just a duplicate trigger phrase. There's no explicit 'Use when...' clause explaining scenarios for selection. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('circuit breaker setup' listed twice) and overly narrow. Missing natural variations users might say like 'fault tolerance', 'retry logic', 'API resilience', 'failure handling', or 'fallback patterns'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'circuit breaker' is fairly specific to a particular software pattern, which provides some distinctiveness. However, the vague 'API Integration' category and lack of detail could cause overlap with other API-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template/placeholder that provides zero actionable content about circuit breakers. It describes what the skill should do but contains no actual implementation guidance, code examples, configuration patterns, or technical details. The entire content could be replaced with a single sentence: 'This skill helps with circuit breakers' without losing any information.
Suggestions
Add executable code examples showing circuit breaker implementation (e.g., using resilience4j, Polly, or custom implementation with state machine)
Include concrete configuration examples with specific thresholds (failure count, timeout duration, half-open retry logic)
Define a clear workflow: 1) Identify failure scenarios, 2) Configure thresholds, 3) Implement fallback behavior, 4) Add monitoring/alerting
Provide specific patterns for common use cases (HTTP client circuit breaker, database connection circuit breaker, message queue circuit breaker)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler with no actionable information. | 1 / 3 |
Actionability | No concrete code, commands, or specific implementation details are provided. The skill describes what it does abstractly ('provides step-by-step guidance') but never actually provides any guidance, examples, or executable content. | 1 / 3 |
Workflow Clarity | No workflow is defined. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, no sequence, and no validation checkpoints for implementing a circuit breaker. | 1 / 3 |
Progressive Disclosure | The content is a shallow placeholder with no real information to disclose. There are no references to detailed documentation, no links to implementation guides, and no structured navigation to deeper content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
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 | 11 / 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.