Official agent skill

Update Samples

by microsoft in microsoft/aspire.dev

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

OfficialMITAuto-check passed

Install Update Samples

skills CLI
$ npx skills add microsoft/aspire.dev --skill update-samples -a claude-code

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

GitHub CLI
$ gh skill install microsoft/aspire.dev update-samples --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/update-samples .claude/skills/update-samples && 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
update-samples
GitHub stars
196
Token cost
~1.7k tokens
SKILL.md length
668 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 7 steps: Run the update script → What the script does → Tag detection → …
  • Adding new samples
  • SKILL.md covers Overview, Prerequisites and Step-by-Step Process
  • Calls pnpm and node; reaches github.com; needs GITHUB_TOKEN

What it does

Update Samples is an agent skill from microsoft/aspire.dev, published by the product's own GitHub organization. Update the samples data file by fetching sample metadata from the microsoft/aspire-samples GitHub repository. Use when adding new samples, refreshing sample data, or ensuring samples.json stays in sync with the upstream repo.

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

It works with GitHub and Microsoft Azure. The repository describes itself as: The official website for all things aspire.dev. The licence is MIT.

When your agent uses it

  • Adding new samples
  • Refreshing sample data
  • Ensuring samples.json stays in sync with the upstream repo

Example prompts

  • “/update-samples”

Requirements

  • Python 3
  • Node.js
  • Docker
  • A credential in GITHUB_TOKEN

Workflow steps

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

  1. Run the update script
  2. What the script does
  3. Tag detection
  4. Output format
  5. Manual review
  6. Environment variables
  7. Integration with build

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:

    • pnpm
    • node

    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 these keys or tokens, usually read from environment variables:

    • GITHUB_TOKEN

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

Context cost

Update Samples loads about 1.7k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 668 words of instructions outside code blocks.

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

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). 668 words, ~1,661 tokens.

