# Installation and host behavior

The repository has one router (`zen`) and 21 focused `zen-*` skills. Install the router alongside chosen modes so shared references and the standalone writer are available. A complete local install includes every folder under the release's skills directory. Skill installation does not pair a device or grant execution permissions.

The proposed public command is `npx skills@latest add sico-vibes/zen-skills`; it works only after that repository is actually published. For a local exported directory use the installed Skills CLI's `add <absolute-export-path> --agent <host> --skill '*' --copy` options after checking its help. Do not change global profiles merely to test an installation; use a clean temporary project.

Codex installations normally discover skills under `.agents/skills` and support explicit `$zen` / `$zen-research` selection when the host offers it. Claude Code normally discovers `.claude/skills` and exposes installed skill names such as `/zen-research`; its `/zen research` form can route through the router if that skill is installed. OpenCode/other compatible hosts may discover `.agents/skills` or their configured directories; inspect that installation before promising a slash alias. Natural-language routing and explicitly reading the selected SKILL.md remain valid fallbacks. Do not invent nested Skill-tool calls on a host that lacks that tool.

If only one mode is installed and a shared reference is absent, follow that mode's procedure and produce its output as a clearly labelled draft. Do not claim persistence. Install/copy the router when actual file-only records are wanted; do not fetch unrelated skills silently.

For a companion checkout, start its documented companion command, then connect its stdio MCP command (`pnpm mcp` in that checkout, or the separately installed companion package's mcp command). Discover tools and workspace IDs after connecting. The public skill package does not contain protected credentials or the companion runtime. A stopped/unpaired device is an explicit unavailable state, not a reason to drive the dashboard visually or bypass local authority.

An owner-selected CLI/model/effort controls task execution. Reading these instructions, invoking a slash skill, or installing a package never supplies missing model selection. The lowest suitable librarian model is configuration, not a hardcoded provider/tier. Single-model hosts use that selected model; provider switches and paid fallbacks require the owner's choice.