Skip to content
TrustedSkillsbeta
Back to all skills

Reliability Strategy Builder

Checked
patricio0312rev·vlatest·other·MIT

This skill generates a tailored reliability strategy based on your input, streamlining planning and boosting operational resilience.

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 patricio0312rev/skills --skill reliability-strategy-builder -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

patricio0312rev

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 patricio0312rev/skills at 79ea6af485.

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

Commit
79ea6af485
Manifest
architecture/reliability-strategy-builder/SKILL.md
Scanned
1 file, 271 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

The reliability-strategy-builder skill enables AI agents to generate comprehensive, actionable plans for maintaining system uptime and minimizing downtime. It analyzes specific infrastructure components to propose targeted strategies for ensuring operational continuity.

When to use it

  • Drafting incident response playbooks for critical production environments.
  • Designing maintenance schedules that balance availability with necessary updates.
  • Creating redundancy protocols for single points of failure in cloud architectures.
  • Developing disaster recovery procedures aligned with business continuity goals.

Key capabilities

  • Generates structured reliability strategies based on system context.
  • Focuses on actionable steps to prevent and mitigate outages.
  • Adapts recommendations to specific infrastructure types and constraints.

Example prompts

  • "Create a reliability strategy for a microservices architecture running on Kubernetes with high availability requirements."
  • "Generate an incident response plan for a database cluster experiencing intermittent latency spikes."
  • "Outline a maintenance window strategy that ensures zero downtime during a critical application update."

Tips & gotchas

Ensure you provide detailed context about your current infrastructure stack, as the generated strategy relies heavily on understanding specific technologies and constraints. The output is strategic guidance; it may require manual validation against real-time operational data before implementation.