claude-mega-brain
OKF knowledge navigation. ALWAYS use this skill the moment a `<mega-brain>` block appears in session context — it means the…
Initialize OKF knowledge base files in the current project. Use when the user wants to start documenting their project for claude-mega-brain, or when the user says "init mega brain", "setup the knowledge base", "cria o okf", "inicializa o mega brain", "quero usar o mega brain",
$ npx -y skills add guhcostan/claude-mega-brain --skill init --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/initContext preview
The summary Claude sees to decide when to auto-load this skill.
Initialize OKF knowledge base files in the current project. Use when the user wants to start documenting their project for claude-mega-brain, or when the user says "init mega brain", "setup the knowledge base", "cria o okf", "inicializa o mega brain", "quero usar o mega brain",
name: init description: Initialize OKF knowledge base files in the current project. Use when the user wants to start documenting their project for claude-mega-brain, or when the user says "init mega brain", "setup the knowledge base", "cria o okf", "inicializa o mega brain", "quero usar o mega brain", "criar a estrutura do knowledge base", or asks how to get started with the plugin.
Creates a minimal set of OKF files so claude-mega-brain can start injecting context at the next session. No dedicated folder required — files can live anywhere in the project.
Two files are enough to get started:
**`index.md`** — the knowledge map (put it at the project root or in `docs/`):
--- type: Index title: <Project Name> Knowledge Base description: Central reference for all project knowledge. timestamp: <today ISO 8601> --- # <Project Name> ## Tables / Data <!-- [orders](docs/orders.md) — one-liner --> ## Metrics <!-- [wau](docs/wau.md) — one-liner --> ## APIs <!-- [auth](docs/auth.md) — one-liner --> ## Services <!-- [payments](docs/payments.md) — one-liner -->
**`log.md`** — append-only changelog (same location as index.md):
--- type: Log --- <today ISO date> — initialized OKF knowledge base
1. Check if OKF files already exist — look for any `.md` with `type:` frontmatter, or an existing `index.md` / `log.md`. If found, tell the user and stop. 2. Detect project type (`package.json`, `pyproject.toml`, `go.mod`, etc.) to personalize the index template. 3. Ask the user where they want the files — suggest project root or `docs/` as default. If `.mega-brain.json` has a `dir` field, use that subdirectory instead. 4. Write `index.md` and `log.md` in the chosen location. 5. Tell the user:
Loads the knowledge. Skips the search. 100% accuracy · 0 tool calls · −66% tokens vs Obsidian+MCP Real agentic sessions. Benchmark →
OKF knowledge navigation. ALWAYS use this skill the moment a `<mega-brain>` block appears in session context — it means the…
Create or update a single OKF concept file from raw input. Use when the user wants to document a specific table, metric, API,…
Scan the project and migrate existing documentation into OKF format. Use when the user wants to populate the knowledge base from…