azure-devops
Skill1 starsChanged 2 months agoMITView on GitHub
Azure DevOps end-to-end — repos, YAML pipelines, boards, artifact feeds, secure files, service connections, deployment gates.
12 other projects use a version of this.
Adopted by
Most recently taken up by
- OpenHands/extensionstheir own version, first seen Oct 8, 2026
- fuseraft/skillstheir own version, first seen Sep 20, 2026
- apideck-libraries/api-skillstheir own version, first seen Aug 13, 2026
- vanenshi/skillstheir own version, first seen Aug 5, 2026
- sanjay3290/ai-skillstheir own version, first seen Jul 6, 2026
- MicrosoftDocs/Agent-Skillstheir own version, first seen Jun 16, 2026
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- MicrosoftDocs/Agent-Skills★ 808same name
- sanjay3290/ai-skills★ 452same name
- OpenHands/extensions★ 167same name
- apideck-libraries/api-skills★ 4same name
- GusY2K/y2k-labs★ 3same name
- ckifonidis/claude-code-skils★ 2same name
- vanenshi/skills★ 2same name
- fuseraft/skills★ 1same name
- tuannv14/claude-team-toolkit★ 1same name
- carobbarlightshow628/y2k-labs★ 0same name
2 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- decideSkill
- deliverSkill
- researchSkill
- sprintSkill
- superteam-coachSkill
- superteam-coachSkill
- azure-ai-foundry-devSkill
- bc-mcpSkill
- copilot-studio-buildSkill
- decideSkill
- deliverSkill
- erp-connectorsSkill
- fabric-appsSkill
- fabric-medallionSkill
- fabric-notebooksSkill
- fabric-onelakeSkill
- fabric-power-biSkill
- find-skillsSkill
- mirrorSkill
- ontologySkill
- playwrightSkill
- researchSkill
- sap-btp-agentsSkill
- semantic-reasoningSkill
- semantic-searchSkill
- sprintSkill
- superteam-coachSkill
- superteam-demoSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Repo setup: Create the repo in the ADO project.
- Very specific: line 21
Artifact feeds: Create a project-scoped feed for internal packages (npm, NuGet, Python, Universal).
- Very specific: line 23
Deployment gates: Add environment approvals for deploy-test and deploy-prod.
- Distinctive: line 32
Every service connection uses Workload Identity Federation when the target supports it — no long-lived secrets
- Distinctive: line 33
Every prod deployment has at least one human approval gate — automated-only prod is forbidden
“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/azure-devops — Delivery Infrastructure on Azure DevOps
Azure DevOps is the delivery plumbing under most Avanade Fabric and Azure engagements. This skill stands up the repo, pipelines, boards, artifacts, and secure secrets story cleanly on day one, so nothing gets bolted on later.
When to invoke
- New Fabric or Azure engagement kicking off with an ADO project
- Orbit is designing CI/CD for a repo before code lands
- Deployment gates or approvals need to be added to a promotion path
- Service connections or secure files need to be provisioned or audited
Steps
- Repo setup. Create the repo in the ADO project. Set default branch to
main, require pull requests, require linked work item on PR, require at least one reviewer, require build validation. Enable branch policies before first push. - YAML pipelines. Author
azure-pipelines.ymlat repo root. Define stages:build→test→deploy-dev→deploy-test→deploy-prod. Use templates (extends: template:) to share stages across repos. Pin agent pool and image versions — never usewindows-latestin production. - Boards and work items. Choose the process (Agile / Scrum / Basic / CMMI). Configure area paths and iterations. Wire work-item auto-linking on PR completion. States must reflect the team's actual workflow — do not accept defaults blindly.
- Artifact feeds. Create a project-scoped feed for internal packages (npm, NuGet, Python, Universal). Set upstream sources for public registries. Consumer pipelines authenticate via the built-in
System.AccessToken. - Secure files and service connections. Store certificates and other sensitive files in Library → Secure files. Service connections (Azure RM, GitHub, ACR, Kubernetes) use Workload Identity Federation (OIDC) — verify current guidance at author time. Never use long-lived secrets when federation is available.
- Deployment gates. Add environment approvals for
deploy-testanddeploy-prod. Add automated gates (query Azure Monitor, invoke REST, Azure Function) where policy requires. Approvers are Entra groups, not individuals.
Deliverable format
azure-pipelines.yml— root pipeline plus shared templates underpipelines/templates/docs/branch-policies.md— screenshot or note of enforced policies per branchdocs/service-connections.md— list of connections with scope and federation type- Environment approvals configured and screenshotted
Non-negotiables
- Every service connection uses Workload Identity Federation when the target supports it — no long-lived secrets
- Every prod deployment has at least one human approval gate — automated-only prod is forbidden
- Pipelines pin agent image versions — no floating
-latesttags in production - Branch policies enforce PR + build validation before merge — no direct pushes to
main
References
- Azure DevOps — pipelines YAML schema
- Azure DevOps — branch policies
- Workload Identity Federation for Azure Pipelines
- Environments and approvals
- Superteam ADR — MS Fabric skills pack
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.