Expecho/Agent42 / .claude/skills/aspire
aspire
VerifiedUse this skill when the user is working with an Aspire distributed application and needs to operate the AppHost or its resources through the Aspire CLI: start, restart, stop, or wait on the app; inspect resources, logs, traces, docs, or health; add integrations; manage secrets or config; publish, deploy, or rerun a named pipeline step; initialize Aspire in an existing app; recover missing `.modules` files in a TypeScript AppHost; discover the right frontend URL for Playwright from Aspire state; expose custom dashboard/resource commands; or understand unfamiliar Aspire AppHost APIs in C# or TypeScript. Use it even if they describe the task in terms of an AppHost, resources, dashboard, existing app bootstrap, missing generated modules, Playwright URL discovery, C# API understanding, or local distributed app workflow without explicitly naming Aspire. Do not use it for non-Aspire .NET apps, container-only repos with no AppHost, or ordinary build and test tasks.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.9 KB |
| references/agent-workflows.md | markdown | 3.5 KB |
| references/app-commands.md | markdown | 2.5 KB |
| references/csharp-apphosts.md | markdown | 1.4 KB |
| references/deployment.md | markdown | 1.4 KB |
| references/monitoring.md | markdown | 3.3 KB |
| references/playwright-handoff.md | markdown | 963 B |
| references/resource-management.md | markdown | 1.5 KB |
| references/tools-and-configuration.md | markdown | 2.6 KB |
| references/typescript-apphosts.md | markdown | 1.4 KB |
references/monitoring.md
View on GitHub# Monitoring
Use this when the task is about inspecting app state, logs, traces, endpoints, or sharable diagnostics.
## Scenario: I Need To Know What Is Running And Where The Endpoints Are
Use these commands when the first job is to inspect current resource state, find URLs, or hand machine-readable app state to another tool.
```bash
aspire describe
aspire resources
aspire describe --apphost <path>
aspire describe --apphost <path> --format Json
```
Keep these points in mind:
- Use `aspire describe` first when you need the current state of the running app before deciding what to do next.
- Use `--apphost <path>` when the workspace has multiple AppHosts or discovery is ambiguous.
- Prefer `--format Json` when another tool or script needs to consume the result, such as a Playwright handoff or endpoint extraction.
## Scenario: Something Is Wrong, But Investigate Before Editing Code
Use these commands when the task is to diagnose behavior in the live app before making code changes.
```bash
aspire otel logs [resource] --format Json
aspire otel traces [resource] --format Json
aspire otel spans [resource] --format Json
aspire otel logs --trace-id <id> --format Json
aspire logs [resource]
```
Keep these points in mind:
- Prefer structured telemetry before raw console logs when possible.
- Use `aspire logs` as a secondary console-output view after checking structured telemetry.
- Use the trace-filtered log command when you already have a trace id and want the related log slice.
- Prefer `--format Json` when another tool or script needs to consume the result, such as a Playwright handoff or endpoint extraction.
- `[resource]` is optional. Include it to filter results to a single resource; omit it to see all resources.
## Scenario: I Need A Sharable Diagnostics Bundle
Use this command when you need a portable handoff artifact for deeper analysis or for another person to inspect offline.
```bash
aspire export [resource]
```
Keep this point in mind:
- Use `aspire export` when you need a sharable bundle of telemetry and resource state.
## Dashboard Links
Commands like `aspire describe`, `aspire otel logs`, `aspire otel traces`, and `aspire otel spans` may include dashboard URLs in their JSON output. Only use URLs that are explicitly returned by these commands β do not construct dashboard URLs yourself.
When a dashboard link is returned alongside a resource or telemetry entry, make the resource name, trace ID, or span ID a clickable markdown link using the returned URL.
## Displaying Resources
When showing resource state to the user, display the state text with a circle emoji prefix:
- π’ Running, healthy
- π‘ Starting, waiting
- π΄ Failed, error, unhealthy
- βͺ Stopped, exited
Link resource names to their dashboard page when the dashboard URL is known.
## Displaying Telemetry
When showing structured logs, prefix each entry with an emoji matching the log level:
- π΄ Error / Critical
- π‘ Warning
- π΅ Information
- βͺ Debug / Trace
Link resource names to their dashboard resource page. When trace IDs are present, display the first 7 characters and link that value to the full trace detail page.
When showing traces or spans, use π’ for success/unset status and π΄ for error status. Display only the first 7 characters of trace and span IDs, and link those values to their dashboard detail pages.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |