spring-boot-resilience4j
This skill should be used when implementing fault tolerance and resilience patterns in Spring Boot applications using the Resilience4j library. Apply this skill to add circuit breaker, retry, rate limiter, bulkhead, time limiter, and fallback mechanisms to prevent cascading failures, handle transient errors, and manage external service dependencies gracefully in microservices architectures.
Install with Tessl CLI
npx tessl i github:giuseppe-trisciuoglio/developer-kit --skill spring-boot-resilience4jOverall
score
83%
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 strong skill description that clearly identifies its domain (Resilience4j with Spring Boot), lists specific capabilities (circuit breaker, retry, rate limiter, etc.), and provides explicit trigger guidance. The description uses proper third-person voice and includes natural keywords that users working with microservices resilience would actually use.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'circuit breaker, retry, rate limiter, bulkhead, time limiter, and fallback mechanisms' along with clear purposes like 'prevent cascading failures, handle transient errors, and manage external service dependencies.' | 3 / 3 |
Completeness | Clearly answers both what (implementing various resilience patterns with Resilience4j) and when ('should be used when implementing fault tolerance and resilience patterns in Spring Boot applications'). Has explicit trigger guidance at the start. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'fault tolerance', 'resilience', 'Spring Boot', 'Resilience4j', 'circuit breaker', 'retry', 'rate limiter', 'bulkhead', 'microservices', 'cascading failures', 'transient errors'. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche targeting specifically Resilience4j with Spring Boot for fault tolerance patterns. The combination of library name, framework, and specific pattern types makes it highly distinctive and unlikely to conflict with generic error handling or other resilience skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
73%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with excellent code examples covering all major Resilience4j patterns. The progressive disclosure is exemplary with clear references to supporting documentation. Main weaknesses are some verbosity in introductory sections and missing validation/verification steps for confirming patterns are correctly applied.
Suggestions
Add a validation step after setup (e.g., 'Verify AOP proxy creation by checking logs for Resilience4j initialization messages' or a simple test endpoint)
Remove or condense the 'Resilience4j is a lightweight...' paragraph as Claude already knows library characteristics
Add a troubleshooting checkpoint: 'If annotations aren't working, verify @EnableAspectJAutoProxy and that the bean is Spring-managed (not created with new)'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary explanation (e.g., 'Resilience4j is a lightweight, composable library...' paragraph) and the 'When to Use' section repeats information Claude would infer from context. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples for all patterns with complete Java classes, YAML configurations, and proper imports. Each pattern has concrete implementation examples with realistic service scenarios. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but lacks explicit validation checkpoints. No guidance on verifying circuit breaker configuration works correctly before production, or how to test that patterns are actually applied (e.g., checking AOP proxies are created). | 2 / 3 |
Progressive Disclosure | Excellent structure with clear overview sections and well-signaled one-level-deep references to configuration-reference.md, testing-patterns.md, and examples.md. Content is appropriately split between main skill and reference files. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
63%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 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 |
license_field | 'license' field is missing | 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 | 10 / 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.