Skip to content
TrustedSkillsbeta
Back to all skills

Devops Engineer

Checked
claudchereji·vlatest·devops

Automates infrastructure provisioning, CI/CD pipelines, and configuration management tasks for faster, reliable deployments.

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 claudchereji/visualverses --skill devops-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

claudchereji

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 claudchereji/visualverses at 5971350ec1.

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

Scanned
1 file, 281 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 allows AI agents to perform DevOps tasks, including automating infrastructure provisioning and deployment pipelines. It can assist with managing cloud resources, configuring CI/CD systems, and troubleshooting application deployments. The agent can also help in identifying and resolving bottlenecks within the development workflow.

When to use it

  • Automating server setup for a new web application.
  • Creating a continuous integration/continuous deployment (CI/CD) pipeline for an existing project.
  • Troubleshooting issues with a failed software release.
  • Managing infrastructure as code using tools like Terraform or Ansible.

Key capabilities

  • Infrastructure provisioning
  • Deployment pipeline automation
  • Cloud resource management
  • CI/CD configuration
  • Application deployment troubleshooting

Example prompts

  • "Create a Terraform script to provision three EC2 instances in AWS."
  • "Set up a CI/CD pipeline using Jenkins for my Python application."
  • "Why did my last deployment fail? Check the logs and identify the root cause."

Tips & gotchas

The agent's effectiveness depends on providing clear instructions and access to relevant configuration files or cloud provider credentials. Be specific with your requests, as DevOps tasks often require detailed steps.