Official agent skill

Container Images

by microsoft in microsoft/aspire.dev

Extracts all container image references (registry, image, tag) from the microsoft/aspire source code and produces a JSON data file for the aspire.dev Astro site.

OfficialMITAuto-check passedDevOps & Cloud

Install Container Images

skills CLI
$ npx skills add microsoft/aspire.dev --skill container-images -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install microsoft/aspire.dev container-images --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/microsoft/aspire.dev.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/container-images .claude/skills/container-images && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
container-images
GitHub stars
196
Token cost
~2.5k tokens
SKILL.md length
697 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
MIT

At a glance

Extracts all container image references (registry, image, tag) from the microsoft/aspire source code and produces a JSON data file for the aspire.dev Astro site.

  • Works in 5 steps: Clone or access the aspire repo at HEAD → Find all ContainerImageTags files → Parse each file → …
  • : update container images JSON
  • SKILL.md covers Source code pattern, Extraction procedure, Validation checklist and Consuming the data in Astro, plus 2 more sections
  • Calls git; reaches github.com

What it does

Container Images is an agent skill from microsoft/aspire.dev, published by the product's own GitHub organization. Extracts all container image references (registry, image, tag) from the microsoft/aspire source code and produces a JSON data file for the aspire.dev Astro site. USE FOR: update container images JSON, refresh container image data, list all aspire container images, sync container image versions, generate container-images.json. DO NOT USE FOR: updating the container image versions in aspire source code itself (that's a product repo change), NuGet package data (use the integrations skill), or Dockerfile-based images…

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Containers. It works with Microsoft Azure, Astro, Docker and Bash. The repository describes itself as: The official website for all things aspire.dev. The licence is MIT.

When your agent uses it

  • : update container images JSON
  • Refresh container image data
  • List all aspire container images
  • Sync container image versions

Example prompts

  • “Use the container-images skill to extract all container image references (registry, image, tag) from the microsoft/aspire source code and produces a…”
  • “/container-images”

Requirements

  • Docker

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Clone or access the aspire repo at HEAD
  2. Find all ContainerImageTags files
  3. Parse each file
  4. Build the JSON
  5. Sort and write

What it can do on your machine

Read from SKILL.md and the folder at commit a097c7e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Container Images loads about 2.5k tokens when it runs. Until then it costs about 165 tokens; SKILL.md has 697 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~165
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from microsoft/aspire.dev at commit a097c7e, republished under its MIT licence (© microsoft). 697 words, ~2,548 tokens.

