Skip to content
TrustedSkillsbeta
Back to all skills

Deployment Observability Smoke

Checked
jsonlee12138·vlatest·devops

Automates deployment verification via smoke tests and provides real-time observability dashboards for rapid issue detection.

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 deployment, 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 jsonlee12138/easy-deployment --skill deployment -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

jsonlee12138

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

    Only contacts known or declared hosts: 127.0.0.1.

    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

    127.0.0.1local

  • 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 jsonlee12138/easy-deployment at 4cef41f034.

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

Commit
4cef41f034
Manifest
skills/deployment/SKILL.md
Scanned
4 files, 1,188 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 the execution of smoke tests against deployed applications. It retrieves deployment information, identifies relevant endpoints for testing, and runs predefined checks to verify basic functionality after a new deployment. The results are then aggregated and presented in a clear format, allowing for rapid assessment of deployment success.

When to use it

  • Automated Verification: After deploying a new version of an application, automatically run smoke tests to quickly confirm core features are working as expected.
  • Incident Response: During incidents or suspected issues with deployed applications, rapidly execute smoke tests to isolate the problem area.
  • Continuous Integration/Continuous Delivery (CI/CD): Integrate this skill into your CI/CD pipelines for automated validation of deployments before promoting them to production.
  • Post-Rollback Validation: After a rollback occurs, run smoke tests to ensure the previous stable version is functioning correctly.

Key capabilities

  • Retrieval of deployment information
  • Identification of relevant endpoints for testing
  • Execution of predefined smoke test checks
  • Aggregation and presentation of test results

Example prompts

  • "Run smoke tests against the latest deployment of the 'order-service'."
  • "Execute a full suite of smoke tests on the staging environment."
  • "Show me the results of the last smoke test run for the 'payment-gateway' application."

Tips & gotchas

  • Requires access to deployment metadata and endpoint definitions. Ensure the AI agent has appropriate permissions and configuration to retrieve this information.