Skip to content
TrustedSkillsbeta
Back to all skills

Deployment Runbook

Checked
pfangueiro·vlatest·devops·MIT

Automates deployment tasks using pre-defined runbooks, streamlining releases and reducing manual errors.

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 pfangueiro/claude-code-agents --skill deployment-runbook -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

pfangueiro

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 pfangueiro/claude-code-agents at c4f343a89f.

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

Commit
c4f343a89f
Manifest
.claude/skills/deployment-runbook/SKILL.md
Scanned
2 files, 864 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 allows an AI agent to execute deployment runbooks, automating complex release processes. It can handle tasks such as updating configuration files, running database migrations, and triggering infrastructure updates based on predefined steps. The skill aims to streamline deployments and reduce manual intervention in the release pipeline.

When to use it

  • Automating a new feature rollout to production environments.
  • Performing routine maintenance or security patches during off-peak hours.
  • Executing disaster recovery procedures after an incident.
  • Ensuring consistent deployment steps across multiple environments (dev, staging, prod).

Key capabilities

  • Runbook execution
  • Configuration file updates
  • Database migration management
  • Infrastructure triggering

Example prompts

  • "Execute the 'release-v1.2' runbook."
  • "Start the deployment process for the 'backend' service, following the standard runbook."
  • "Run the database migrations outlined in the 'post-deploy' section of the runbook."

Tips & gotchas

The skill requires access to the relevant infrastructure and configuration repositories. Ensure proper permissions are configured before using this skill to avoid deployment failures or unintended consequences.