How do I install the Ki Bootstrap skill?

Run npx skillmds@latest add knowledgeislands/ki-bootstrap in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ki Bootstrap safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ki Bootstrap?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ki Bootstrap free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ki Bootstrap?

knowledgeislands (@knowledgeislands) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ki Bootstrap by knowledgeislands — Agent Skill

Name: Ki Bootstrap
Author: knowledgeislands

Ki Bootstrap

Explains first-time Knowledge Islands activation through the `ki` CLI: bootstrap a user, select a verified canonical harness, and distinguish user skills from repository-declared governance. Use for guidance on `ki bootstrap`, `ki harness`, `ki skill add/remove`, `ki repo skill add/remove`, and `ki dev local`; the CLI itself owns all mechanics. Triggers: "set up KI", "what does ki bootstrap do", "activate a KI skill", "why won't ki repo audit run". For repository coverage use `ki-repo`; for command behaviour use `ki --help`.

knowledgeislands 9869acd 4 files · 18.8 KB Updated Sep 17, 2026

File contents

Knowledge Islands Bootstrap

The ki CLI owns installation, activation, and repository operations. This guidance-only skill explains that command surface; it has no executable catalogue, checker, or alternative executor.

Read the bootstrap standard when the installation, activation, or trust boundary matters. Use the exemplars for concrete command sequences.

First-time user setup

Run ki bootstrap.

KI detects supported local agent runtimes, creates its XDG configuration if absent, installs the canonical knowledgeislands/ki-agentic-harness, and links the core user skills into each detected agent's user skill directory.

Run ki bootstrap --refresh to redetect agents and reconcile the recorded harness and managed user-skill inventory with installed state.

The user configuration and installed harness payloads are separate from a repository's .ki.toml.

Harnesses and skills

ki harness list, ki harness info <id>, ki harness install <id>, and ki harness uninstall <id> manage compatible installed harnesses. The canonical harness is always retained.

ki skill add <skill> and ki skill remove <skill> manage a skill in configured user agent spaces.

ki repo skill add <skill> and ki repo skill remove <skill> manage a skill's repository declaration and runtime link. They affect only the selected repository; they never alter user activation.

Managed activation is fail-closed. If a link, installed payload, or development projection is unfamiliar, altered, escaping, or otherwise unsafe, use the owning ki diagnostic and repair command; do not copy or delete files across source, installed, and runtime-discovery surfaces. Start a new agent session after changing activation or the selected development source so the runtime re-scans its discovery directories.

Repository operations

.ki.toml declares the skills that govern a repository. ki repo educate, ki repo audit, and ki repo conform resolve only those declarations and their explicit dependencies from installed harnesses.

Missing, incompatible, undeclared, or ambiguous skills fail before an audit or conform operation runs. The CLI executes native rubric catalogues; it never uses repository-vendored runners or .ki/bin wrappers.

Development boundary

An installed verified payload is the authoritative source of capabilities. Local development is explicit: ki dev local set <harness-id> <local-harness-path> validates and records a checkout, ki dev local on [harness-id] selects it, and ki dev local off [harness-id] restores the verified archive. A selected local checkout is a mutable development source, not a verified installed payload; activation and loaded runtime capability remain separate host evidence.

For command grammar, run ki --help. For repository coverage, use ki-repo.

Operating modes

Mode HELP

Explain the first-time bootstrap, installed-harness, user-activation, repository-activation, and native repository-operation boundaries above. Route exact command and option questions to ki --help; route .ki.toml coverage questions to ki-repo.

Mode REFRESH

This mode refreshes guidance, not user or repository state.

Read the source list and re-check the delivered tools-ki command surface, the compatible-harness contract, and the repository declaration contract.
Diff them against the bootstrap standard, this routing overview, and the exemplars.
Update only this skill's guidance and source review record. Record behavioural history in git rather than adding a changelog.

---name: ki-bootstrapdescription: Explains first-time Knowledge Islands activation through the `ki` CLI: bootstrap a user, select a verified canonical harness, and distinguish user skills from repository-declared governance. Use for guidance on `ki bootstrap`, `ki harness`, `ki skill add/remove`, `ki repo skill add/remove`, and `ki dev local`; the CLI itself owns all mechanics. Triggers: "set up KI", "what does ki bootstrap do", "activate a KI skill", "why won't ki repo audit run". For repository coverage use `ki-repo`; for command behaviour use `ki --help`.---# Knowledge Islands BootstrapThe `ki` CLI owns installation, activation, and repository operations. This guidance-only skill explains that command surface; it has no executable catalogue, checker, or alternative executor.Read [the bootstrap standard](references/standards-bootstrap.md) when the installation, activation, or trust boundary matters. Use [the exemplars](references/exemplars.md) for concrete command sequences.## First-time user setupRun `ki bootstrap`.KI detects supported local agent runtimes, creates its XDG configuration if absent, installs the canonical `knowledgeislands/ki-agentic-harness`, and links the core user skills into each detected agent's user skill directory.Run `ki bootstrap --refresh` to redetect agents and reconcile the recorded harness and managed user-skill inventory with installed state.The user configuration and installed harness payloads are separate from a repository's `.ki.toml`.## Harnesses and skills`ki harness list`, `ki harness info <id>`, `ki harness install <id>`, and `ki harness uninstall <id>` manage compatible installed harnesses. The canonical harness is always retained.`ki skill add <skill>` and `ki skill remove <skill>` manage a skill in configured user agent spaces.`ki repo skill add <skill>` and `ki repo skill remove <skill>` manage a skill's repository declaration and runtime link. They affect only the selected repository; they never alter user activation.Managed activation is fail-closed. If a link, installed payload, or development projection is unfamiliar, altered, escaping, or otherwise unsafe, use the owning `ki` diagnostic and repair command; do not copy or delete files across source, installed, and runtime-discovery surfaces. Start a new agent session after changing activation or the selected development source so the runtime re-scans its discovery directories.## Repository operations`.ki.toml` declares the skills that govern a repository. `ki repo educate`, `ki repo audit`, and `ki repo conform` resolve only those declarations and their explicit dependencies from installed harnesses.Missing, incompatible, undeclared, or ambiguous skills fail before an audit or conform operation runs. The CLI executes native rubric catalogues; it never uses repository-vendored runners or `.ki/bin` wrappers.## Development boundaryAn installed verified payload is the authoritative source of capabilities. Local development is explicit: `ki dev local set <harness-id> <local-harness-path>` validates and records a checkout, `ki dev local on [harness-id]` selects it, and `ki dev local off [harness-id]` restores the verified archive. A selected local checkout is a mutable development source, not a verified installed payload; activation and loaded runtime capability remain separate host evidence.For command grammar, run `ki --help`. For repository coverage, use `ki-repo`.## Operating modes### Mode HELPExplain the first-time bootstrap, installed-harness, user-activation, repository-activation, and native repository-operation boundaries above. Route exact command and option questions to `ki --help`; route `.ki.toml` coverage questions to `ki-repo`.### Mode REFRESHThis mode refreshes guidance, not user or repository state.1. Read [the source list](references/sources.md) and re-check the delivered `tools-ki` command surface, the compatible-harness contract, and the repository declaration contract.2. Diff them against [the bootstrap standard](references/standards-bootstrap.md), this routing overview, and [the exemplars](references/exemplars.md).3. Update only this skill's guidance and source review record. Record behavioural history in git rather than adding a changelog.

Frequently asked questions