holoctl-foreign-bootstraplisted
Install: claude install-skill FelipeCarillo/holoctl
# Bootstrap a non-Claude assistant from a holoctl workspace
This repo is managed by **holoctl**. The canonical source of truth lives in
`.holoctl/` — it is tool-neutral. holoctl's CLI (`hctl`, on PATH) compiles that
source into **Claude Code's** native files only (`CLAUDE.md`, `.claude/`).
If you are Claude Code, ignore this skill — your config is already in `.claude/`.
If you are **any other assistant**, you have no compiler maintained for you.
Instead, do the translation yourself: read `.holoctl/` and write the equivalent
into your own tool's native config location. Read **`.holoctl/`** as the source —
NOT `.claude/` (that one is already shaped for Claude).
## Step 1 — read the canonical source
Read these, in order, skipping any that don't exist:
1. `.holoctl/instructions.md` — the project's primary agent instructions (objective, architecture, conventions, merged).
2. `.holoctl/context/*.md` — `objective.md`, `architecture.md`, `conventions.md` and any `documents/`.
3. `.holoctl/agents/*.md` — active personas (each has `name` / `description` / `tools` / `paths` frontmatter).
4. `.holoctl/memory/MEMORY.md` — always-on durable memory index, plus `.holoctl/memory/topics/*.md` (each topic has a `scope:` of `always_on` / `lazy` / `glob`).
5. `.holoctl/commands/*.md` — reusable slash-command-style workflows.
## Step 2 — materialize into your native config dir
Write the content into the location **your** tool reads. Pick your row:
| Your tool | Where to wr