kienbui1995/magic-powers/ado-pipelines-ops
Claude Code and agent skill by kienbui1995/magic-powers
- community
Checking that the SKILL.md file is still in the repository.
Use when managing Azure DevOps pipeline infrastructure — self-hosted agent pools, service connections, variable groups, secure files, environments, approvals, and pipeline resource governance.
Install
npx vskill@latest install kienbui1995/magic-powers/ado-pipelines-opsSKILL.md
The same SKILL.md was published earlier as kienbui1995/magic-powers/ado-pipelines-ops.
ADO Pipelines Operations & Infrastructure
When to Use
- Setting up self-hosted agent pools and registering agents
- Creating and managing service connections (Azure, GitHub, Docker, etc.)
- Managing variable groups and secure files (Library)
- Configuring deployment environments with approvals and checks
- Auditing and governing pipeline resource access
Core Jobs
1. Agent Pool Management
Self-hosted agent registration:
Agent pool types:
- Microsoft-hosted — managed, fresh VM per job, no maintenance, costs per parallel job
- Self-hosted — your VMs, full control, pre-installed tools, behind firewall access, no per-minute cost
- Scale set agents — Azure VMSS auto-scales based on demand (best of both)
2. Service Connections
Service connection types and use cases:
| Type | Use case | |
|---|---|---|
| Azure Resource Manager | Deploy to Azure (App Service, AKS, etc.) | |
| Docker Registry | Push/pull container images | |
| GitHub | Checkout private repos, trigger from GitHub | |
| Kubernetes | Deploy to AKS/any cluster | |
| Generic | Custom REST APIs, webhooks |
Security: Grant "Project Collection Build Service" only — not broad contributor access.
3. Library — Variable Groups & Secure Files
Link to Azure Key Vault:
- Variable group → Link secrets from Azure Key Vault → select secrets
- Requires service connection with Key Vault access
- Secrets auto-refresh on pipeline run
4. Environments & Approvals
Add approval check via UI: Environment → Approvals and checks → Add → Approvals
- Set approvers, timeout (default 30 days), instructions
- Allow pipeline to self-approve: disable for prod
Environment resources: VMs and Kubernetes clusters can be registered as resources for deployment target tracking.
Key Concepts
- Agent pool — collection of agents that can run pipeline jobs
- Service connection — authenticated connection to external service (Azure, Docker, GitHub)
- Variable group — shared variables across multiple pipelines (vs pipeline-specific variables)
- Secure file — binary files (certificates, provisioning profiles) stored encrypted
- Environment — logical target (dev/staging/prod) with history, approvals, and resource tracking
- Scale set agents — auto-scaling agent pool backed by Azure VMSS
Checklist
- [ ] Self-hosted agents using service account (not personal user)?
- [ ] Service connections using service principal (not personal PAT)?
- [ ] Service principal has minimum required permissions only?
- [ ] Secrets in Key Vault-linked variable group (not hardcoded in pipeline)?
- [ ] Production environment has approval gates?
- [ ] Agent capabilities documented (for pool selection in pipeline YAML)?
Key Outputs
- Agent pools registered and agents online
- Service connections created with least-privilege service principals
- Variable groups with Key Vault linking for secrets
- Environments with approvals for production
Output Format
- 🔴 Critical — service connection using personal PAT (breaks on offboarding), no approval on production environment, secrets hardcoded in pipeline YAML
- 🟡 Warning — all pipelines using single service connection (no isolation), no environment resource tracking, variable groups without Key Vault
- 🟢 Suggestion — use scale set agents for variable workloads, link variable groups to Key Vault, add Exclusive Lock check for sequential deployments
Anti-Patterns
- Service connections using personal user credentials (offboarding breaks pipelines)
- Granting service principal Owner role (least-privilege: Contributor on specific RG)
- Secrets in pipeline variables instead of Key Vault-linked variable groups
- No approval gates on production deployments
- Running pipeline agents as root/admin (security risk)
Integration
ado-security-policies— control who can create/modify service connections and pipeline resourcesado-api-cli— automate service connection creation and variable group managementazure-devops-pipelines— YAML authoring that consumes the infrastructure set up here
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/ado-pipelines-ops/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/kienbui1995/magic-powers/ado-pipelines-ops)