aspire

Orchestrates Aspire distributed applications using the Aspire CLI for running, debugging, and managing resources.

1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/miiitch/EzSCIM --skill aspire-miiitch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aspire
Source: https://github.com/miiitch/EzSCIM/tree/main/.github/skills/aspire
Command: npx skills add https://github.com/miiitch/EzSCIM --skill aspire-miiitch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing a distributed .NET application with multiple services, databases, and integrations requires coordinating many moving parts. This Skill provides structured guidance for operating Aspire AppHosts through the Aspire CLI, covering startup, resource lifecycle, log inspection, and integration management without memorizing command syntax. ## Core Features & Use Cases - App Lifecycle Management: Start, stop, and restart the AppHost with aspire start, including isolated mode for git worktrees to avoid port conflicts. - Resource-Level Operations: Rebuild individual .NET project resources with aspire resource <name> rebuild instead of restarting the entire AppHost. - Debugging and Observability: Inspect resource status, structured logs, console output, and distributed traces via aspire describe, aspire otel logs, and aspire otel traces. - Integration Management: Search official docs with aspire docs search and add new integrations with aspire add. - Use Case: After modifying a single API project in your Aspire solution, run aspire resource myapi rebuild to rebuild and restart only that resource, then check aspire otel logs myapi to verify it started cleanly. ## Quick Start Ask the agent to start the Aspire app and show the status of all resources.

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 distributed application from the CLI?▼

Run `aspire start` to launch the AppHost in the background. When working in a git worktree, use `aspire start --isolated` to avoid port conflicts and prevent sharing user secrets with other running instances.

How do I restart a single Aspire resource without restarting the whole app?▼

Use `aspire resource <name> rebuild` for .NET project resources, which coordinates stop, build, and restart for just that resource. Only restart the full AppHost with `aspire start` when the AppHost code itself changed.

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

Use `aspire otel logs <resource>` for structured logs, `aspire logs <resource>` for console output, and `aspire otel traces <resource>` for distributed traces. You can also filter logs by trace ID with `aspire otel logs --trace-id <id>`.

Can I run multiple Aspire AppHosts in git worktrees at the same time?▼

Yes, use `aspire start --isolated` in each worktree. Isolated mode prevents port conflicts and stops instances from sharing user secrets or other local state with each other.

When should I not use the Aspire CLI?▼

Do not use it for non-Aspire .NET apps (use the dotnet CLI), container-only deployments (use docker or podman), or Azure deployment after local testing. It is scoped to orchestrating Aspire AppHosts during local development.

How do I add a new integration to an Aspire AppHost?▼

Search documentation with `aspire docs search <query>`, read the guide with `aspire docs get <slug>`, then run `aspire add` to add the integration package. Restart the app with `aspire start` for the new resource to take effect.