Skip to content
TrustedSkillsbeta
Back to all skills

Deployment Verification

Listed
dseirz-rgb·vlatest·devops

Automates post-deployment checks against defined criteria to ensure application functionality and stability.

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 dseirz-rgb/worker --skill deployment-verification -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

dseirz-rgb

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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: cloud.google.com.

    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.

    Hosts contacted

    cloud.google.comundeclared

    What it found

    • .kiro/skills/deployment-verification/scripts/verify-gcp.sh:45contacts cloud.google.com
      echo "Install from: https://cloud.google.com/sdk/docs/install"

  • 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 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 dseirz-rgb/worker at 5c0a3621c1.

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

Commit
5c0a3621c1
Manifest
.kiro/skills/deployment-verification/SKILL.md
Scanned
4 files, 1,265 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 automates verification of deployments to ensure they meet predefined criteria. It can check for expected services running, correct versions deployed, and validate basic functionality after a deployment is complete. The tool aims to reduce manual verification steps and improve overall deployment reliability by automating checks against established standards.

When to use it

  • After deploying a new version of an application to production.
  • When validating infrastructure changes following an automated rollout.
  • To confirm that critical services are running as expected after a server migration.
  • During the implementation of continuous delivery pipelines, providing automated feedback on deployment success.

Key capabilities

  • Automated verification checks
  • Predefined criteria validation
  • Service status monitoring
  • Version confirmation

Example prompts

  • "Verify the latest deployment to production."
  • "Check if service 'payment-processor' is running version 1.2.3."
  • "Validate that all required database migrations have completed successfully after the deployment."

Tips & gotchas

The skill requires access to deployment logs and system metrics for effective verification. Ensure appropriate permissions are configured for the AI agent to perform these checks.