BF resilient-connections
Patterns for building resilient API clients and real-time connections with retry logic, circuit breakers, and graceful degradation. Use when building production systems that need to handle failures. Triggers on retry logic, circuit breaker, connection resilience, exponential backoff, API client, fault tolerance.
Patterns for building resilient API clients and real-time connections with retry logic, circuit breakers, and graceful degradation.
As a process F 45/100 · Will not run — References files that are not bundled: ../../meta/realtime-dashboard/, ../realtime-react-hooks/, ../websocket-hub-patterns/
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../meta/realtime-dashboard/ - warning
missing-refreference to a missing file: ../realtime-react-hooks/ - warning
missing-refreference to a missing file: ../websocket-hub-patterns/
Process rating: all ten parameters 45/100
- 0Tools and files. 3 referenced file(s) missing: ../../meta/realtime-dashboard/, ../realtime-react-hooks/, ../websocket-hub-patterns/
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (resilient-connections) differs from the folder (resiliant-connections)
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 12 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 1663 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 313: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 12 items
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.