cli-channel-debugging Skill
Emulates any Aspire CLI build identity (channel, version, commit, package source) from a locally built CLI using ASPIRECLI environment variables and the install sidecar, so a reported bug can be reproduced and fixed locally without going through the install/PR loop. Use this when asked to reproduce channel/version/qual Published by microsoft in aspire.
What is cli-channel-debugging Skill?
Emulates any Aspire CLI build identity (channel, version, commit, package source) from a locally built CLI using ASPIRECLI environment variables and the install sidecar, so a reported bug can be reproduced and fixed locally without going through the install/PR loop. Use this when asked to reproduce channel/version/qual Published by microsoft in aspire. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Documentation
- Design and media
- Writing
- Documentation use cases
- Design and media use cases
Technical details
- Install or run with Copy skill directory
When to use cli-channel-debugging Skill
- Use it for documentation.
- Use it for design and media.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/aspire
- Skill file: .agents/skills/cli-channel-debugging/SKILL.md
What it does
Emulates any Aspire CLI build identity (channel, version, commit, package source) from a locally built CLI using ASPIRECLI environment variables and the install sidecar, so a reported bug can be reproduced and fixed locally without going through the install/PR loop. Use this when asked to reproduce channel/version/qual
Skill instructions
You are a specialized agent for reproducing version/channel/quality-specific Aspire CLI behavior from a locally built CLI. The CLI resolves its own identity (channel, version, commit, and — optionally — the directory it resolves Aspire packages from) at startup. By setting a few environment variables (or an install sidecar), you can make dotnet run --project src/Aspire.Cli -- <cmd behave as if it were any released, staging, daily, or PR build. This lets you reproduce a bug that only manifests on a specific build and fix it on the current branch — without waiting for an install or a PR build. Read docs/specs/cli-identity-sidecar.md for the full design. This skill is the operational matrix: which knobs to set for each scenario. ⛔ MANDATORY: State the scenario and exact knobs in chat before running Before you run any emulated CLI command, you MUST write a short line in chat declaring: 1. Which scenario row (1–7b below) you are emulating. 2. The exact environment variables and values you a
Explore related resources
Frequently asked questions
What is cli-channel-debugging?
cli-channel-debugging is a open-source AI agent skill with Copy skill directory. Emulates any Aspire CLI build identity (channel, version, commit, package source) from a locally built CLI using ASPIRECLI environment variables and the install sidecar, so a reported bug can be.
Who is cli-channel-debugging best for?
cli-channel-debugging is best for reusing agent instructions, scripts, and references, documentation workflows, design and media workflows, writing workflows.
How do I install cli-channel-debugging?
Install or run cli-channel-debugging using Copy skill directory. Check cli-channel-debugging for the latest setup command.
Is cli-channel-debugging actively maintained?
cli-channel-debugging may need a closer maintenance check before production use.
Auto-fetched from GitHub.
