Skip to content
TrustedSkillsbeta
Back to all skills

Deployment Verification Agent

Checked
ratacat·vlatest·devops

Automates verification of deployments across environments, ensuring successful rollout and identifying immediate issues post-release.

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 ratacat/claude-skills --skill deployment-verification-agent -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

ratacat

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 ratacat/claude-skills at d4b471d05d.

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

Scanned
1 file, 149 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

The deployment-verification-agent automates the process of verifying deployments to ensure they meet pre-defined criteria. It can check for things like correct version numbers, expected resource availability, and successful execution of post-deployment tasks. This skill helps reduce errors and improve confidence in new releases by providing automated validation.

When to use it

  • Automated Release Verification: After a deployment pipeline completes, automatically verify the environment is as expected before promoting to production.
  • Rollback Decision Support: Use verification results to inform decisions about whether to roll back a problematic deployment.
  • Environment Consistency Checks: Regularly check environments (staging, testing) against baseline configurations.
  • Post-Deployment Testing: Execute and validate post-deployment tests like database migrations or cache invalidations.

Key capabilities

  • Automated verification checks
  • Version number validation
  • Resource availability confirmation
  • Post-deployment task execution validation

Example prompts

  • "Verify the deployment to staging environment, checking version 1.2.3 and confirming database connection."
  • "Run the post-deployment tests for release candidate 4 on the QA server."
  • "Check if all required services are running after the latest production deployment."

Tips & gotchas

The agent requires access to deployment logs and environment configuration data to perform accurate verification. Ensure appropriate permissions are granted before use.