Lists multiple specific concrete actions: running, debugging, managing distributed apps, checking resources, listing integrations, viewing logs, adding resources, accessing dashboard, updating apphost. Also names specific MCP tools like list_resources, list_integrations, list_structured_logs.

Clearly answers both 'what' (orchestrates Aspire applications using CLI and MCP tools for running, debugging, managing) and 'when' (explicit USE FOR and DO NOT USE FOR clauses with specific trigger scenarios). The DO NOT USE FOR section with alternatives adds exceptional clarity.

Excellent coverage of natural trigger terms users would say: 'aspire run', 'aspire stop', 'start aspire app', 'check aspire resources', 'list aspire integrations', 'debug aspire issues', 'view aspire logs', 'aspire dashboard'. These are highly natural phrases a user would type.

Highly distinctive with clear niche (Aspire-specific tooling). The DO NOT USE FOR section explicitly delineates boundaries against dotnet CLI, docker/podman, and azure-deploy skill, making conflicts very unlikely.

Significant verbosity throughout. Explains obvious concepts ('Aspire is an orchestrator for the entire application'), repeats information (running the application is covered twice with overlapping content), and includes unnecessary phrasing like 'use this tool to get details about' repeatedly. The documentation tools section is particularly bloated—Claude doesn't need to be told what 'search' and 'get' do in such detail.

Provides concrete CLI commands (aspire run, aspire stop, aspire run --detach --isolated) which is good, but the MCP tool references are vague—they use informal names like 'list resources tool' and 'list structured logs' without specifying exact tool names or parameters. The debugging section tells Claude to use tools but doesn't show concrete invocation patterns or expected outputs.

There are some workflows present (general recommendations list steps, debugging has a sequence, documentation lookup has a 3-step workflow), but validation checkpoints are mostly missing. The 'make changes incrementally and run aspire run to validate' is vague. There's no explicit feedback loop for what to do when resources fail or when debugging reveals specific error patterns. The relaunch rules section is helpful but lacks error recovery guidance.

Everything is in a single monolithic file with no references to supporting files. The content is long (~120 lines) and mixes quick-start information with advanced topics (updating, persistent containers, Playwright MCP, documentation tools) all inline. Topics like documentation tool usage, Playwright integration, and updating could easily be split into separate referenced files.