Skip to content
TrustedSkillsbeta
Back to all skills

Status

Checked
zerodeploy-dev·vlatest·devops

This "Status" skill provides real-time system and application health updates, ensuring proactive monitoring and rapid issue resolution.

Repository

Install on your platform

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

Installs under a different name. Its SKILL.md names it zerodeploy-status, not the name it is listed under, so the command below uses that name.
  1. 1

    Run this in your project

    terminal
    $ npx skills add zerodeploy-dev/skills --skill zerodeploy-status -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

zerodeploy-dev

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 zerodeploy-dev/skills at c135984441.

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

Commit
c135984441
Manifest
zerodeploy-status/SKILL.md
Scanned
1 file, 65 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 zerodeploy-dev-status skill provides a way to check the deployment status of applications within the Zerodeploy platform. It allows agents to query for the current state (e.g., deploying, succeeded, failed) and retrieve relevant details about deployments. This enables automated monitoring and proactive responses to deployment events.

When to use it

  • Automated Monitoring: Regularly check the status of a critical application deployment as part of an automated workflow.
  • Incident Response: Quickly determine if a recent deployment is causing issues by querying its status.
  • Progress Reporting: Provide updates on deployment progress to stakeholders or other systems.
  • Conditional Actions: Trigger subsequent actions (e.g., rollback, scaling) based on the outcome of a deployment.

Key capabilities

  • Query deployment status
  • Retrieve deployment details
  • Supports various deployment states (deploying, succeeded, failed)

Example prompts

  • "What is the current status of deployment 'my-app-v1'?"
  • "Check if the last deployment to production was successful."
  • "Give me details about the most recent deployment attempt for service 'api'."

Tips & gotchas

  • Requires access to the Zerodeploy platform and appropriate permissions.
  • Deployment names are case-sensitive; ensure accurate spelling when querying.