Aspire
Routes Aspire-related prompts to orchestration, deployment, or monitoring sub-skills and steers you toward project-local agent init when you need richer Aspire guidance.
Overview
aspire is an agent skill most often used in Build (also Ship, Operate) that routes Aspire intents to orchestration, deployment, or monitoring sub-skills and promotes project-local agent initialization.
Install
npx skills add https://github.com/microsoft/aspire-skills --skill aspireWhat is this skill?
- Top-level router evaluates prompts and directs to aspire-orchestration, aspire-deployment, or aspire-monitoring
- Eval harness expects recommendations for aspire agent init for stronger project-local skills
- Uses real AppHost csproj and Program.cs fixtures for routing fidelity
- Supports AI agent enablement narratives on existing Aspire solutions
- Versioned capability skill (v1.0) with copilot-sdk style eval configuration
- 3 routing targets: aspire-orchestration, aspire-deployment, aspire-monitoring
- Eval config version 1.0 with 3 runs per stimulus in sample harness
Adoption & trust: 27 installs on skills.sh; 48 GitHub stars.
What problem does it solve?
You have an Aspire AppHost but generic AI answers mix up orchestration, deploy steps, and monitoring without matching your project files.
Who is it for?
Indie developers on .NET Aspire who need intent-based routing across app host setup, release, and ops concerns.
Skip if: Teams not using Aspire or builders who only need unrelated Azure resource scripts without an AppHost.
When should I use this skill?
Working on .NET Aspire projects when intent spans orchestration, deployment, monitoring, or Aspire agent initialization.
What do I get? / Deliverables
You land on the correct Aspire sub-skill path and get actionable guidance such as running aspire agent init for richer local skills.
- Correct sub-skill recommendation for the user’s Aspire intent
- Guidance to run aspire agent init when richer local skills are needed
- Project-aware routing grounded in AppHost layout
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Aspire work starts while wiring services and app hosts during Build, even though deployment and monitoring questions appear later in Ship and Operate. Integrations is the primary shelf because the router evaluates intent around AppHost projects, agent init, and cloud-native composition—not one-off docs.
Where it fits
You ask for better AI agent support and the router recommends aspire agent init against your AppHost csproj.
You describe a production push and get routed toward aspire-deployment instead of local orchestration edits.
You troubleshoot telemetry and the router sends you to aspire-monitoring guidance for running services.
How it compares
Acts as a router hub across Aspire-specific skills—not a replacement for reading official Aspire deployment docs end to end.
Common Questions / FAQ
Who is aspire for?
Solo and small-team builders maintaining .NET Aspire AppHost solutions who want the agent to pick orchestration, deployment, or monitoring guidance automatically.
When should I use aspire?
In Build when wiring services and agent support; in Ship when choosing deployment flows; in Operate when you ask about monitoring or dashboards for an Aspire app.
Is aspire safe to install?
Check Prism’s Security Audits panel for this listing and restrict filesystem access to your AppHost repo when running router evals or init commands.
SKILL.md
READMESKILL.md - Aspire
name: aspire-router-eval description: Evaluates the top-level aspire router skill for correct sub-skill routing. Tests that prompts are directed to aspire-orchestration, aspire-deployment, or aspire-monitoring based on intent. version: "1.0" type: capability tags: skill: aspire config: runs: 3 timeout: 120s executor: copilot-sdk model: gpt-5-mini stimuli: - name: router-init-001 prompt: I want better AI agent support for my Aspire project tags: priority: p1 area: recommendation environment: files: - src: ../../../evals/csharp-apphost/MyApp.AppHost/MyApp.AppHost.csproj dest: csharp-apphost/MyApp.AppHost/MyApp.AppHost.csproj - src: ../../../evals/csharp-apphost/MyApp.AppHost/Program.cs dest: csharp-apphost/MyApp.AppHost/Program.cs - src: ../../../evals/csharp-apphost/aspire.config.json dest: csharp-apphost/aspire.config.json graders: - type: prompt name: recommends_agent_init config: prompt: Does the assistant's response recommend running 'aspire agent init' (or an equivalent command to generate project-local Aspire agent skills)? Answer based on the intent, not exact string matching. - type: prompt name: explains_value config: prompt: The assistant's response should recommend running 'aspire agent init' to generate project-local skills with richer, scenario-based guidance. It should mention that this provides deeper coverage for C# AppHost editing, TypeScript AppHosts, and investigation workflows. - type: output-contains config: substring: aspire agent init - name: router-reject-001 prompt: How do I run my .NET console app? tags: priority: p1 area: routing environment: files: - src: ../../../evals/non-aspire/MyApp/MyApp.csproj dest: non-aspire/MyApp/MyApp.csproj - src: ../../../evals/non-aspire/MyApp/Program.cs dest: non-aspire/MyApp/Program.cs graders: - type: prompt name: uses_dotnet_not_aspire config: prompt: The assistant's response should recognize this is a standard .NET project (no Aspire.AppHost.Sdk) and suggest 'dotnet run' rather than 'aspire start'. Aspire-specific guardrails should not be applied to a non-Aspire project. Answer based on intent. - type: output-contains config: substring: dotnet run name: allows_dotnet_run - type: output-not-contains config: substring: aspire start name: no_aspire_commands - type: output-not-contains config: substring: aspire run - name: router-azdiag-001 prompt: My Aspire app is deployed to Azure and users are reporting errors. Help me investigate. tags: priority: p0 area: routing environment: files: - src: ../../../evals/csharp-apphost/MyApp.AppHost/MyApp.AppHost.csproj dest: csharp-apphost/MyApp.AppHost/MyApp.AppHost.csproj - src: ../../../evals/csharp-apphost/MyApp.AppHost/Program.cs dest: csharp-apphost/MyApp.AppHost/Program.cs - src: ../../../evals/csharp-apphost/aspire.config.json dest: csharp-apphost/aspire.config.json graders: - type: prompt name: routes_to_azure_diagnostics config: prompt: The assistant's response should recognize this is a deployed app and route to azure-diagnostics or platform-specific tools. It should explain that Aspire CLI cannot connect to deployed apps (local backchannel only). Answer based on intent. - type: output-not-contains config: substring: aspire logs name: no_local_aspire_for_deployed - type: output-not-contains config: substring: aspire describe - name: router-deploy-001 prompt: