Skip to content

[docs] Update aspire agent init docs for bundle-derived skill catalog (13.4) #1129

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
aspire-repo-bot wants to merge 1 commit into
base: release/13.4
Choose a base branch
from
+12 −2
Open

[docs] Update aspire agent init docs for bundle-derived skill catalog (13.4) #1129

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 12 additions & 2 deletions src/frontend/src/content/docs/reference/cli/commands/aspire-agent-init.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ aspire agent init [options]
The `aspire agent init` command initializes skill files and MCP (Model Context Protocol) server configuration for your development environment. It presents an interactive multi-step flow to configure AI coding agent support:

1. **Select skill locations** — choose where skill files are installed (Standard `.agents/skills/`, Claude Code `.claude/skills/`, GitHub Skills `.github/skills/`, OpenCode `.opencode/skill/`). The **Standard** location is the only option that defaults as pre-selected.
2. **Select skills and tools** — choose which skills to install (Aspire skill, Playwright CLI, dotnet-inspect skill). All options are pre-selected by default.
2. **Select skills and tools** — the available skill catalog is loaded from the Aspire skills bundle manifest, so the list includes all bundle-provided skills (such as `aspire-init`, `aspire-monitoring`, and `aspire-orchestration`) in addition to the CLI-defined skills (`playwright-cli`, `dotnet-inspect`). All catalog skills are pre-selected by default, except one-time workspace-wiring skills (such as `aspireify`) that are omitted from the defaults when running against an existing project.
Copy link
Copy Markdown
Member

@IEvangelist IEvangelist May 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Phase A nuance + Phase B warning (line 27): the sentence "All catalog skills are pre-selected by default, except one-time workspace-wiring skills (such as aspireify) that are omitted from the defaults when running against an existing project." reads as a universal rule but only applies to the standalone aspire agent init command documented here.

In microsoft/aspire release/13.4 @ e258349fd:

  • AgentInitCommand.cs:141-143 — standalone agent init excludes aspireify by default (matches this doc).
  • InitCommand.cs:171-173 — aspire init (which also runs against an existing repo) deliberately calls PromptAndChainAsync without the exclusion predicate, so aspireify IS pre-selected there. The source comment: "aspire init creates an AppHost in an existing repo, so pre-select every bundle skill (which includes aspireify as the natural follow-up wiring skill)."

The aspire init docs page advertises this behavior too — it has a dedicated "The aspireify skill" section. A reader hopping between pages will see two different defaulting behaviors for the same "existing project" scenario.

Suggested wording: "In this standalone command, one-time workspace-wiring skills (such as aspireify) are not pre-selected. Use aspire init to install the AppHost and pre-select aspireify together as part of that flow."

3. **Apply selections** — installs the chosen skills into each selected location and sets up the MCP server connection.

The command also removes skill files from any locations that were deselected, keeping your workspace clean.
Expand All @@ -43,7 +43,11 @@ The following options are available:

- **`--skills <skills>`**

Comma-separated list of skills to enable, such as `aspire`, `aspireify`, `playwright-cli`, or `dotnet-inspect`. Use `all` to enable all available skills or `none` to skip skill installation. When not specified, the command prompts interactively.
Comma-separated list of skills to install. Bundle skills are loaded dynamically from the Aspire skills bundle manifest and include skills such as `aspire-init`, `aspire-monitoring`, and `aspire-orchestration`. CLI-provided skills include `playwright-cli` and `dotnet-inspect`. Use `all` to enable all available skills or `none` to skip skill installation. When not specified, the command prompts interactively.

:::note
The full list of available bundle skills depends on the Aspire skills bundle cached or embedded in the CLI. To enable remote fetch of the latest bundle from GitHub, set the `aspireSkillsRemoteFetchEnabled` feature flag to `true` in your Aspire CLI configuration (disabled by default in 13.4).
:::
Comment on lines +48 to +50

- <Include relativePath="reference/cli/includes/option-help.md" />

Expand Down Expand Up @@ -71,6 +75,12 @@ The following options are available:
aspire agent init --skills all --skill-locations all
```

- Install specific bundle skills by name:

```bash title="Aspire CLI"
aspire agent init --skills aspire-monitoring,aspire-orchestration
```

- Initialize agent configuration from a specific workspace root:

```bash title="Aspire CLI"
Expand Down
Loading