aspire

Routes Aspire distributed app tasks to orchestration, deployment, and monitoring sub-skills.

25|4|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/thangchung/agent-engineering-experiment --skill aspire-thangchung
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aspire
Source: https://github.com/thangchung/agent-engineering-experiment/tree/main/agentgateway-entraid-obo/.claude/skills/aspire
Command: npx skills add https://github.com/thangchung/agent-engineering-experiment --skill aspire-thangchung

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Working with Aspire 13.4 distributed applications requires knowing which CLI command or workflow applies to each task, and falling back to ad-hoc dotnet, docker, or shell commands often breaks the AppHost model. This Skill detects Aspire projects, enforces safety guardrails, and routes every task to the correct sub-skill. ## Core Features & Use Cases - AppHost Detection: Identifies C#, file-based C#, and TypeScript AppHosts via project files, apphost.cs, apphost.ts, aspire.config.json, and .aspire directories. - Task Routing: Directs lifecycle operations to aspire-orchestration, deployments to aspire-deployment, observability to aspire-monitoring, and bootstrap or wiring work to aspire-init and aspireify. - Safety Guardrails: Enforces rules like always using aspire start instead of dotnet run, aspire wait before interacting with resources, and --non-interactive for agent execution. - Use Case: When you open a repo containing an Aspire AppHost and ask to restart a single failing resource, the Skill detects the AppHost, blocks a full AppHost restart, and routes to aspire-orchestration for a targeted resource command. ## Quick Start Ask the agent to start my Aspire AppHost and wait until the database resource is healthy before running the API.

Frequently Asked Questions about aspire

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start an Aspire AppHost from the command line?▼

Use aspire start instead of dotnet run on the AppHost project. In worktrees or shared environments, use aspire start --isolated, then run aspire wait <resource> before interacting with any resource.

How do I add Aspire to an existing .NET repository?▼

Run aspire init to drop the skeleton (aspire.config.json plus an AppHost stub), then use the aspireify skill to scan the repo, propose a resource graph, wire ServiceDefaults and OpenTelemetry, and validate with aspire start.

What changed in Aspire 13.3 that breaks existing code?▼

Key breaking changes include --log-level renamed to --pipeline-log-level, dashboard MCP server removal, NameOutput renamed to NameOutputReference, AddAndPublishPromptAgent replaced by AddPromptAgent, and aspire init no longer wiring the AppHost automatically.

Can I use dotnet run instead of the Aspire CLI for AppHosts?▼

No. The skill mandates aspire start for AppHosts and aspire wait for resource readiness, because dotnet run bypasses the Aspire CLI lifecycle, resource commands, and dashboard integration.

When should I not use the Aspire workflow skill?▼

Skip it for non-Aspire .NET projects (use dotnet directly), Azure provisioning without Aspire, container-only repos with no AppHost, and ordinary build or test tasks that do not involve the AppHost.

How do I view logs and traces for Aspire resources?▼

Use aspire logs, aspire otel logs, and aspire otel traces for local diagnostics, aspire describe for resource state, and aspire dashboard run for the dashboard. Deployed Azure apps route to the azure-diagnostics skill.