**WORKFLOW SKILL** - Orchestrates Aspire applications using the Aspire CLI and MCP tools for running, debugging, and managing distributed apps. USE FOR: aspire run, aspire stop, start aspire app, check aspire resources, list aspire integrations, debug aspire issues, view aspire logs, add aspire resource, aspire dashboard, update aspire apphost. DO NOT USE FOR: non-Aspire .NET apps (use dotnet CLI), container-only deployments (use docker/podman), Azure deployment after local testing (use azure-de
SkillScore91Maintained
Automatic
◆Coding pack
Last verified 8/19/2026
What it changes
Passed 20 of 22 test cases with the skill, and 11 of 22 without it.
Without skill52%
With skill91%
Checks it passed that the model alone missed
Recommends executing `aspire stop`.
Recommends executing `aspire update`.
Recommends executing `aspire run --detach`.
and 9 more in the full report
10 fixed11 passed either way1 still failing1 broke
Pass-rate lift
+39 pp
Tokens
+36%
Agent turns
0%
Response time
-67%
Model gemini-3.6-flashMeasured 8/19/2026v121 of 23 cases passed with skill · 22 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
Before editing `apphost.cs` to add new services, what command should I run first to ensure we are building from a healthy known baseline state?
What was checked, without and with the skill
Checked
Without skill
With skill
Recommends executing `aspire run` to verify initial state.
Missed
Passed
case-20 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md115 linessingle file
Aspire Skill
This repository is set up to use Aspire. Aspire is an orchestrator for the entire application and will take care of configuring dependencies, building, and running the application. The resources that make up the application are defined in apphost.cs including application code and external dependencies.
General recommendations for working with Aspire
Before making any changes always run the apphost using aspire run and inspect the state of resources to make sure you are building from a known state.
Changes to the apphost.cs file will require a restart of the application to take effect.
Make changes incrementally and run the aspire application using the aspire run command to validate changes.
Use the Aspire MCP tools to check the status of resources and debug issues.
Running Aspire in agent environments
Agent environments may terminate foreground processes when a command finishes. Use detached mode:
aspire run --detach --isolated
This starts the AppHost in the background and returns immediately. The CLI will:
Automatically stop any existing running instance before starting a new one
Display a summary with the Dashboard URL and resource endpoints
Stopping the application
To stop a running AppHost:
aspire stop
This will scan for running AppHosts and stop them gracefully.
Relaunch rules
If AppHost code changes, run aspire run --detach again to restart with the new code.
Relaunching is safe: starting a new instance will automatically stop the previous instance.
Do not attempt to keep multiple instances running.