aspire

**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-deploy skill). INVOKES: Aspire MCP tools (list_resources, list_integrations, list_structured_logs, get_doc, search_docs), bash for CLI commands. FOR SINGLE OPERATIONS: Use Aspire MCP tools directly for quick resource status or doc lookups.

Quality

75%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.github/skills/aspire/SKILL.md

Quality

Discovery

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an excellent skill description that follows best practices across all dimensions. It provides specific concrete actions, comprehensive natural trigger terms, explicit 'use when' and 'don't use when' guidance, and clear boundaries against related skills. The DO NOT USE FOR section with alternative skill recommendations is particularly effective for disambiguation in a multi-skill environment.

Dimension	Reasoning	Score
Specificity	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.	3 / 3
Completeness	Clearly answers both 'what' (orchestrates Aspire applications using CLI and MCP tools for running, debugging, managing) and 'when' (explicit USE FOR triggers and DO NOT USE FOR exclusions). The DO NOT USE FOR section with alternatives adds exceptional clarity about when to select this skill.	3 / 3
Trigger Term Quality	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 closely match how users would phrase requests.	3 / 3
Distinctiveness Conflict Risk	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.	3 / 3
	Total	12 / 12 Passed

Implementation

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a functional skill that covers the key Aspire workflows (run, stop, debug, update, check resources) with real CLI commands and tool references. Its main weaknesses are verbosity with some redundant sections, vague MCP tool references that lack concrete invocation examples, and missing validation/feedback loops in multi-step workflows. Tightening the content and adding specific tool call examples would significantly improve it.

Suggestions

Show concrete MCP tool invocation examples with parameters and expected output shapes instead of vague 'use the _list resources_ tool' references

Remove the duplicate 'Running the application' section since it overlaps with 'Running Aspire in agent environments' - consolidate into one section

Add explicit validation checkpoints after key steps, e.g., after 'aspire run --detach', show how to verify resources are healthy using list_resources before proceeding

Trim the documentation tools section - Claude can infer a search-then-retrieve workflow; just list the three tools with their parameters concisely

Dimension	Reasoning	Score
Conciseness	The skill contains some unnecessary verbosity and repetition. For example, the 'Running the application' section largely repeats what was already covered in 'Running Aspire in agent environments'. Tool descriptions like 'use this tool to get details about...' are repetitive patterns that could be tightened. The documentation tools section explains basic search-then-retrieve workflows that Claude can infer.	2 / 3
Actionability	The skill provides concrete CLI commands (aspire run --detach --isolated, aspire stop, aspire update) which are good, but MCP tool references are vague ('use the _list resources_ tool') without showing exact tool invocation syntax or parameters. The debugging section lists tools but doesn't show concrete usage examples or expected outputs.	2 / 3
Workflow Clarity	The general recommendations provide a reasonable high-level workflow (run first, make incremental changes, validate). The debugging section has a numbered sequence. However, there are no explicit validation checkpoints or feedback loops - e.g., after running 'aspire run', there's no 'verify resources are healthy by checking X' step. The relaunch rules are clear but lack error recovery guidance.	2 / 3
Progressive Disclosure	The content is organized into logical sections with clear headers, which is good. However, it's somewhat monolithic - the documentation tools section and integration workflow could potentially be split into separate reference files. There are no references to external skill files for deeper topics. The content is all inline at one level.	2 / 3
	Total	8 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: FritzAndFriends/BlazorWebFormsComponents
Commit: 9bf8669

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.