Skip to content
TrustedSkillsbeta
Back to all skills

Epic Deployment

Listed
epicweb-dev·vlatest·devops·MIT

Automates complex infrastructure provisioning and application deployments across multiple environments with detailed rollback capabilities.

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 epicweb-dev/epic-stack --skill epic-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

epicweb-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 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.

  • Declares what it does: failed

    SKILL.md frontmatter is missing 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 epicweb-dev/epic-stack at 8473afd804.

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

Scanned
1 file, 729 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 deployments to various environments. It streamlines the process of pushing code changes, configuring infrastructure, and ensuring application readiness across development, staging, and production environments. The skill aims to reduce manual effort and potential errors associated with traditional deployment workflows.

When to use it

  • Automating releases to a staging environment for testing before production.
  • Deploying updates to a live production server during off-peak hours.
  • Rolling back deployments in case of issues after a release.
  • Managing infrastructure configuration changes alongside application code.

Key capabilities

  • Automated deployment pipelines
  • Environment management (development, staging, production)
  • Infrastructure configuration
  • Rollback functionality

Example prompts

  • "Deploy the latest version of the 'webapp' to the staging environment."
  • "Initiate a rollback of the last deployment on the production server."
  • "Update the database connection string for the development environment."

Tips & gotchas

This skill requires proper configuration and access credentials for your target environments. Ensure that all necessary permissions are granted to the AI agent before attempting deployments.