Agent skill · DevOps & Cloud

aspire

Aspire skill covering the Aspire CLI, AppHost orchestration, service discovery, integrations, MCP server, VS Code extension, Dev Containers, GitHub Codespaces, templates, dashboard, and deployment. Use when the user asks to create, run, debug, configure, deploy, or troubleshoot an Aspire distributed application.

GitHub68,948★ · +463/wk · 2 repos on radarProfile →
copilotMIT
Install
npx skills add github/awesome-copilot --skill aspire --agent copilot

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

Facts
Files in the skill folder: 10
SKILL.md size: 9 KB
Bundled scripts: none
Path: skills/aspire/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 37,432 · +281 this week
Language: Python

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

From the SKILL.md

# Aspire — Polyglot Distributed-App Orchestration Aspire is a **code-first, polyglot toolchain** for building observable, production-ready distributed applications. It orchestrates containers, executables, and cloud resources from a single AppHost project — regardless of whether the workloads are C#, Python, JavaScript/TypeScript, Go, Java, Rust, Bun, Deno, or PowerShell. > **Mental model:** The AppHost is a *conductor* — it doesn't play the instruments, it tells every service when to start, how to find each other, and watches for problems. Detailed reference material lives in the `references/` folder — load on demand. --- ## References | Reference | When to load | |---|---| | [CLI Reference](references/cli-reference.md) | Command flags, options, or detailed usage | | [MCP Server](references/mcp-server.md) | Setting up MCP for AI assistants, available tools | | [Integrations Catalog](references/integrations-catalog.md) | Discovering integrations via MCP tools, wiring patterns | | [Polyglot APIs](references/polyglot-apis.md) | Method signatures, chaining options, language-specific patterns | | [Architecture](references/architecture.md) | DCP internals, resource model, service discov

What's inside
Steps it walks through
  1. References
  2. 1. Researching Aspire Documentation
  3. Aspire CLI 13.2+ (recommended — has built-in docs search)
  4. Aspire CLI 13.1 (integration tools only)
  5. Fallback: Context7
  6. Fallback: GitHub search (when Context7 is also unavailable)
  7. 2. Prerequisites & Install
  8. 3. Project Templates
  9. 4. AppHost Quick Start (Polyglot)
  10. 5. Core Concepts (Summary)
  11. 6. CLI Quick Reference
  12. 7. Common Patterns
  13. Adding a new service
  14. Migrating from Docker Compose
Ships with 9 files
  • references/architecture.md
  • references/cli-reference.md
  • references/dashboard.md
  • references/deployment.md
  • references/integrations-catalog.md
  • references/mcp-server.md
  • references/polyglot-apis.md
  • references/testing.md
  • references/troubleshooting.md
Commands it runs
Linux / macOS
curl -sSL https://aspire.dev/install.sh | bash
Windows PowerShell
irm https://aspire.dev/install.ps1 | iex
Verify
aspire --version
Install templates
dotnet new install Aspire.ProjectTemplates
More from awesome-copilot
All skills →
About this skill
What does the aspire skill do?

Aspire skill covering the Aspire CLI, AppHost orchestration, service discovery, integrations, MCP server, VS Code extension, Dev Containers, GitHub Codespaces, templates, dashboard, and deployment. Use when the user asks to create, run, debug, configure, deploy, or troubleshoot an Aspire distributed application.

How do I install it?

Run `npx skills add github/awesome-copilot --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 github/awesome-copilot, a repository with 37,432 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