aspire

Routes Aspire AppHost operations to orchestration, deployment, and monitoring sub-skills via the Aspire CLI.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/codebytes/btt --skill aspire-codebytes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aspire
Source: https://github.com/codebytes/btt/tree/main/.agents/skills/aspire
Command: npx skills add https://github.com/codebytes/btt --skill aspire-codebytes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Working with Aspire distributed applications requires knowing which CLI command and workflow fits each task, and falling back to ad-hoc dotnet, docker, or shell commands causes errors and unsafe operations. This Skill detects an Aspire AppHost in the repository, enforces safety guardrails, and routes every task to the correct specialized sub-skill. ## Core Features & Use Cases - AppHost Detection: Identifies C# (.csproj with Aspire.AppHost.Sdk), file-based C# (apphost.cs), and TypeScript (apphost.ts) AppHosts, plus aspire.config.json and .aspire/ directory signals. - Task Routing: Directs lifecycle operations to aspire-orchestration, deployments to aspire-deployment, observability to aspire-monitoring, and first-run setup to aspire-init or aspireify. - Safety Guardrails: Enforces rules such as always using aspire start instead of dotnet run, always using aspire wait before interacting with resources, and always passing --non-interactive for agent execution. - Use Case: You open a repository containing an Aspire AppHost and ask to restart a single Redis resource. The Skill detects the AppHost, routes to aspire-orchestration, and uses aspire resource commands instead of restarting the entire application. ## Quick Start Ask the assistant to start the Aspire AppHost in this repository and wait until all resources are healthy before making changes.

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 from the repository root, never dotnet run on the AppHost project. For non-interactive agent runs, add the --non-interactive flag, then use 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 wire resources, integrations, and service defaults. In Aspire 13.3+, aspire init no longer wires the AppHost automatically.

Does this skill work with TypeScript Aspire AppHosts?

Yes, it detects apphost.ts files and generated .aspire/modules/ directories as definitive Aspire signals. It routes TypeScript AppHosts to the same orchestration, deployment, and monitoring sub-skills, with guidance to never edit .aspire/modules/ directly.

When should I not use the Aspire CLI workflow?

Do not use it for non-Aspire .NET projects, where dotnet commands apply directly, or for Azure provisioning without Aspire. Container-only repositories with no AppHost and ordinary build or test tasks are also out of scope.

Why does aspire publish fail with an unknown --log-level option?

In Aspire 13.3, --log-level was renamed to --pipeline-log-level on aspire publish and aspire deploy. Update CI/CD scripts to use --pipeline-log-level <level> to resolve the error.