Azure Devops
ListedHelps 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
Run this in your project
terminal$ npx skills add notmyself/claude-stack-dotnet --skill azure-devops -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
notmyself
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.
Automated safety checks
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.msundeclaredWhat it found
- .claude/skills/azure-devops/SKILL.md:30contacts aka.ms
curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash
No pipe-to-shell installers: failed
Runs code fetched at install time in 1 place.
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/SKILL.md:30remote 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 notmyself/claude-stack-dotnet at d5467b4b06.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- d5467b4b06
- Scanned
- 1 file, 479 lines
About this skill
What it does
This skill allows AI agents to interact with Azure DevOps. Specifically, it enables querying work items (like tasks and bugs), retrieving build information, and managing pipelines within an Azure DevOps organization. The agent can be used to automate reporting, track progress, or even trigger pipeline runs based on specific conditions.
When to use it
- Automated Reporting: Generate daily/weekly reports summarizing the status of work items in a project.
- Pipeline Monitoring: Check the status of a build pipeline and alert if failures occur.
- Work Item Tracking: Retrieve all bugs assigned to a specific user or with a particular tag.
- Release Management: Trigger a release pipeline based on successful completion of a development branch merge.
Key capabilities
- Querying work items (tasks, bugs)
- Retrieving build information
- Managing pipelines
Example prompts
- "What is the status of build pipeline 'MyPipeline'?"
- "List all open bugs assigned to user '[email protected]'."
- "Trigger release pipeline 'ReleasePipeline' in Azure DevOps."
Tips & gotchas
- Requires appropriate credentials and permissions within your Azure DevOps organization. Ensure the AI agent has access to the necessary resources.