Download SKILL.mdSave it as .claude/skills/update-samples/SKILL.md (or your agent's skills folder).
name
update-samples
description
Update the samples data file by fetching sample metadata from the microsoft/aspire-samples GitHub repository. Use when adding new samples, refreshing sample data, or ensuring samples.json stays in sync with the upstream repo.

Update Samples Data

This skill synchronizes the samples data file with the microsoft/aspire-samples GitHub repository. It enumerates all sample projects in the samples/ directory, fetches each sample's README.md, and generates a structured JSON catalog.

Overview

The aspire.dev site maintains a data file for samples:

  • src/frontend/src/data/samples.json — Sample metadata including titles, descriptions, tags, deep links, and README content extracted from the upstream repo.

This skill keeps that file in sync with the microsoft/aspire-samples repository on GitHub.

Prerequisites

  • Node.js installed and available on PATH
  • Working directory is the repository root
  • The frontend project dependencies are installed (pnpm install in src/frontend/)
  • Optional: GITHUB_TOKEN environment variable for higher GitHub API rate limits

Step-by-Step Process

1. Run the update script

Fetch the latest sample data from the GitHub API:

bash
cd src/frontend && node scripts/update-samples.js

This writes updated sample metadata to src/frontend/src/data/samples.json. The script queries the GitHub Contents API for directories in microsoft/aspire-samples/samples/, fetches each sample's README.md, and extracts structured metadata.

2. What the script does

For each subdirectory in samples/:

  1. Lists directories — Calls the GitHub Contents API to enumerate entries in samples/ and filters to directories only (skipping files like global.json, Directory.Build.props).

  2. Fetches README.md — Downloads the raw README.md for each sample directory.

  3. Extracts metadata from the README:

    • name — The directory name (e.g., aspire-shop)
    • title — Extracted from the first # heading in the README
    • description — The first paragraph of body text after the title (before any ## heading)
  • href — Deep link to the sample on GitHub: https://github.com/microsoft/aspire-samples/tree/main/samples/{name}
  • readme — The full Markdown content of the README.md, with image paths rewritten to local assets (see below)
  • tags — Auto-detected tags based on technologies, languages, services, and features mentioned in the README and directory name
  • thumbnail — Local asset path to the first image referenced in the README (if any), or null
  1. Downloads images — For each image referenced in the README (![alt](src)):

    • Resolves the remote URL (relative paths are resolved against the GitHub raw content URL)
    • Downloads the image to src/frontend/src/assets/samples/{name}/{filename}
    • Rewrites the image reference in the README to use the local asset path: ~/assets/samples/{name}/{filename}
    • This ensures images are bundled with the site and served locally rather than hotlinked from GitHub
  2. Writes output — Saves the result as a sorted JSON array to src/frontend/src/data/samples.json.

3. Tag detection

Tags are automatically inferred from the README content and sample name. The script detects:

Languages
TagMatched by
csharpC#, .NET references
pythonPython references
javascriptJavaScript references
nodeNode.js references
goGo/Golang references
javaJava, Spring Boot, Quarkus, Maven, Gradle references
Show full SKILL.md (264 more words)Show less
Services & Technologies
TagMatched by
redisRedis references
postgresqlPostgreSQL, Postgres, Npgsql references
sql-serverSQL Server, MSSQL references
mysqlMySQL references
mongodbMongoDB references
rabbitmqRabbitMQ references
kafkaKafka references
prometheusPrometheus references
grafanaGrafana references
dockerDocker, container references
Azure Services
TagMatched by
azureAzure references
azure-functionsAzure Functions references
azure-storageAzure Storage references
azure-service-busAzure Service Bus references
Frameworks & Features
TagMatched by
blazorBlazor references
orleansOrleans references
grpcgRPC references
ef-coreEntity Framework Core references
metricsMetrics, OpenTelemetry references
health-checksHealth check references
containersContainer build/deployment references
databasesDatabase-related references
migrationsDatabase migration references
volumesVolume mount references
dashboardDashboard references
4. Output format

The output samples.json is a JSON array with entries like:

json
[
  {
    "name": "aspire-shop",
    "title": "Aspire Shop",
    "description": "The app consists of four .NET services including a Blazor frontend, catalog API, catalog database manager, and basket service.",
    "href": "https://github.com/microsoft/aspire-samples/tree/main/samples/aspire-shop",
    "readme": "# Aspire Shop\n\n![Screenshot...](~/assets/samples/aspire-shop/aspireshop-frontend-complete.png)...",
    "tags": ["csharp", "blazor", "postgresql", "redis", "grpc", "ef-core"],
    "thumbnail": "~/assets/samples/aspire-shop/aspireshop-frontend-complete.png"
  }
]
5. Manual review

After running the script:

  • Review new entries — Verify titles and descriptions are meaningful
  • Check tags — The auto-detection may miss niche technologies; manually add tags if needed
  • Verify thumbnails — Ensure image URLs resolve correctly
  • Remove stale samples — The script automatically handles this since it rebuilds from source
6. Environment variables
VariableRequiredDescription
GITHUB_TOKENNoGitHub personal access token for higher API rate limits (60 → 5000 requests/hour)
SAMPLES_BRANCHNoOverride the microsoft/aspire-samples ref to fetch from (default main). Useful for staging samples.json against a still-open upstream PR — set to the PR's head ref. The generated href fields stay anchored to main so links remain valid after the PR branch is deleted.
7. Integration with build

The script is registered as an npm script in src/frontend/package.json:

bash
pnpm update:samples

It is also included in the update:all aggregate script so it runs alongside other data updates during builds.

© 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/update-samples of microsoft/aspire.dev.

Open the folder on GitHubat commit a097c7e

Compare with similar skills

Update Samples 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.

Update Samples compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Update Samples this skillmicrosoft/aspire.dev196—~1.7kAutomated safety check: PassMIT
Version ReleaseNG-ZORRO/ng-zorro-antd9.2k—~3.1kAutomated safety check: PassMIT
Kql ValidatorAzure/azqr794—~703Automated safety check: PassMIT
Update Provider Depsmondoohq/mql411—~4.5kAutomated safety check: PassCustom licence
ReleaseAzure/agent-app-orchestrator103—~2.5kAutomated safety check: PassMIT
Code Reviewlangchain-ai/langchain-azure147—~2.3kAutomated safety check: PassMIT

Similar skills

  • Version Release

    NG-ZORRO/ng-zorro-antd

    NG-ZORRO/ng-zorro-antd repository release workflow. An agent skill from NG-ZORRO/ng-zorro-antd.

    9.2k GitHub stars~3.1k tokensUpdated 7 days ago
    DevelopmentAuto-check passed
  • Kql Validator

    Azure/azqr

    Official

    Validate KQL (Kusto Query Language) files used in Azure Quick Review (azqr) against their recommendation definitions.

    794 GitHub stars~703 tokensUpdated 2 days ago
    Backend & APIsAuto-check passed
  • Upgrade an mql provider's vendored SDKs (all providers or a named subset), audit the new versions for breaking changes and fix call sites while keeping shipped MQL fields backwards-compatible, check…

    411 GitHub stars~4.5k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Release

    Azure/agent-app-orchestrator

    Official

    Prepare and reconcile GPT-RAG Orchestrator releases, including authoritative version discovery, semantic version selection, release branches, VERSION and CHANGELOG updates, release notes, tags…

    103 GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check passed
  • Code Review

    langchain-ai/langchain-azure

    Official

    Reviews changes in the langchain-azure monorepo using package-specific knowledge of langchain-azure-ai, langchain-azure-compute, langchain-azure-cosmosdb, langchain-azure-postgresql…

    147 GitHub stars~2.3k tokensUpdated yesterday
    AI & LLM EngineeringAuto-check passed
  • Sdaf Orientation And Surface

    Azure/sap-automation

    Official

    Orient a newcomer to the SAP Deployment Automation Framework (SDAF): explain the spine (control plane → workload zone → SAP system → software → install → operate/remove), summarise the three…

    145 GitHub stars~1.6k tokensUpdated today
    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
  • Container Images

    microsoft/aspire.dev

    Official

    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.

    196 GitHub stars~2.5k 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 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

Questions about Update Samples

What does Update Samples do?

Update the samples data file by fetching sample metadata from the microsoft/aspire-samples GitHub repository. dev, published by the product's own GitHub organization. Update the samples data file by fetching sample metadata from the microsoft/aspire-samples GitHub repository.

When should I use Update Samples?

Update Samples fits situations like: adding new samples; refreshing sample data; ensuring samples.json stays in sync with the upstream repo.

How do I install Update Samples in Claude Code?

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

How do I install Update Samples in Codex?

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

Can I use Update Samples 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 update-samples -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/update-samples, .gemini/skills/update-samples, .github/skills/update-samples and .opencode/skills/update-samples in your project.

What does Update Samples need to run?

Going by SKILL.md and its folder, Update Samples needs the command-line tools its instructions call (pnpm and node) and credentials named GITHUB_TOKEN. Our summary lists: Python 3; Node.js; Docker; A credential in GITHUB_TOKEN.

Does Update Samples 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 Update Samples 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 Update Samples use?

Update Samples 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 Update Samples use?

About 1.7k tokens (SKILL.md is roughly 6.6k 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 Update Samples?

Skills that share tags, products or a category with Update Samples: Version Release (NG-ZORRO/ng-zorro-antd, 9.2k stars), Kql Validator (Azure/azqr, 794 stars), Update Provider Deps (mondoohq/mql, 411 stars) and Release (Azure/agent-app-orchestrator, 103 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Update Samples?

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.