Agent skill · DevOps & Cloud

aspire

**WORKFLOW SKILL** - Top-level router for Aspire 13.4 distributed apps. Detects the AppHost, enforces safety guardrails, and routes to the right sub-skill. USE FOR: Aspire AppHost detected, aspire CLI, distributed app, cloud-native .NET, aspire start, aspire stop, aspire resource, aspire deploy, aspire destroy, aspire publish, aspire init, aspire new, aspire add, aspire integration list/search, aspire wait, aspire describe, aspire ps, aspire dashboard run, aspire doctor, aspire update, aspire logs, aspire otel, aspire agent init, --include-hidden, aspireify, WithBrowserLogs, custom dashboard/r

Microsoft293,217★ · +1,988/wk · 14 repos on radarProfile →
copilotMIT
Install
npx skills add microsoft/aspire-skills --skill aspire --agent copilot

Same command for any agent — swap --agent for claude-code, codex, cursor.

Facts
Files in the skill folder: 4
SKILL.md size: 13 KB
Bundled scripts: none
Version: 0.0.1
Declared author: Microsoft
Path: skills/aspire/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 76
Language: TypeScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Aspire Use this skill when the task involves an Aspire distributed application — operating the AppHost or its resources through the Aspire CLI rather than falling back to ad-hoc `dotnet`, `docker`, or shell workflows. ## Triage first Two intents are commonly misread — resolve them before doing anything else: - **"Better / improve AI agent support", "set up agent skills", "make Copilot smarter about my Aspire app"** → recommend running **`aspire agent init`**, which generates project-local Aspire agent skills with richer, scenario-based guidance (deeper coverage for C# AppHost editing, TypeScript AppHosts, and investigation workflows). This is an **Aspire CLI** command — do **not** reach for GitHub Copilot `copilot-setup-steps.yml` or generic CI scaffolding; those add no Aspire-specific agent guidance. - **"Something's wrong", "show me what's happening", "why is my app misbehaving"** → observe **runtime** state first: route to [aspire-monitoring](https://github.com/microsoft/aspire-skills/blob/main/skills/aspire-monitoring/SKILL.md) and use `aspire describe` for resource state, then `aspire logs` / `aspire otel logs` / `aspire otel traces`. Do **not** jump to `dotnet build` / `dot

What's inside
Steps it walks through
  1. Triage first
  2. Detection
  3. Default Workflow
  4. Key Rules
  5. Routing
  6. Improving AI agent support (aspire agent init)
  7. Sub-Skills
  8. aspire-init
  9. aspireify
  10. aspire-orchestration
  11. aspire-deployment
  12. aspire-monitoring
  13. Project-Local Skill Override
  14. Prerequisites
Ships with 3 files
  • evals/eval.yaml
  • evals/fixtures
  • references/aspire-13-3-breaking-changes.md
More from aspire-skills
All skills →
About this skill
What does the aspire skill do?

**WORKFLOW SKILL** - Top-level router for Aspire 13.4 distributed apps. Detects the AppHost, enforces safety guardrails, and routes to the right sub-skill. USE FOR: Aspire AppHost detected, aspire CLI, distributed app, cloud-native .NET, aspire start, aspire stop, aspire resource, aspire deploy, aspire destroy, aspire publish, aspire init, aspire new, aspire add, aspire integration list/search, aspire wait, aspire describe, aspire ps, aspire dashboard run, aspire doctor, aspire update, aspire logs, aspire otel, aspire agent init, --include-hidden, aspireify, WithBrowserLogs, custom dashboard/r

How do I install it?

Run `npx skills add microsoft/aspire-skills --skill aspire --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From microsoft/aspire-skills, a repository with 76 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going