Skip to content
TrustedSkillsbeta
Back to all skills

Spring Boot Resilience4J

Checked
giuseppe-trisciuoglio·vlatest·backend·MIT

This skill provides resilient Spring Boot applications using Resilience4J, enhancing fault tolerance and improving system stability under load.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add giuseppe-trisciuoglio/developer-kit --skill spring-boot-resilience4j -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

giuseppe-trisciuoglio

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned giuseppe-trisciuoglio/developer-kit-claude-code at fe73fb33a0.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
fe73fb33a0
Manifest
plugins/developer-kit-java/skills/spring-boot-resilience4j/SKILL.md
Scanned
4 files, 1,658 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides Spring Boot applications with resilience capabilities using Resilience4j. It allows developers to build more robust and fault-tolerant systems by implementing features like circuit breakers, rate limiters, and retry mechanisms. This helps prevent cascading failures and improves the overall stability of microservices architectures.

When to use it

  • Handling external service dependencies: When your application relies on other services that might be unreliable or experience downtime.
  • Implementing fallback strategies: To provide a graceful degradation of functionality when an upstream dependency fails.
  • Protecting against overload: To prevent overwhelming downstream services by limiting the rate of requests.
  • Automating retry logic: For transient errors, automatically retrying operations can improve success rates without manual intervention.

Key capabilities

  • Circuit Breakers: Prevents repeated calls to a failing service.
  • Rate Limiters: Controls the number of requests made to a downstream service within a specific time window.
  • Retry Mechanisms: Automatically retries failed operations.

Example prompts

  • "Implement circuit breaking for the payment service."
  • "Add a retry mechanism with exponential backoff for database calls."
  • "Configure rate limiting to 10 requests per second for the external API."

Tips & gotchas

This skill requires familiarity with Spring Boot and Java. Ensure that Resilience4j dependencies are correctly added to your project's build file (e.g., pom.xml or build.gradle).