DevOps & Infra
azure-container-registry-cli - Claude MCP Skill
Manage Azure Container Registry via the az acr CLI including registries, images, cloud builds, ACR Tasks, authentication, tokens, geo-replication, and networking. Use when working with ACR, az acr commands, pushing/importing/purging container images in Azure, or when the user mentions Azure Container Registry.
SEO Guide: Enhance your AI agent with the azure-container-registry-cli tool. This Model Context Protocol (MCP) server allows Claude Desktop and other LLMs to manage azure container registry via the az acr cli including registries, images, cloud builds, acr t... Download and configure this skill to unlock new capabilities for your AI workflow.
Documentation
SKILL.md# Azure Container Registry CLI
Manage Azure Container Registry (ACR) resources using the `az acr` command group of the Azure CLI.
**CLI:** `az acr` ships with core Azure CLI ā no extension required (the `acrtransfer` extension is only needed for export/import pipelines).
## Prerequisites
```bash
# Install Azure CLI
brew install azure-cli # macOS
curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash # Linux
winget install Microsoft.AzureCLI # Windows
# Sign in and select subscription
az login
az account set --subscription {subscription-id}
```
## Quick Start
```bash
# Create a registry (SKU: Basic | Standard | Premium)
az acr create --resource-group {rg} --name {registry} --sku Standard
# Authenticate Docker/Podman against the registry
az acr login --name {registry}
# Build and push in the cloud ā no local Docker needed
az acr build --registry {registry} --image app:v1 .
# Copy an image from another registry without pull/push
az acr import --name {registry} --source mcr.microsoft.com/hello-world:latest
# List repositories and tags
az acr repository list --name {registry} --output table
az acr repository show-tags --name {registry} --repository app --orderby time_desc
# Diagnose registry connectivity and configuration
az acr check-health --name {registry} --yes
```
## Key Principles
- **Prefer `az acr build` / ACR Tasks** over local `docker build` + `docker push`: builds run in Azure, work without a local daemon, and integrate with triggers.
- **Prefer `az acr import`** to move images between registries: it is server-side, faster, and requires no local storage.
- **Never enable the admin user for production** ā use Microsoft Entra identities (RBAC roles `AcrPull`/`AcrPush`, or `Container Registry Repository Reader`/`Writer` on ABAC-enabled registries), repository-scoped tokens, or managed identities.
- **Premium-only features**: geo-replication, private endpoints, retention policies, connected registries, agent pools. (Repository-scoped tokens work in all tiers; zone redundancy is automatic in all tiers in supported regions.)
## CLI Structure
```
az acr
āāā create / delete / list / show / update # Registry lifecycle
āāā login # Docker credential helper (or --expose-token)
āāā check-health / check-name / show-usage # Diagnostics & quota
āāā build # Cloud image build (quick task)
āāā run # Run a command / multi-step task once
āāā task # ACR Tasks (triggers, timers, logs, runs)
āāā agentpool # Dedicated task agent pools (Premium)
āāā import # Server-side image copy into the registry
āāā repository # List/show/delete/untag repos & tags, lock images
āāā manifest # Manifest metadata, delete, OCI referrers
āāā credential # Admin user credentials (avoid in production)
āāā token / scope-map # Repository-scoped tokens (Premium)
āāā replication # Geo-replication (Premium)
āāā network-rule # IP network rules
āāā private-endpoint-connection # Private Link approvals
āāā config # content-trust, retention, soft-delete, ...
āāā cache / credential-set # Artifact cache (pull-through cache) rules
āāā webhook # Push/delete event webhooks
āāā connected-registry # On-premises / IoT connected registries
āāā export-pipeline / import-pipeline / pipeline-run # acrtransfer extension
```
## Reference Files
Read the relevant reference file based on the user's task. Each file contains complete command syntax and examples for its domain.
| File | When to read | Covers |
|---|---|---|
| `references/auth-and-security.md` | Login failures, permissions, CI/CD or AKS pull access | `az acr login` (incl. `--expose-token`), Entra RBAC roles, service principals, managed identities, `--attach-acr` for AKS, repository-scoped tokens & scope maps, admin user, content trust |
| `references/build-and-tasks.md` | Building images in Azure, automation, CI triggers | `az acr build`, `az acr run`, multi-step task YAML, `az acr task` (git/base-image/timer triggers, logs, runs), agent pools |
| `references/images-and-artifacts.md` | Managing repos, tags, cleanup, storage costs | `az acr import`, repository & manifest commands, untag vs delete, purge (`acr purge`), image locking, retention policy, soft delete, artifact cache, `show-usage` |
| `references/networking-and-geo.md` | Multi-region, private access, edge scenarios | Geo-replication, zone redundancy, private endpoints, network rules, dedicated data endpoints, connected registries, registry transfer pipelines |Signals
Information
- Repository
- github/awesome-copilot
- Author
- github
- Last Sync
- 11/2/2026
- Repo Updated
- 11/2/2026
- Created
- 7/30/2026
Reviews (0)
No reviews yet. Be the first to review this skill!
Related Skills
cursorrules
CrewAI Development Rules
sparc
Execute SPARC methodology workflows with Claude-Flow
mem0-vercel-ai-sdk
Mem0 provider for Vercel AI SDK (@mem0/vercel-ai-provider). TRIGGER when: user mentions "vercel ai sdk", "@mem0/vercel-ai-provider", "createMem0", "retrieveMemories", "addMemories", "getMemories", "searchMemories", "mem0 vercel", "AI SDK provider", "AI SDK memory", or is using generateText/streamText with mem0. Also triggers for Next.js apps needing memory-augmented AI. DO NOT TRIGGER when: user asks about direct Python/TS SDK calls without Vercel (use mem0 skill), or CLI terminal commands (use mem0-cli skill).
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local `Memory` class) to the mem0 Platform / hosted SDK (`MemoryClient`). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch from self-hosted mem0 to MemoryClient", "use my mem0 API key instead of a local Qdrant", "replace my local vector store + embedder config with the platform", even without the word "migrate". Covers Python (`Memory` to `MemoryClient`) and TypeScript (`mem0ai/oss` to `mem0ai`). Produces a reviewable plan, then executes it after approval. Touches only the mem0 integration. DO NOT TRIGGER when: adding mem0 to a project that has none (use `mem0-integrate`) or answering SDK usage questions (use `mem0`).
Related Guides
Building Full-Stack Applications with Claude: The Node.js MongoDB JWT Express React Skill Guide
Learn how to use the nodejs mongodb jwt express react Claude skill. Complete guide with installation instructions and examples.
Complete Guide to the Node.js MongoDB Claude Skill: Supercharge Your Full-Stack Development
Learn how to use the nodejs mongodb Claude skill. Complete guide with installation instructions and examples.
Mastering Modern Web Development with the Medusa Claude Skill
Learn how to use the medusa Claude skill. Complete guide with installation instructions and examples.