Download SKILL.mdSave it as .claude/skills/container-images/SKILL.md (or your agent's skills folder).
name
container-images
description
Extracts all container image references (registry, image, tag) from the microsoft/aspire source code and produces a JSON data file for the aspire.dev Astro site. USE FOR: update container images JSON, refresh container image data, list all aspire container images, sync container image versions, generate container-images.json. DO NOT USE FOR: updating the container image versions in aspire source code itself (that's a product repo change), NuGet package data (use the integrations skill), or Dockerfile-based images for dev containers. INVOKES: bash, file read/write. FOR SINGLE OPERATIONS: Use grep/find to quickly check a single image tag.

Container Images Skill

This skill extracts every container image reference from the microsoft/aspire product repository and writes a structured JSON file to microsoft/aspire.dev at:

src/frontend/src/data/container-images.json

This JSON is consumed by Astro components on the aspire.dev site to render a browsable catalog of all container images used by Aspire hosting integrations.


Source code pattern

All container image metadata in microsoft/aspire lives in static classes named *ContainerImageTags (or *ContainerImageTags.cs). Each file follows a strict, consistent pattern:

csharp
internal static class <Name>ContainerImageTags
{
    public const string Registry = "<registry-host>";
    public const string Image = "<image-path>";
    public const string Tag = "<tag>";

    // Some files have additional companion images, e.g.:
    public const string <Companion>Registry = "<registry-host>";
    public const string <Companion>Image = "<image-path>";
    public const string <Companion>Tag = "<tag>";
}
Where to find them

All files matching the glob pattern:

src/**/ContainerImageTags.cs
src/**/*ContainerImageTags.cs

These span across many projects including (but not limited to):

ProjectFile
Aspire.Hosting.RedisRedisContainerImageTags.cs
Aspire.Hosting.PostgreSQLPostgresContainerImageTags.cs
Aspire.Hosting.SqlServerSqlServerContainerImageTags.cs
Aspire.Hosting.MongoDBMongoDBContainerImageTags.cs
Aspire.Hosting.MySqlMySqlContainerImageTags.cs
Aspire.Hosting.KafkaKafkaContainerImageTags.cs
Aspire.Hosting.RabbitMQRabbitMQContainerImageTags.cs
Aspire.Hosting.NatsNatsContainerImageTags.cs
Aspire.Hosting.GarnetGarnetContainerImageTags.cs
Aspire.Hosting.ValkeyValkeyContainerImageTags.cs
Aspire.Hosting.SeqSeqContainerImageTags.cs
Aspire.Hosting.QdrantQdrantContainerImageTags.cs
Aspire.Hosting.KeycloakKeycloakContainerImageTags.cs
Aspire.Hosting.OracleOracleContainerImageTags.cs
Aspire.Hosting.MilvusMilvusContainerImageTags.cs
Aspire.Hosting.ElasticsearchElasticsearchContainerImageTags.cs
Aspire.Hosting.YarpYarpContainerImageTags.cs
Aspire.Hosting.Azure.StorageStorageEmulatorContainerImageTags.cs
Aspire.Hosting.Azure.CosmosDBCosmosDBEmulatorContainerImageTags.cs
Aspire.Hosting.Azure.ServiceBusServiceBusEmulatorContainerImageTags.cs
Aspire.Hosting.Azure.EventHubsEventHubsEmulatorContainerImageTags.cs
Aspire.Hosting.Azure.SignalRSignalREmulatorContainerImageTags.cs
Aspire.Hosting.Azure.AppConfigurationAppConfigurationEmulatorContainerImageTags.cs
Aspire.Hosting.Azure.FunctionsDurableTaskSchedulerEmulatorContainerImageTags.cs
Aspire.Hosting.Azure.KustoAzureKustoEmulatorContainerImageTags.cs

Important: New hosting packages may be added at any time. Always discover files dynamically — never rely on a hardcoded list.


Extraction procedure

Step 1 — Clone or access the aspire repo at HEAD
bash
# If working locally:
git clone --depth 1 https://github.com/microsoft/aspire.git /tmp/aspire
Step 2 — Find all ContainerImageTags files
bash
find /tmp/aspire/src -name '*ContainerImageTags.cs' -type f
Step 3 — Parse each file

For each file, extract all image groups. A single file can define multiple images (primary + companions). The parsing rules are:

  1. Primary image: Fields named exactly Registry, Image, Tag.
  2. Companion images: Fields with a prefix, e.g. PgAdminRegistry, PgAdminImage, PgAdminTag — group them by the shared prefix.
  3. Alternate tags: Fields like TagVNextPreview, ManagementTag — include these as additional tag variants on the same image.
  4. Static properties vs const fields: Most use public const string, but some (e.g. Kusto) use public static string { get; }. Handle both.
  5. Computed tags: Some tags are computed, e.g. public const string ManagementTag = $"{Tag}-management"; — resolve these to their literal value.
  6. Derive the aspirePackage from the project directory name (e.g. src/Aspire.Hosting.Redis/ → Aspire.Hosting.Redis).
  7. Derive the sourceFile as the path relative to the repo root.
Step 4 — Build the JSON

Each entry in the output array represents one distinct container image:

json
[
  {
    "aspirePackage": "Aspire.Hosting.Redis",
    "name": "Redis",
    "registry": "docker.io",
    "image": "library/redis",
    "tag": "8.6",
    "fullImage": "docker.io/library/redis:8.6",
    "sourceFile": "src/Aspire.Hosting.Redis/RedisContainerImageTags.cs",
    "sourceUrl": "https://github.com/microsoft/aspire/blob/main/src/Aspire.Hosting.Redis/RedisContainerImageTags.cs",
    "isCompanion": false,
    "companionOf": null,
    "alternateTags": []
  },
  {
    "aspirePackage": "Aspire.Hosting.Redis",
    "name": "Redis Commander",
    "registry": "docker.io",
    "image": "rediscommander/redis-commander",
    "tag": "latest",
    "fullImage": "docker.io/rediscommander/redis-commander:latest",
    "sourceFile": "src/Aspire.Hosting.Redis/RedisContainerImageTags.cs",
    "sourceUrl": "https://github.com/microsoft/aspire/blob/main/src/Aspire.Hosting.Redis/RedisContainerImageTags.cs",
    "isCompanion": true,
    "companionOf": "Redis",
    "alternateTags": []
  },
  {
    "aspirePackage": "Aspire.Hosting.Azure.CosmosDB",
    "name": "CosmosDB Emulator",
    "registry": "mcr.microsoft.com",
    "image": "cosmosdb/linux/azure-cosmos-emulator",
    "tag": "stable",
    "fullImage": "mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator:stable",
    "sourceFile": "src/Aspire.Hosting.Azure.CosmosDB/CosmosDBEmulatorContainerImageTags.cs",
    "sourceUrl": "https://github.com/microsoft/aspire/blob/main/src/Aspire.Hosting.Azure.CosmosDB/CosmosDBEmulatorContainerImageTags.cs",
    "isCompanion": false,
    "companionOf": null,
    "alternateTags": ["vnext-preview"]
  }
]
Field definitions
FieldTypeDescription
aspirePackagestringThe NuGet package / project name (directory name under src/)
namestringHuman-friendly name. For primary images, derive this from the class name (strip ContainerImageTags / EmulatorContainerImageTags suffix, split PascalCase). For companion images, derive this from the companion prefix/type (e.g. PgAdmin*, RedisCommander*) rather than only from the class name.
registrystringContainer registry host (e.g. docker.io, mcr.microsoft.com, ghcr.io, quay.io, container-registry.oracle.com)
imagestringImage path within the registry
tagstringPrimary tag
fullImagestringFully qualified image reference: {registry}/{image}:{tag}
sourceFilestringRelative path to the source file in microsoft/aspire
sourceUrlstringGitHub permalink to the source file on the main branch
isCompanionbooleantrue if this is a companion/tooling image (e.g. pgAdmin, Kafka UI, phpMyAdmin)
companionOfstring?Name of the primary image this accompanies, or null
alternateTagsstring[]Any additional tag constants defined for this image (e.g. vnext-preview, management)
Show full SKILL.md (222 more words)Show less
Step 5 — Sort and write

Sort the array by aspirePackage (ascending), then by isCompanion (primary first), then by name (ascending).

Write to: src/frontend/src/data/container-images.json


Validation checklist

After generating the file, verify:

  • Every *ContainerImageTags.cs file in src/ is represented
  • No duplicate entries (same registry + image + tag + aspirePackage)
  • All fullImage values are well-formed (registry/image:tag)
  • Companion images are correctly linked to their primary
  • The JSON is valid and properly formatted (2-space indent)
  • The file is sorted per the rules above

Consuming the data in Astro

The JSON file at src/frontend/src/data/container-images.json can be imported directly in Astro components:

typescript
import containerImages from '../data/container-images.json';

This follows the same pattern as existing data files like aspire-integrations.json, samples.json, and github-stats.json in the same directory.

Each container image entry can be cross-referenced with:

  • The integration docs at src/frontend/src/data/integration-docs.json (match on aspirePackage)
  • The NuGet integrations at src/frontend/src/data/aspire-integrations.json (match on title ≈ aspirePackage)
  • The source file link back to microsoft/aspire for contributors

Important rules

  • Always discover files dynamically — new hosting packages are added frequently.
  • Parse both const and static property patterns — they both exist in the codebase.
  • Resolve string interpolation in computed tag values (e.g. $"""{Tag}-management""").
  • Do not include devcontainer images, test-only images, or images from the playground/ directory.
  • Only extract from src/ directory files matching *ContainerImageTags.cs.
  • The aspire.dev repo is an Astro site — the data file lives alongside other JSON data consumed by components.

© microsoft, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/container-images of microsoft/aspire.dev.

Open the folder on GitHubat commit a097c7e

Compare with similar skills

Container Images next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Container Images compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Container Images this skillmicrosoft/aspire.dev196—~2.5kAutomated safety check: PassMIT
Rtk Skillsopaco/deepwiki-rs3.1k—~1.4kAutomated safety check: PassMIT
Image Managementdotnet/dotnet-docker4.9k—~1.1kAutomated safety check: PassMIT
Build Imageskubernetes-sigs/cloud-provider-azure294—~1.7kAutomated safety check: PassApache-2.0
Ama Logs Update Charts Release Notesmicrosoft/Docker-Provider173—~2.6kAutomated safety check: PassCustom licence
Headless Codex CLI AutomationXiaomiMiMo/MiMo-Code14k—~2.7kAutomated safety check: PassMIT

Similar skills

  • Rtk Skill

    sopaco/deepwiki-rs

    A skill your agent uses when running shell commands that produce verbose output (git, test, build, lint, package managers, docker).

    3.1k GitHub stars~1.4k tokensUpdated 23 days ago
    DevOps & CloudAuto-check passed
  • Image Management

    dotnet/dotnet-docker

    Official

    Manages .NET Docker images including adding images for new .NET versions, new Linux distros (Alpine, Ubuntu, Azure Linux), and new Windows versions.

    4.9k GitHub stars~1.1k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Build Images

    kubernetes-sigs/cloud-provider-azure

    Official

    Build cloud-provider-azure container images through the repo Makefile with explicit IMAGETAG and IMAGEREGISTRY inputs, optional make flag overrides, and opt-in bounded Docker or Podman retries.

    294 GitHub stars~1.7k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Ama Logs Update Charts Release Notes

    microsoft/Docker-Provider

    Official

    Prepare an ama-logs release PR: bump the image tag (X.Y.Z) across Helm charts, manifests, and Dockerfiles, and add a formatted ReleaseNotes.md entry.

    173 GitHub stars~2.6k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Headless Codex CLI Automation

    XiaomiMiMo/MiMo-Code

    Runs OpenAI Codex CLI as a non-interactive worker for CI, Docker, Kubernetes or remote servers, with sandbox modes and JSONL-friendly output.

    14k GitHub stars~2.7k tokensUpdated 4 days ago
    DevOps & CloudAuto-check passed
  • Docker Via Wsl

    JMBeresford/retrom

    A skill your agent uses when YOU (the AI agent) are running on Windows OUTSIDE WSL (Git Bash/MSYS/PowerShell shell) and need to run ANY docker / docker compose command.

    2.1k GitHub stars~832 tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed

More from microsoft/aspire.dev

All 8 skills in this repo
  • Aspire

    microsoft/aspire.dev

    Official

    Orchestrates Aspire distributed applications using the Aspire CLI for running, debugging, and managing distributed apps.

    196 GitHub starsUsed in 4 repos~1.1k tokens
    Auto-check passed
  • Whatsnew

    microsoft/aspire.dev

    Official

    Step-argument skill that formalizes writing an Aspire "What's new in N.N" release-notes page (src/frontend/src/content/docs/whats-new/aspire-N-N.mdx) as a repeatable lifecycle.

    196 GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Doc Writer

    microsoft/aspire.dev

    Official

    Guidelines for producing accurate and maintainable documentation for the Aspire documentation site.

    196 GitHub stars~7.6k tokensUpdated today
    Auto-check passed
  • Twoslash Validator

    microsoft/aspire.dev

    Official

    Validate and fix two-slash TypeScript examples for aspire.dev.

    196 GitHub stars~856 tokensUpdated today
    Auto-check passed
  • Update Samples

    microsoft/aspire.dev

    Official

    Update the samples data file by fetching sample metadata from the microsoft/aspire-samples GitHub repository.

    196 GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Update Integrations

    microsoft/aspire.dev

    Official

    Update integration documentation links and API reference data by synchronizing NuGet package names with their documentation URLs and generating per-package API schemas.

    196 GitHub stars~5.2k tokensUpdated today
    Auto-check passed

Categories

Questions about Container Images

What does Container Images do?

Extracts all container image references (registry, image, tag) from the microsoft/aspire source code and produces a JSON data file for the aspire.dev Astro site. dev, published by the product's own GitHub organization.dev Astro site.

When should I use Container Images?

Container Images fits situations like: : update container images JSON; refresh container image data; list all aspire container images; sync container image versions.

How do I install Container Images in Claude Code?

Run `npx skills add microsoft/aspire.dev --skill container-images -a claude-code`. Or copy the skill folder (.agents/skills/container-images in microsoft/aspire.dev) into .claude/skills/container-images in your project. Claude Code loads it when a task matches its description.

How do I install Container Images in Codex?

Run `npx skills add microsoft/aspire.dev --skill container-images -a codex`. Or copy the skill folder (.agents/skills/container-images in microsoft/aspire.dev) into .agents/skills/container-images in your project. Codex loads it when a task matches its description.

Can I use Container Images in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add microsoft/aspire.dev --skill container-images -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/container-images, .gemini/skills/container-images, .github/skills/container-images and .opencode/skills/container-images in your project.

What does Container Images need to run?

Going by SKILL.md and its folder, Container Images needs the command-line tools its instructions call (git). Our summary lists: Docker.

Does Container Images access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Container Images safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Container Images use?

Container Images is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Container Images use?

About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Container Images?

Skills that share tags, products or a category with Container Images: Rtk Skill (sopaco/deepwiki-rs, 3.1k stars), Image Management (dotnet/dotnet-docker, 4.9k stars), Build Images (kubernetes-sigs/cloud-provider-azure, 294 stars) and Ama Logs Update Charts Release Notes (microsoft/Docker-Provider, 173 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Container Images?

microsoft (a GitHub organization, an official publisher) maintains it in microsoft/aspire.dev, which has 196 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 7, 2026.

Source: microsoft/aspire.dev on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.