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 markpitt/claude-skills --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
markpitt
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 1 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 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
- skills/azure-devops/resources/artifacts-packages.md:211npm install straight from a URL
npm install @{scope}/mypackage --registry https://pkgs.dev.azure.com/{organization}/{project}/_packaging/{feedName}/npm/registry/
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.
Pinned to a commit: passed
Scanned markpitt/claude-skills at 43b02eee90.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 43b02eee90
- Manifest
- skills/azure-devops/SKILL.md
- Scanned
- 8 files, 3,068 lines
About this skill
What it does
This skill enables AI agents to interact directly with Azure DevOps services, allowing them to manage work items, pipelines, and repositories programmatically. It bridges the gap between automated workflows and your existing DevOps infrastructure for streamlined project management.
When to use it
- Automating the creation and tracking of bugs or feature requests within a team's backlog.
- Triggering CI/CD pipeline executions based on specific code changes or schedule events.
- Retrieving build status reports or deployment logs without manual dashboard access.
- Updating sprint progress or moving work items through state transitions automatically.
Key capabilities
- Manage Azure DevOps resources via API integration.
- Execute and monitor build pipelines.
- Handle work item lifecycle operations (create, update, close).
- Interact with Git repositories for version control tasks.
Example prompts
- "Create a new bug in the 'Frontend' project with priority high and assign it to Sarah."
- "Run the 'Deploy-Production' pipeline and wait for the build status to change."
- "List all open work items tagged with 'urgent' in the current sprint."
Tips & gotchas
Ensure your AI agent has valid Azure DevOps personal access tokens or service principal credentials configured before attempting operations. Complex multi-step workflows may require breaking tasks into smaller, sequential prompts if the agent hits token limits.