kienbui1995/magic-powers/ado-artifacts
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 Artifacts — feed creation and permissions, upstream sources, retention policies, package promotion across views, and connecting build pipelines to artifact feeds.
Install
npx vskill@latest install kienbui1995/magic-powers/ado-artifactsSKILL.md
The same SKILL.md was published earlier as kienbui1995/magic-powers/ado-artifacts.
ADO Artifacts Feed Management
When to Use
- Creating artifact feeds for npm, NuGet, Maven, Python, or Universal packages
- Configuring upstream sources (npm, PyPI, Maven Central, NuGet.org)
- Setting feed permissions and visibility
- Implementing retention policies to control storage costs
- Promoting packages between views (prerelease → release)
Core Jobs
1. Feed Creation & Configuration
Feed scope:
- Project-scoped — isolated to project, better access control
- Organization-scoped — shared across all projects (use for shared libraries)
Views: @local (all versions) → @prerelease (tested) → @release (production-ready). Promote packages between views as quality gates.
2. Upstream Sources
Configure via UI: Feed → Settings → Upstream sources → Add upstream
Common upstreams:
| Package type | Upstream | Use | |
|---|---|---|---|
| npm | npmjs.com | Public npm packages | |
| NuGet | NuGet Gallery | Public .NET packages | |
| PyPI | pypi.org | Public Python packages | |
| Maven | Maven Central | Public Java packages |
Key benefit: Developers use ONE feed URL, packages from upstream auto-cached. Enables audit and governance of public package versions.
3. Permissions
Feed permissions levels:
- Owner — full control (feed settings, delete)
- Contributor — publish packages
- Collaborator — save packages from upstream
- Reader — install packages only
4. Retention Policies
Configure: Feed → Settings → Retention policies
- Set max versions per package (e.g., 10 latest)
- Auto-delete older versions
- Does NOT delete packages in
@releaseview (protected)
5. Connect Pipeline to Feed
Key Concepts
- Feed — package repository; project or org scoped
- View — subset of feed packages at a quality level (@local, @prerelease, @release)
- Upstream source — proxy to public registry; caches packages for audit and reliability
- Promotion — moving a package to a higher quality view (prerelease → release)
- Retention policy — auto-cleanup of old package versions
Checklist
- [ ] Project-scoped feeds for team isolation, org-scoped for shared libraries?
- [ ] Upstream sources configured (developers use only feed URL, not direct public registry)?
- [ ] Build service has Contributor, developers have Reader/Collaborator?
- [ ] Retention policy set to prevent storage bloat?
- [ ] Release view protected from auto-deletion?
Key Outputs
- Feeds created with correct scope and permissions
- Upstream sources configured for all package types used
- Retention policies preventing unbounded storage growth
- Pipeline authentication to feeds configured
Output Format
- 🔴 Critical — no upstream sources (developers using public registries directly — supply chain risk), build service has Owner role
- 🟡 Warning — no retention policy (storage costs grow unboundedly), org-scoped feed when project isolation needed
- 🟢 Suggestion — use views for quality gates (prerelease/release), automate package promotion in release pipeline
Anti-Patterns
- Developers configuring .npmrc/.nuget to pull from public registries directly (bypasses feed, supply chain risk)
- No retention policy on feeds with frequent publishing (GB of storage wasted)
- Single feed for all package types and teams (poor governance)
Integration
ado-pipelines-ops— pipeline service connections used to authenticate to feedsado-security-policies— feed permissions align with project security modelado-api-cli— automate package publishing and promotion
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-artifacts/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-artifacts)