aspire

Route Aspire AppHost tasks through the Aspire CLI.

1|Updated Feb 4, 2025

Search Tags:#workflow #routing #cli #orchestration #aspire #apphost

Ready to run

npx skills add https://github.com/MarcelMichau/dotnet-starter-project-template --skill aspire-marcelmichau

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aspire
Source: https://github.com/MarcelMichau/dotnet-starter-project-template/tree/main/.agents/skills/aspire
Command: npx skills add https://github.com/MarcelMichau/dotnet-starter-project-template --skill aspire-marcelmichau

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates and centralizes control of Aspire AppHost workflows by routing tasks through the Aspire CLI, avoiding ad-hoc dotnet, docker, or shell sequences.

Core Features & Use Cases

Routing & orchestration: Detects the AppHost and routes to the appropriate sub-skills (aspire-init, aspireify, aspire-orchestration, aspire-deployment, aspire-monitoring) to drive lifecycle tasks.
Safety guardrails: Enforces best-practice workflows and prevents unsafe operations by coordinating with sub-skills.
Lifecycle management: Supports start, wait, describe, logs, and deployment workflows across a single, coordinated flow.

Quick Start

Route tasks to this skill and run the Aspire CLI to drive the AppHost lifecycle.

Frequently Asked Questions about aspire

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

FAQPage Schema

How do I orchestrate Aspire AppHost workflows without writing manual dotnet or docker commands?▼

You can orchestrate Aspire AppHost workflows by routing lifecycle tasks through the Aspire CLI, which centralizes control and avoids ad-hoc shell sequences. It coordinates sub-skills to manage start, wait, describe, logs, and deployment operations.

What is the best way to manage distributed application lifecycle tasks in an Aspire-enabled repository?▼

The best way to manage distributed application lifecycle tasks is routing them through the Aspire CLI, which detects the AppHost and delegates to orchestration, deployment, and monitoring sub-skills to enforce safe, coordinated workflows.

Do I need the Aspire CLI and wired sub-skills to govern AppHost orchestration?▼

Yes, governing AppHost orchestration requires the Aspire CLI and an Aspire-enabled repository with wired sub-skills like aspire-init, aspireify, aspire-orchestration, aspire-deployment, and aspire-monitoring to route and execute tasks properly.

How does routing Aspire AppHost tasks through sub-skills prevent unsafe operations?▼

Routing AppHost tasks through sub-skills enforces safety guardrails and best-practice workflows by coordinating operations through a centralized CLI flow, preventing ad-hoc or unsafe dotnet, docker, and shell executions.

Can I use this skill to monitor resources and wire dependencies across Aspire distributed apps?▼

Yes, you can monitor resources and wire dependencies across distributed apps because the skill routes AppHost resource wiring and monitoring tasks to the appropriate aspire-orchestration and aspire-monitoring sub-skills.

What limitations should I expect when automating Aspire AppHost lifecycle management?▼

Limitations include strict dependency on the Aspire CLI, an Aspire-enabled repository, and pre-wired sub-skills; without these, the skill cannot route tasks or enforce safety guardrails across the distributed application lifecycle.