LangBot Deployment Guide
langbot-app/LangBot
Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.
ANALYSIS SKILL - Observe Aspire apps: logs, traces, metrics, resource state, telemetry export, browser telemetry, and the standalone dashboard.
Install Aspire Monitoring
$ npx skills add CommunityToolkit/Aspire --skill aspire-monitoring -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install CommunityToolkit/Aspire aspire-monitoring --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/CommunityToolkit/Aspire.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/aspire-monitoring .claude/skills/aspire-monitoring && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "aspire-monitoring" agent skill from https://github.com/CommunityToolkit/Aspire/tree/main/.agents/skills/aspire-monitoring into .claude/skills/aspire-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aspire-monitoring", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/CommunityToolkit/Aspire/tree/main/.agents/skills/aspire-monitoringType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add CommunityToolkit/Aspire --skill aspire-monitoring -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install CommunityToolkit/Aspire aspire-monitoring --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CommunityToolkit/Aspire.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/aspire-monitoring .agents/skills/aspire-monitoring && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "aspire-monitoring" agent skill from https://github.com/CommunityToolkit/Aspire/tree/main/.agents/skills/aspire-monitoring into .agents/skills/aspire-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aspire-monitoring", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add CommunityToolkit/Aspire --skill aspire-monitoring -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install CommunityToolkit/Aspire aspire-monitoring --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CommunityToolkit/Aspire.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/aspire-monitoring .cursor/skills/aspire-monitoring && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "aspire-monitoring" agent skill from https://github.com/CommunityToolkit/Aspire/tree/main/.agents/skills/aspire-monitoring into .cursor/skills/aspire-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aspire-monitoring", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/CommunityToolkit/Aspire.git --path .agents/skills/aspire-monitoring--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add CommunityToolkit/Aspire --skill aspire-monitoring -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install CommunityToolkit/Aspire aspire-monitoring --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CommunityToolkit/Aspire.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/aspire-monitoring .gemini/skills/aspire-monitoring && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "aspire-monitoring" agent skill from https://github.com/CommunityToolkit/Aspire/tree/main/.agents/skills/aspire-monitoring into .gemini/skills/aspire-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aspire-monitoring", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install CommunityToolkit/Aspire aspire-monitoringInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add CommunityToolkit/Aspire --skill aspire-monitoring -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/CommunityToolkit/Aspire.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/aspire-monitoring .github/skills/aspire-monitoring && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "aspire-monitoring" agent skill from https://github.com/CommunityToolkit/Aspire/tree/main/.agents/skills/aspire-monitoring into .github/skills/aspire-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aspire-monitoring", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add CommunityToolkit/Aspire --skill aspire-monitoring -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install CommunityToolkit/Aspire aspire-monitoring --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CommunityToolkit/Aspire.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/aspire-monitoring .opencode/skills/aspire-monitoring && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "aspire-monitoring" agent skill from https://github.com/CommunityToolkit/Aspire/tree/main/.agents/skills/aspire-monitoring into .opencode/skills/aspire-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aspire-monitoring", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
aspire-monitoring- GitHub stars
- 627
- Token cost
- ~3.5k tokens
- SKILL.md length
- 1,414 words
- Files
- 4 (incl. references)
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- MIT
At a glance
ANALYSIS SKILL - Observe Aspire apps: logs, traces, metrics, resource state, telemetry export, browser telemetry, and the standalone dashboard.
- Works in 5 steps: Is this about AppHost code or deployment… → Is the app running locally via aspire… → Is it deployed to AKS? → kubectl +… → …
- Aspire otel logs
- SKILL.md covers Diagnostics Bridge — Where To…, Investigation Workflow, Local Commands Reference and Version-Specific Diagnostics, plus 7 more sections
- Calls docker, kubectl and jq; needs DASHBOARD_API_KEY
What it does
Aspire Monitoring is an agent skill from CommunityToolkit/Aspire. ANALYSIS SKILL - Observe Aspire apps: logs, traces, metrics, resource state, telemetry export, browser telemetry, and the standalone dashboard. Routes between local Aspire CLI, AKS workload diagnostics, and deployed Azure resource health. USE FOR: aspire logs, aspire otel logs, aspire otel traces, aspire otel spans, aspire describe, aspire ps, aspire export, aspire dashboard run, describe --include-hidden, browser logs in dashboard, terminal view, DevTunnel URLs, WithBrowserLogs, App Insights query, AKS pod logs…
Its SKILL.md is about 3.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/diagnostics-bridge.md`, `references/monitoring.md` and `references/playwright-handoff.md`).
It sits in DevOps & Cloud, covering Container orchestration and Deployment. It works with Microsoft Azure, OpenTelemetry, Kubernetes and Docker. The repository describes itself as: A community project with additional components and extensions for Aspire. The licence is MIT.
When your agent uses it
- Aspire otel logs
- Aspire otel traces
- Aspire otel spans
- Aspire describe
Example prompts
- “/aspire-monitoring”
Requirements
- Docker
- A credential in DASHBOARD_API_KEY
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Is this about AppHost code or deployment definition? → aspire-deployment skill.
- Is the app running locally via aspire start? → Aspire CLI.
- Is it deployed to AKS? → kubectl + Container Insights for workload; azure-diagnostics for the cluster's Azure resources.
- Is it deployed to other Azure (App Service, Container Apps)? → azure-diagnostics.
- Is it deployed to Docker / Compose? → docker / docker compose CLI.
What it can do on your machine
Read from SKILL.md and the folder at commit 853823c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
dockerkubectljq
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
DASHBOARD_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Aspire Monitoring loads about 3.5k tokens when it runs, and up to ~10k if it reads all its reference files. Until then it costs about 237 tokens; SKILL.md has 1,414 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from CommunityToolkit/Aspire at commit 853823c, republished under its MIT licence (© CommunityToolkit). 1,414 words, ~3,480 tokens.
Download SKILL.mdSave it as
.claude/skills/aspire-monitoring/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- aspire-monitoring
- description
- **ANALYSIS SKILL** - Observe Aspire apps: logs, traces, metrics, resource state, telemetry export, browser telemetry, and the standalone dashboard. Routes between local Aspire CLI, AKS workload diagnostics, and deployed Azure resource health. USE FOR: aspire logs, aspire otel logs, aspire otel traces, aspire otel spans, aspire describe, aspire ps, aspire export, aspire dashboard run, describe --include-hidden, browser logs in dashboard, terminal view, DevTunnel URLs, WithBrowserLogs, App Insights query, AKS pod logs, container app logs. DO NOT USE FOR: start/stop/wait (use aspire-orchestration), deploy/publish/destroy (use aspire-deployment), AppHost code edits like WithBrowserLogs() (use aspireify), Azure provisioning (use azure-prepare). INVOKES: aspire CLI, azure-diagnostics (deployed Azure), kubectl + Container Insights. FOR SINGLE OPERATIONS: Run the aspire CLI command directly for quick log or describe lookups.
- license
- MIT
- metadata.author
- Microsoft
- metadata.version
- 0.0.3
Aspire Monitoring
Aspire CLI provides full observability locally. For deployed apps, route to platform-specific tools.
Diagnostics Bridge — Where To Look
| Need | Environment | Tool | Command / Route |
|---|---|---|---|
| Console logs | Local dev | Aspire CLI | aspire logs <resource> |
| Structured logs | Local dev | Aspire CLI | aspire otel logs [resource] |
| Distributed traces | Local dev | Aspire CLI | aspire otel traces [resource] |
| Span detail | Local dev | Aspire CLI | aspire otel spans [resource] |
| Running AppHosts | Local dev | Aspire CLI | aspire ps |
| Resource state | Local dev | Aspire CLI | aspire describe (add --include-hidden if a resource is missing) |
| Telemetry export | Local dev | Aspire CLI | aspire export [resource] |
| Standalone dashboard | Any (no AppHost) | Aspire CLI | aspire dashboard run (foreground/blocking — see below) |
| Browser console / network / diagnostics | Local dev (frontend) | Aspire CLI + dashboard | Discover <frontend>-browser-logs, start its tracked browser, then inspect its console logs |
| AppHost / deployment definition | Authoring | aspire-deployment skill | → aspire-deployment skill |
| AKS workload (pod logs, pod state) | Deployed AKS | kubectl + Container Insights | kubectl logs <pod>, kubectl describe pod <pod>, Container Insights in Azure Monitor |
| Azure resource health (App Insights, Front Door, NSP, private endpoint) | Deployed Azure | azure-diagnostics | → azure-diagnostics skill |
| App Service / Container Apps logs | Deployed Azure | azure-diagnostics | → azure-diagnostics skill |
| Logs/state | Deployed Docker / Compose | Docker CLI | docker logs <container>, docker compose logs <service> |
Decision tree:
- Is this about AppHost code or deployment definition? →
aspire-deploymentskill. - Is the app running locally via
aspire start? → Aspire CLI. - Is it deployed to AKS? → kubectl + Container Insights for workload;
azure-diagnosticsfor the cluster's Azure resources. - Is it deployed to other Azure (App Service, Container Apps)? →
azure-diagnostics. - Is it deployed to Docker / Compose? →
docker/docker composeCLI.
See diagnostics-bridge.md for detailed routing.
Investigation Workflow
When something is wrong, investigate before editing code:
aspire describe— check resource state and endpointsaspire otel logs <resource>— structured logs firstaspire logs <resource>— console output as secondary viewaspire otel traces <resource>— cross-service activityaspire export— zipped telemetry snapshot for deeper analysis
Local Commands Reference
| Command | Purpose | Example |
|---|---|---|
aspire logs <resource> | Console stdout/stderr | aspire logs apiservice |
aspire logs --follow | Stream logs in real-time | aspire logs apiservice --follow |
aspire otel logs | Structured OpenTelemetry logs | aspire otel logs |
aspire otel traces | Distributed trace data | aspire otel traces |
aspire otel spans | Individual span detail | aspire otel spans |
aspire otel logs --trace-id <id> | Logs correlated to trace (⚠️ verify flag) | aspire otel logs --trace-id abc123 |
aspire otel logs --dashboard-url | Query a standalone dashboard (login URL or base URL + --api-key) | aspire otel logs --dashboard-url "http://localhost:18888/login?t=TOKEN" --follow |
aspire otel traces --dashboard-url | Query a standalone dashboard | aspire otel traces --dashboard-url "http://localhost:18888/login?t=TOKEN" |
aspire describe | Resource state, endpoints, health | aspire describe --format Json |
aspire describe --include-hidden | Include proxies, helper containers, migrations | aspire describe --include-hidden --format Json |
aspire resources | Compatibility alias for resource state | Prefer aspire describe in new guidance |
aspire export | Portable telemetry bundle | aspire export |
aspire dashboard run | Standalone dashboard (foreground/blocking) | aspire dashboard run |
Hidden resources are filtered by default
aspire describe and other CLI commands filter out resources marked hidden in the AppHost (proxies, helper containers, migrations). The default output is correct for normal app inspection. Add --include-hidden when:
- Debugging proxies, sidecar/helper containers, or migration jobs.
- An expected resource is "missing" from
aspire resources/aspire describe. - Triaging connectivity or wiring issues that may involve infrastructure resources.
Tips for Agents
# ✅ Use --format Json for machine parsing (supported: describe, start)
aspire describe --format Json
# ✅ When a resource you expect is missing, retry with --include-hidden
aspire describe --include-hidden --format Json
# ✅ Get endpoints from describe, not guessing ports
ENDPOINT=$(aspire describe apiservice --format Json | jq -r '.endpoints[0].url')
# ✅ Use --apphost <path> when multiple AppHosts exist
aspire describe --apphost ./src/MyApp.AppHost/Version-Specific Diagnostics
Check the running dashboard version and actual error before applying a historical fix. An older fix does not establish that downgrading a newer dashboard is a working mitigation, even temporarily or in an isolated test.
| Symptom | Guidance |
|---|---|
Resource missing from aspire describe | Re-run aspire describe --include-hidden; do not use removed aspire ps --include-hidden. |
| DevTunnel is healthy but has no public URL on 13.5.0-13.5.2 | Fixed in 13.5.3. Use a compatible release containing the fix before changing endpoint configuration. |
| Known multi-path icon Graph crash on 13.5.0-13.5.2 | Fixed in 13.5.3. Use a compatible release containing the fix. |
| Dashboard Graph crashes on 13.5.3 or later | Keep the selected version. Capture the browser console stack trace and dashboard logs to diagnose a separate cause or regression; do not recommend installing 13.5.3 as a workaround. |
Resolved in 13.3: The standalone-dashboard workaround for #16236 is obsolete — use
aspire dashboard run(see below).
Standalone Dashboard (aspire dashboard run)
aspire dashboard run launches the Aspire Dashboard without an AppHost, so any OTLP-emitting application (Aspire or not) can stream telemetry into it.
aspire dashboard run
# Dashboard: http://localhost:18888/login?t=<TOKEN>
# OTLP/gRPC: http://localhost:4317
# OTLP/HTTP: http://localhost:4318⚠️ Foreground / blocking.
aspire dashboard rundoes not return until you stop it (Ctrl-C). Agents must treat it as a long-running background process — start it with the bash tool'smode="async", capture the dashboard URL and token from initial output, and leave it running. Do not invoke it as a one-shot synchronous command, and do not wait for it to "finish".
Connect the Aspire CLI to a standalone dashboard
aspire otel logs and aspire otel traces accept --dashboard-url. The simplest form passes the full login URL printed by aspire dashboard run — the CLI normalizes it automatically:
# Stream structured logs from a standalone dashboard (login URL form)
aspire otel logs --dashboard-url "http://localhost:18888/login?t=TOKEN" --follow
# Search recent traces
aspire otel traces --dashboard-url "http://localhost:18888/login?t=TOKEN"For dashboards configured with API-key authentication (e.g., the standalone container image with a separate API key), pass --api-key alongside the base --dashboard-url:
aspire otel logs --dashboard-url https://my-dashboard.example.com --api-key "$DASHBOARD_API_KEY" --followThe container-image standalone dashboard still works for environments where the CLI isn't available.
Show full SKILL.md (582 more words)Show less
Browser Logs (Aspire.Hosting.Browsers)
When a frontend has already opted into WithBrowserLogs(), Aspire creates a child resource named
<frontend>-browser-logs. Browser console messages, errors, exceptions, and network diagnostics
are sent to that child resource's console log stream, not to the frontend's OpenTelemetry logs.
Begin with normal
aspire describeoraspire resourcesoutput to find<frontend>-browser-logs;aspire psno longer lists resources. It is a normal child resource, so retry withaspire describe --include-hiddenonly if unavailable.Correlate it to the frontend through its parent relationship and
Sourceproperty.Start a tracked browser session with:
bash aspire resource <frontend>-browser-logs open-tracked-browserInspect the browser diagnostics with:
bash aspire logs <frontend>-browser-logs
Do not use aspire otel logs <frontend> for browser output; it does not return that child
resource's browser diagnostics.
| Need | Action |
|---|---|
| Inspect existing browser diagnostics | Discover <frontend>-browser-logs, start open-tracked-browser, then run aspire logs <frontend>-browser-logs |
| Confirm the browser resource belongs to a frontend | Check the child resource's parent relationship and Source property |
| Confirm a frontend has browser logging enabled | Check the AppHost for .WithBrowserLogs() on the resource |
Add WithBrowserLogs() to a resource | → aspireify skill (AppHost authoring) — do not edit the AppHost from this skill |
Dashboard UX Features
Agents inspecting a running dashboard should know:
- Notification center (bell icon, top-right) — surfaces results of resource commands and lifecycle events. Inline command responses appear here instead of being scraped from the logs panel.
- Rebuild command — available on container and project resources; rebuilds the image and restarts the resource without restarting the whole AppHost. Result lands in the notification center.
- Structured command results — custom resource commands return
ExecuteCommandResultwith aMessagepayload that the dashboard renders inline; HTTP commands setHttpCommandResultMode.Auto | Json | Text | Noneto control how the response body is shown. - 13.5 filtering — filter telemetry by timestamp, use
==/!=for exact numeric values, and search console-log text while streams continue updating. - Terminal view — resources configured with experimental
WithTerminal()open as interactive sessions in the dashboard. - No dashboard AI Assistant — it was removed in 13.5. Use
aspire agent initand the AppHost/CLI agent integration instead. - VS Code launch is opt-in — the Aspire extension no longer opens the dashboard
automatically. Use its in-editor dashboard or configure
dashboardBrowser/launch.json.
Authoring custom commands or
WithBrowserLogs()calls is AppHost work — route toaspireify. This skill is for observing what those features surface in the dashboard.
Why Aspire CLI Can't Do Remote Diagnostics
The Aspire CLI talks to a running AppHost through a local backchannel socket at ~/.aspire/backchannels/. This is by design — there is no remote backchannel. For deployed apps, route to platform-specific tools (azure-diagnostics, kubectl, docker).
Exception: if a Dashboard is reachable (deployed alongside the app, or running standalone), aspire otel logs and aspire otel traces can query it via --dashboard-url (login URL form) and optional --api-key (see the Standalone Dashboard section above). This does not apply to aspire logs or aspire describe.
Handoff Rules
| Scenario | Route To |
|---|---|
| Start/stop/wait/rebuild lifecycle | → aspire-orchestration skill |
| Deploy, publish, pipeline steps, AppHost compute environment binding | → aspire-deployment skill |
AppHost code changes (WithBrowserLogs(), custom commands, WithHttpCommand) | → aspireify skill |
| Deployed Azure resource health (App Insights, Front Door, NSP, private endpoint, ACA, App Service) | → azure-diagnostics skill (azure-skills) |
| AKS workload diagnostics (pod logs, pod state, Container Insights) | → kubectl + Azure Monitor Container Insights |
| Docker / Compose container logs | → docker logs / docker compose logs |
Project-Local Skill Routing
If .agents/skills/aspire/SKILL.md exists (from aspire agent init), see its
references/monitoring.md for deeper telemetry workflow guidance.
References
- diagnostics-bridge.md — Local vs deployed routing detail
- monitoring.md — Telemetry inspection and export patterns
- playwright-handoff.md — Find the correct Aspire frontend URL before browser testing
© CommunityToolkit, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references) in .agents/skills/aspire-monitoring of CommunityToolkit/Aspire.
- SKILL.md
- references/diagnostics-bridge.md
- references/monitoring.md
- references/playwright-handoff.md
Open the folder on GitHubat commit 853823c
Compare with similar skills
Aspire Monitoring next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Aspire Monitoring this skillCommunityToolkit/Aspire | 627 | — | ~3.5k | Automated safety check: Pass | MIT | |
| LangBot Deployment Guidelangbot-app/LangBot | 18k | — | ~1.5k | Automated safety check: Notes | Apache-2.0 | |
| Aspiremicrosoft/aspire.dev | 195 | 4 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Debug Openshell ClusterNVIDIA/OpenShell | 16k | — | ~20k | Automated safety check: Notes | Apache-2.0 | |
| Kcli Cluster Deploymentkarmab/kcli | 653 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Aks Deployment Skilltimothywarner/chatgptclass | 143 | — | ~916 | Automated safety check: Pass | Custom licence |
Similar skills
- Official
Aspire
microsoft/aspire.dev
Orchestrates Aspire distributed applications using the Aspire CLI for running, debugging, and managing distributed apps.
- Official
Debug Openshell Cluster
NVIDIA/OpenShell
Debug why an OpenShell gateway deployment is unhealthy, unreachable, or unable to create sandboxes.
Kcli Cluster Deployment
karmab/kcli
Guides deployment and management of Kubernetes clusters with kcli.
Aks Deployment Skill
timothywarner/chatgptclass
Deploy and operate workloads on Azure Kubernetes Service (AKS) the safe way.
- Official
Ama Logs Update Charts Release Notes
microsoft/Docker-Provider
Prepare an ama-logs release PR: bump the image tag (X.Y.Z) across Helm charts, manifests, and Dockerfiles, and add a formatted ReleaseNotes.md entry.
More from CommunityToolkit/Aspire
All 8 skills in this repoDotnet Inspect
CommunityToolkit/Aspire
Query .NET APIs across NuGet packages, platform libraries, and local files.
Aspireify
CommunityToolkit/Aspire
WORKFLOW SKILL - Wire Aspire AppHosts or repair TypeScript AppHost toolchains.
Aspire Deployment
CommunityToolkit/Aspire
WORKFLOW SKILL — Deploy Aspire apps from AppHost models to Docker Compose, Kubernetes, Azure, AWS, or preview Radius.
Aspire Project V2 Migration
CommunityToolkit/Aspire
WORKFLOW SKILL - Safely migrates eligible Aspire 13.6+ AppHosts from legacy ProjectResource APIs to experimental DotnetProjectResource APIs after a per-resource assessment and explicit approval of…
Aspire Typescript Apphost
CommunityToolkit/Aspire
Generate a TypeScript AppHost from an existing C example AppHost, then add a TypeScriptAppHostTest-based integration test.
Aspire Upgrade
CommunityToolkit/Aspire
Update the Aspire version in the repository to the latest nightly build.
Related
Categories
Questions about Aspire Monitoring
What does Aspire Monitoring do?
ANALYSIS SKILL - Observe Aspire apps: logs, traces, metrics, resource state, telemetry export, browser telemetry, and the standalone dashboard. Aspire Monitoring is an agent skill from CommunityToolkit/Aspire. ANALYSIS SKILL - Observe Aspire apps: logs, traces, metrics, resource state, telemetry export, browser telemetry, and the standalone dashboard.
When should I use Aspire Monitoring?
Aspire Monitoring fits situations like: aspire otel logs; aspire otel traces; aspire otel spans; aspire describe.
How do I install Aspire Monitoring in Claude Code?
Run `npx skills add CommunityToolkit/Aspire --skill aspire-monitoring -a claude-code`. Or copy the skill folder (.agents/skills/aspire-monitoring in CommunityToolkit/Aspire) into .claude/skills/aspire-monitoring in your project. Claude Code loads it when a task matches its description.
How do I install Aspire Monitoring in Codex?
Run `npx skills add CommunityToolkit/Aspire --skill aspire-monitoring -a codex`. Or copy the skill folder (.agents/skills/aspire-monitoring in CommunityToolkit/Aspire) into .agents/skills/aspire-monitoring in your project. Codex loads it when a task matches its description.
Can I use Aspire Monitoring in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add CommunityToolkit/Aspire --skill aspire-monitoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/aspire-monitoring, .gemini/skills/aspire-monitoring, .github/skills/aspire-monitoring and .opencode/skills/aspire-monitoring in your project.
What does Aspire Monitoring need to run?
Going by SKILL.md and its folder, Aspire Monitoring needs the command-line tools its instructions call (docker, kubectl and jq) and credentials named DASHBOARD_API_KEY. Our summary lists: Docker; A credential in DASHBOARD_API_KEY.
Does Aspire Monitoring access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Aspire Monitoring safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Aspire Monitoring use?
Aspire Monitoring is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Aspire Monitoring use?
About 3.5k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.5k tokens, read only when the agent opens those files.
What are the alternatives to Aspire Monitoring?
Skills that share tags, products or a category with Aspire Monitoring: LangBot Deployment Guide (langbot-app/LangBot, 18k stars), Aspire (microsoft/aspire.dev, 195 stars), Debug Openshell Cluster (NVIDIA/OpenShell, 16k stars) and Kcli Cluster Deployment (karmab/kcli, 653 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Aspire Monitoring?
CommunityToolkit (a GitHub organization) maintains it in CommunityToolkit/Aspire, which has 627 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 9, 2026.
Source: CommunityToolkit/Aspire on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.