Skip to content
TrustedSkillsbeta
Back to all skills

Devops Engineer

Checked
jordanhubbard·vlatest·devops·MIT

Automates infrastructure provisioning, CI/CD pipelines, and configuration management using best practices for efficient deployments.

Repository

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 jordanhubbard/loom --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

jordanhubbard

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 jordanhubbard/loom at 2faf49470c.

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

Commit
2faf49470c
Manifest
personas/default/devops-engineer/SKILL.md
Scanned
3 files, 126 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 provides DevOps engineering expertise to an AI agent. It can automate infrastructure provisioning, manage deployments using CI/CD pipelines, and troubleshoot system issues by analyzing logs and configurations. The agent can leverage this skill to streamline development workflows and ensure application reliability.

When to use it

  • Automating the setup of a new development environment with specific software versions.
  • Creating a basic CI/CD pipeline for deploying an application to a staging server.
  • Diagnosing errors in a deployed application by analyzing system logs.
  • Generating infrastructure-as-code configurations (e.g., Terraform) based on requirements.

Key capabilities

  • Infrastructure provisioning
  • CI/CD pipeline management
  • Log analysis and troubleshooting
  • Configuration management

Example prompts

  • "Create a Dockerfile for my Python application."
  • "Generate a basic Terraform script to provision an AWS EC2 instance."
  • "Help me debug this error message from my Jenkins build."

Tips & gotchas

The agent's effectiveness depends on the clarity and specificity of your prompts. Providing context about existing infrastructure or desired configurations will improve results.