CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

65

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/aspire/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%Weight 40%Scale 1-5

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

An actionable, well-sectioned instruction skill with concrete CLI commands and named MCP tools. It is held back by some redundant/explanatory padding and workflows that lack explicit validation checkpoints.

Suggestions

Consolidate the duplicate aspire run guidance from 'Running Aspire in agent environments' and 'Running the application' into a single section to remove repetition.

Add an explicit validation checkpoint to the change workflow (e.g. after aspire run, use list_resources to confirm each resource is Healthy before proceeding).

Trim the introductory sentence explaining what Aspire is, since Claude already knows the framework's role.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands, but includes some unnecessary explanation (e.g. 'Aspire is an orchestrator for the entire application and will take care of configuring dependencies, building, and running the application') and repeats aspire run guidance across the 'Running Aspire in agent environments' and 'Running the application' sections.

3 / 5

Actionability

Provides concrete executable commands (aspire run --detach --isolated, aspire stop, aspire update, dotnet tool install --global dotnet-outdated-tool) and names specific MCP tools, with only minor gaps where tools are referenced by descriptive name rather than exact identifier.

4 / 5

Workflow Clarity

A rough sequence exists in the General recommendations (run apphost, inspect resources, change incrementally, validate) and debugging tool ordering, but validation checkpoints are implicit and there is no explicit validate-then-proceed feedback loop.

3 / 5

Progressive Disclosure

Single file with no bundle references and clear section headers (Running, Stopping, Checking resources, Listing integrations, Debugging, Updating app host) providing good organization; minor gaps from redundant run sections.

4 / 5

Total

14

/

20

Passed

Description

95%Weight 40%Scale 1-5

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

A strong, well-structured description with explicit what/when guidance, comprehensive natural trigger terms, and clear boundary disambiguation. The only weakness is a second-person imperative clause that triggers the voice penalty on specificity.

DimensionReasoningScore

Specificity

Lists many concrete actions in the USE FOR clause (aspire run, aspire stop, list aspire integrations, debug aspire issues, update aspire apphost, etc.) for comprehensive coverage, but the imperative 'Use Aspire MCP tools directly' clause is second-person voice, triggering the rubric's -1 specificity penalty.

4 / 5

Completeness

Explicitly answers 'what' ('Orchestrates Aspire applications using the Aspire CLI and MCP tools for running, debugging, and managing distributed apps') and 'when' via a concrete USE FOR trigger list plus a DO NOT USE FOR boundary clause.

5 / 5

Trigger Term Quality

The USE FOR list comprehensively covers natural phrases a user would say ('aspire run', 'start aspire app', 'debug aspire issues', 'view aspire logs', 'aspire dashboard') including command-style synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

The DO NOT USE FOR clause explicitly disambiguates from dotnet CLI, docker/podman, and the azure-deploy skill, giving it a clear niche with minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
FritzAndFriends/BlazorWebFormsComponents
Reviewed

Table of Contents

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.