Skip to content
TrustedSkillsbeta
Back to all skills

Deployment Engineer

Listed
neversight·vlatest·devops

Automates infrastructure provisioning, configuration management, and deployment pipelines for scalable, reliable applications.

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 neversight/learn-skills.dev --skill deployment-engineer -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

neversight

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

    No SKILL.md was found in the skill's directory.

    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 neversight/skills_feed at 58220bbac4.

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

Scanned
0 files
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 and streamlines software deployments. It handles tasks such as configuring infrastructure, deploying applications to various environments (staging, production), and managing rollbacks in case of issues. The tool aims to reduce manual effort and improve the reliability of release processes.

When to use it

  • You need to deploy a new version of your application to a staging environment for testing.
  • You want to automate the process of deploying code changes to production servers.
  • Your team frequently needs to roll back deployments due to errors or unexpected behavior.
  • You're looking to standardize and improve the consistency of deployment procedures across multiple projects.

Key capabilities

  • Automated infrastructure configuration
  • Deployment to staging and production environments
  • Rollback functionality
  • Standardized release processes

Example prompts

  • "Deploy version 1.2.3 of my application to the staging environment."
  • "Initiate a rollback to the previous stable deployment."
  • “Configure the infrastructure for a new microservice.”

Tips & gotchas

The skill requires access to your deployment environments and configuration files. Ensure proper permissions are granted before use, as incorrect configurations can lead to deployment failures or security vulnerabilities.