Skip to content
TrustedSkillsbeta
Back to all skills

Azure Devops Cli

Checked
rysweet·vlatest·cloud

Helps with Azure, DevOps as part of deploying and managing cloud infrastructure workflows.

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 rysweet/amplihack --skill azure-devops-cli -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

rysweet

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 rysweet/amplihack at 84424457d5.

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

Scanned
20 files, 8,959 lines
Copies in repo
2 — all of them scanned
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 interact with Azure DevOps using the command line interface (CLI). It can automate tasks such as creating work items, managing pipelines, and retrieving build information. The agent can execute CLI commands directly, enabling scripting and automation within the Azure DevOps environment.

When to use it

  • Automated Build Management: Trigger builds or deployments based on external events or conditions.
  • Work Item Creation & Updates: Automatically create new work items (e.g., bugs, tasks) and update their status.
  • Pipeline Status Checks: Regularly check the status of Azure DevOps pipelines and report any failures.
  • Retrieve Build Details: Get information about specific builds, such as logs or test results.

Key capabilities

  • Execute Azure DevOps CLI commands
  • Automate build pipeline management
  • Work item creation and modification
  • Retrieval of build status and details

Example prompts

  • "Create a new task in Azure DevOps called 'Update documentation' assigned to John Doe."
  • "Check the status of the 'Release Pipeline 1' in Azure DevOps."
  • "Get the logs for build number 12345 in Azure DevOps."

Tips & gotchas

  • Requires appropriate permissions within your Azure DevOps organization.
  • The agent needs access to an environment with the Azure DevOps CLI installed and configured.