Skip to content
TrustedSkillsbeta
Back to all skills

Azure Devops

Listed
rysweet·vlatest·cloud

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

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 rysweet/amplihack --skill azure-devops -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 failed 2 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.

  • No undeclared network calls: failed

    Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: aka.ms.

    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.

    Hosts contacted

    aka.msundeclared

    What it found

    • .claude/skills/azure-devops/authentication.md:28contacts aka.ms
      curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash
    • amplifier-bundle/skills/azure-devops/authentication.md:28contacts aka.ms
      curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash

  • No pipe-to-shell installers: failed

    Runs code fetched at install time in 2 places.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

    What it found

    • .claude/skills/azure-devops/authentication.md:28remote script piped into a shell
      curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash
    • amplifier-bundle/skills/azure-devops/authentication.md:28remote script piped into a shell
      curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash

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

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

Commit
84424457d5
Manifest
.claude/skills/azure-devops/SKILL.md
Scanned
18 files, 4,180 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

The azure-devops skill enables AI agents to interact directly with Azure DevOps services, allowing them to manage work items, pipelines, and repositories programmatically. It facilitates automation of CI/CD workflows and integration of development processes within the Microsoft ecosystem.

When to use it

  • Automating build and deployment pipelines for cloud-native applications.
  • Creating or updating work items (bugs, user stories) based on code changes.
  • Integrating Azure DevOps with other tools like GitHub Actions or Jenkins.
  • Managing release definitions and environment configurations dynamically.

Key capabilities

  • Trigger Azure Pipelines via REST API or CLI commands.
  • Query and manipulate work items in Azure Boards.
  • Access repository data from Azure Repos.
  • Execute scripts within pipeline agents for custom logic.

Example prompts

  • "Create a new release pipeline that deploys my app to staging when the main branch is pushed."
  • "List all open bugs in project 'MyApp' and assign them to the developer who last modified the related code."
  • "Run the 'build-and-test' pipeline and notify me via email upon completion."

Tips & gotchas

Ensure your AI agent has proper authentication (e.g., PAT or service principal) with sufficient permissions to access Azure DevOps resources. Some advanced features may require additional setup, such as installing the Azure DevOps CLI locally or configuring webhook listeners for real-time event handling.