Originally created by: kumaakh
Every install example in the docs ends with `--skill`. Users and agents copy-paste it without knowing what it means, and the FAQ has a question explaining it. Multiple users have asked why they need to specify it every time if everyone needs it.
The current mental model is: `install` = bare server, `install --skill` = full setup. But in practice nobody wants the bare server.
Introduce a named skill set argument so users can precisely control what gets installed. Default to `all` so bare `install` gives the full experience.
| Command | Installs |
|---|---|
| `apra-fleet install` | MCP server + fleet skill + PM skill (default = `all`) |
| `apra-fleet install --skill all` | Same as above |
| `apra-fleet install --skill pm` | MCP server + fleet skill + PM skill |
| `apra-fleet install --skill fleet` | MCP server + fleet skill only (no PM) |
| `apra-fleet install --skill none` | MCP server only, no skills |
| `apra-fleet install --no-skill` | Same as `--skill none` |
Skill hierarchy: PM depends on fleet — installing `pm` always includes `fleet`. Installing `fleet` alone gives the raw tools without the PM orchestration layer.
Once this ships, every install example simplifies:
Before:
```bash
curl -fsSL .../apra-fleet-darwin-arm64 -o apra-fleet && chmod +x apra-fleet && ./apra-fleet install --skill
```
After:
```bash
curl -fsSL .../apra-fleet-darwin-arm64 -o apra-fleet && chmod +x apra-fleet && ./apra-fleet install
```
Files to update: `README.md`, `docs/user-guide.md`, `docs/FAQ.md`, `skills/pm/deploy.md`.
The "Omit `--skill` if you only need basic fleet operations" note in the user guide can be replaced with a brief mention of `--skill none` / `--no-skill` for minimal installs.
Originally posted by: kumaakh
When this ships, also complete [#136] — the user guide needs a visible explainer of what
installdoes and what each--skilloption installs.Related
Tickets:
#136Ticket changed by: kumaakh