Skip to content
Back to search

karpathy-wiki

Karpathy Wiki - Claude Code skills for building persistent, compounding knowledge bases. Based on Andrej Karpathy's LLM Wiki pattern.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/toolboxmd--karpathy-wiki/badge.svg)](/listings/toolboxmd--karpathy-wiki)

HTML

<a href="/listings/toolboxmd--karpathy-wiki"><img src="/api/listings/toolboxmd--karpathy-wiki/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Add the ToolboxMD marketplace, then install this plugin:

codex plugin marketplace add toolboxmd/marketplace
codex plugin add karpathy-wiki@toolboxmd

Then start a new Codex session. Review and trust the plugin's `SessionStart` and `Stop` hooks through `/hooks`. The installed SessionStart hook tells the agent the exact plugin-owned CLI path, so no global `wiki` symlink or separate skill copy is required.

To update a GitHub installation:

1. Run the plugin lifecycle commands in your shell:

codex plugin marketplace upgrade toolboxmd
codex plugin remove karpathy-wiki@toolboxmd
codex plugin add karpathy-wiki@toolboxmd

The catalog lives in `toolboxmd/marketplace`. This repository is the plugin.

2. Start a new Codex session, review the new hook hash through `/hooks`, then ask Codex to run `wiki scheduler install` with the new plugin-owned Runtime CLI path. This refreshes the one machine scheduler.

The reinstall step is required when scheduling is enabled because the LaunchAgent stores the absolute path to the installed plugin snapshot. v0.3.1 stores that path in one machine scheduler instead of one plist per wiki.

Start a new session after each install or update. If a hook definition changed, review and trust its new hash through `/hooks`.

For development from sibling checkouts, generate local indexes from the marketplace catalog (see `toolboxmd/marketplace`) and add that sibling root as marketplace toolboxmd. Do not add this plugin repo as the marketplace.

Codex installs a snapshot from the marketplace. During local development, refresh it by removing and adding the snapshot in your shell:

codex plugin remove karpathy-wiki@toolboxmd
codex plugin add karpathy-wiki@toolboxmd

Open a new session and ask Codex to run `wiki scheduler install` through the new plugin-owned Runtime CLI. Scheduled wikis keep their per-wiki activation mode across the plugin refresh.

Do not install duplicate copies of these skills under `~/.agents/skills` or `~/.codex/skills`.

Where the plugin and wiki data live

- Codex installs the plugin code into its managed plugin cache. The bundled `bin/wiki` is the executable, not a wiki-data directory. - `~/.wiki-pointer` stores the selected main-wiki path. `~/wiki/` is the default, not a required location. - `${XDG_CONFIG_HOME:-~/.config}/karpathy-wiki/wikis/<wiki-hash>/runtime.toml` stores the local trust record and provider settings. It is never read from a project checkout. - `${XDG_CONFIG_HOME:-~/.config}/karpathy-wiki/workspaces/<workspace-hash>/runtime.toml` stores the one authoritative `project|main|both` selection and exact pinned targets. `wiki use` writes it atomically without editing tracked markers. - Project-specific data lives in `<project>/wiki/` after project mode is configured. - Removing or updating the plugin does not remove `~/.wiki-pointer`, a main wiki, or any project wiki.

Uninstall from Codex

If scheduled activation is enabled, first ask Codex to run `wiki scheduler uninstall --force` while the plugin is still installed, or run `wiki scheduler disable <wiki-path>` for each scheduled wiki and then `wiki scheduler uninstall`. Then remove the plugin:

codex plugin remove karpathy-wiki@toolboxmd

Optionally remove the configured marketplace as well:

codex plugin marketplace remove toolboxmd

These commands remove the Codex plugin bundle and optional marketplace source. They intentionally preserve all wiki data and `~/.wiki-pointer`.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/plugin.json · Manifest · 9 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "karpathy-wiki",
  3. "version": "0.7.3",
  4. "description": "Auto-maintained LLM wiki based on Andrej Karpathy's pattern.",
  5. "author": {
  6. "name": "lukaszmaj"
  7. },
  8. "repository": "https://github.com/toolboxmd/karpathy-wiki"
  9. }
README.md · README · 410 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Karpathy Wiki
  2. > **Retired.** karpathy-wiki is no longer maintained.
  3. > [ContextMD](https://github.com/toolboxmd/contextmd) now captures and serves
  4. > what agents learn. The plugin is no longer offered in the toolboxmd
  5. > marketplace. Existing wikis are plain git-versioned markdown and stay readable
  6. > without the plugin.
  7. A provider-aware plugin for auto-maintained LLM wikis — based on [Andrej Karpathy's LLM Wiki pattern](https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f).
  8. Instead of re-deriving answers from raw documents every time (RAG), the LLM incrementally builds and maintains a wiki — a structured, interlinked collection of markdown files. The wiki compounds with every source you add and every question you ask.
  9. For day-to-day usage and the workflow walkthrough, see [MANUAL.md](MANUAL.md).
  10. ## What it does
  11. As you work with Codex or Claude Code, durable knowledge such as research findings, resolved confusions, validated patterns, gotchas, and architectural decisions gets written as a small capture file and processed by a detached background worker into a persistent wiki. The wiki is git-versioned. Your flow is never interrupted.
  12. Agent-facing CLI commands are listed below. In normal plugin use, ask Codex in
  13. natural language and the SessionStart hook supplies the installed CLI path. From
  14. a source checkout, operators can invoke the same commands as `./bin/wiki ...`.
  15. No global `wiki` command is required.
  16. - `wiki status` — content and ingest-runtime health report: queue depth, active slots, profiles, cooldowns, heartbeat stalls, scheduler state, failed/deferred captures, quality, drift, issues, and selective-promotion decisions.
  17. - `wiki capture` — write a chat-driven capture (the agent's canonical entry point; supports `--kind chat-only|chat-attached`, body via stdin or `--body-file`).
  18. - `wiki ingest-now` — drift-scan + drain `inbox/` on demand.
  19. - `wiki issues` — show recent ingester-reported issues, grouped and severity-ordered.
  20. - `wiki use project|main|both` — change per-cwd wiki mode.
  21. - `wiki config init-local|migrate|migrate-local|validate|show` — manage trusted, per-machine provider and dispatcher settings outside the checkout.
  22. - `wiki scheduler install|uninstall|enable|disable|status|tick-all` — manage the one machine-wide macOS LaunchAgent adapter and per-wiki activation.
  23. - `wiki tick` — run one short, bounded dispatcher pass (also usable from an external scheduler).
  24. - `wiki init-main` — bootstrap `~/.wiki-pointer` (interactive).
  25. - `wiki doctor` — detached census: tests, schema/tags/frontmatter/related, rewrite jobs. Does not rewrite page bodies.
  26. The plugin handles both a main knowledge base and per-project wikis via the
  27. `wiki-resolve.sh` resolver. The default main-wiki location is `~/wiki/`, but
  28. the actual path is selected by `wiki init-main` and stored in
  29. `~/.wiki-pointer`. A project wiki lives at `<project>/wiki/`. Each machine
  30. chooses one automatic activation mode: SessionStart, or a local scheduler.
  31. Drop a file into a wiki's `inbox/` and the next scan ingests it directly. No
  32. fabricated wrapper capture is required.
  33. `wiki use both` is project-first. Every original capture enters only the
  34. project wiki. After local ingest, the project worker keeps repository-specific
  35. knowledge local or publishes one generalized, provenance-linked capture to the
  36. main wiki through an atomic idempotent helper. It never copies the original
  37. capture verbatim into both queues.
  38. ## Install in Codex
  39. Add the ToolboxMD marketplace, then install this plugin:
  40. ```bash
  41. codex plugin marketplace add toolboxmd/marketplace
  42. codex plugin add karpathy-wiki@toolboxmd
  43. ```
  44. Then start a new Codex session. Review and trust the plugin's `SessionStart`
  45. and `Stop` hooks through `/hooks`. The installed SessionStart hook tells the
  46. agent the exact plugin-owned CLI path, so no global `wiki` symlink or separate
  47. skill copy is required.
  48. To update a GitHub installation:
  49. 1. Run the plugin lifecycle commands in your shell:
  50. ```bash
  51. codex plugin marketplace upgrade toolboxmd
  52. codex plugin remove karpathy-wiki@toolboxmd
  53. codex plugin add karpathy-wiki@toolboxmd
  54. ```
  55. The catalog lives in `toolboxmd/marketplace`. This repository is the plugin.
  56. 2. Start a new Codex session, review the new hook hash through `/hooks`, then
  57. ask Codex to run `wiki scheduler install` with the new plugin-owned Runtime
  58. CLI path. This refreshes the one machine scheduler.
  59. The reinstall step is required when scheduling is enabled because the
  60. LaunchAgent stores the absolute path to the installed plugin snapshot. v0.3.1
  61. stores that path in one machine scheduler instead of one plist per wiki.
  62. Start a new session after each install or update. If a hook definition changed,
  63. review and trust its new hash through `/hooks`.
  64. For development from sibling checkouts, generate local indexes from the
  65. marketplace catalog (see `toolboxmd/marketplace`) and add that sibling root as
  66. marketplace toolboxmd. Do not add this plugin repo as the marketplace.
  67. Codex installs a snapshot from the marketplace. During local development,
  68. refresh it by removing and adding the snapshot in your shell:
  69. ```bash
  70. codex plugin remove karpathy-wiki@toolboxmd
  71. codex plugin add karpathy-wiki@toolboxmd
  72. ```
  73. Open a new session and ask Codex to run
  74. `wiki scheduler install` through the new plugin-owned Runtime CLI. Scheduled
  75. wikis keep their per-wiki activation mode across the plugin refresh.
  76. Do not install duplicate copies of these skills under `~/.agents/skills` or
  77. `~/.codex/skills`.
  78. ### Where the plugin and wiki data live
  79. - Codex installs the plugin code into its managed plugin cache. The bundled
  80. `bin/wiki` is the executable, not a wiki-data directory.
  81. - `~/.wiki-pointer` stores the selected main-wiki path. `~/wiki/` is the
  82. default, not a required location.
  83. - `${XDG_CONFIG_HOME:-~/.config}/karpathy-wiki/wikis/<wiki-hash>/runtime.toml`
  84. stores the local trust record and provider settings. It is never read from a
  85. project checkout.
  86. - `${XDG_CONFIG_HOME:-~/.config}/karpathy-wiki/workspaces/<workspace-hash>/runtime.toml`
  87. stores the one authoritative `project|main|both` selection and exact pinned
  88. targets. `wiki use` writes it atomically without editing tracked markers.
  89. - Project-specific data lives in `<project>/wiki/` after project mode is
  90. configured.
  91. - Removing or updating the plugin does not remove `~/.wiki-pointer`, a main
  92. wiki, or any project wiki.
  93. ### Uninstall from Codex
  94. If scheduled activation is enabled, first ask Codex to run
  95. `wiki scheduler uninstall --force` while the plugin is still installed, or run
  96. `wiki scheduler disable <wiki-path>` for each scheduled wiki and then
  97. `wiki scheduler uninstall`. Then remove the plugin:
  98. ```bash
  99. codex plugin remove karpathy-wiki@toolboxmd
  100. ```
  101. Optionally remove the configured marketplace as well:
  102. ```bash
  103. codex plugin marketplace remove toolboxmd
  104. ```
  105. These commands remove the Codex plugin bundle and optional marketplace source.
  106. They intentionally preserve all wiki data and `~/.wiki-pointer`.
  107. ## Claude Code compatibility
  108. Add marketplace toolboxmd, then enable `karpathy-wiki@toolboxmd`. If you
  109. already enabled `karpathy-wiki@karpathy-wiki-local`, rename that key to
  110. `karpathy-wiki@toolboxmd` and point `extraKnownMarketplaces.toolboxmd` at
  111. `toolboxmd/marketplace` (GitHub or the generated local sibling root).
  112. ```json
  113. {
  114. "extraKnownMarketplaces": {
  115. "toolboxmd": {
  116. "source": {
  117. "source": "github",
  118. "repo": "toolboxmd/marketplace"
  119. }
  120. }
  121. },
  122. "enabledPlugins": {
  123. "karpathy-wiki@toolboxmd": true
  124. }
  125. }
  126. ```
  127. Then run `/reload-plugins`. Hooks, commands, and skills are discovered from
  128. the plugin manifest. No global CLI symlink or manual hook wiring is required.
  129. ## Grok Build
  130. ```bash
  131. grok plugin marketplace add toolboxmd/marketplace
  132. grok plugin install karpathy-wiki --trust
  133. ```
  134. Start a new session or reload plugins. Grok copies the plugin on install;
  135. `grok plugin update karpathy-wiki` refreshes it after a release. Do not
  136. path-install this checkout. Uninstalling the plugin preserves wiki data and
  137. `~/.wiki-pointer`.
  138. ## How it works
  139. The skill is split into four focused parts, each loaded only when its moment arrives:
  140. - `skills/using-karpathy-wiki/SKILL.md` — loader, auto-injected into every session by the SessionStart hook (via `hookSpecificOutput.additionalContext` for Claude Code; `additional_context` for Cursor; `additionalContext` for Copilot CLI / SDK-standard). Defines iron laws, triggers, and points at the other three.
  141. - `skills/karpathy-wiki-capture/SKILL.md` — main agent, on-demand. Capture-authoring protocol: format, body floor, `bin/wiki capture` invocation.
  142. - `skills/karpathy-wiki-read/SKILL.md` — main agent, on-demand. Deterministic 6-step orientation ladder for finding wiki coverage of a user question (orient → count candidates → inline-read OR Explore subagent OR web search → cite). Loaded for any user question, per Iron Rule 4.
  143. - `skills/karpathy-wiki-ingest/SKILL.md` — detached runtime ingester only. Provider-neutral deep orientation, page format, validator contract, manifest protocol, and deterministic completion contract.
  144. One hook lives at repo level:
  145. - `hooks/session-start` — applies the subagent/ingester guard, injects the loader, resolves the wiki, and starts exactly one short dispatcher tick only when that wiki's local mode is `session_start`. In `scheduled` mode it is loader-only.
  146. Captures land as tiny markdown files in `<wiki>/.wiki-pending/`. Two flows feed it:
  147. - **Chat-driven capture.** The main agent calls `bin/wiki capture` with a body that encodes durable knowledge from the conversation. The resolver chooses the right wiki for the cwd (project vs main), and the file is written into that wiki's `.wiki-pending/`.
  148. - **Raw-direct ingest.** A file dropped into `<wiki>/inbox/` is picked up by the next configured scan (SessionStart, LaunchAgent, or `wiki ingest-now`), which writes a `capture_kind: raw-direct` capture pointing at the file's absolute path. The ingester reads the file directly — no fabricated wrapper.
  149. A successful `wiki capture` call completes the foreground handoff. The main
  150. agent does not wait for `.wiki-pending/` to drain; the scheduler owns queue
  151. claiming, leases, retries, cooldowns, and failed-work handling.
  152. For Grok image ingestion, a JPEG or PNG named by the capture is sent in the
  153. same provider request as the normal ingester instructions using native ACP
  154. image content blocks. The adapter detects MIME type from the file signature,
  155. not the extension, and records only byte count, MIME type, and SHA-256 in
  156. invocation metadata. It never records image bytes or base64. A primary image is
  157. followed by any repeatable `--attachment-path` values in capture order. The
  158. adapter does not scan the wiki for images, and a declared image that is missing,
  159. unsupported, unreadable, outside the primary evidence directory, or too large
  160. for the process argument limit fails before Grok starts. There is no path-only
  161. or `read_file` visual fallback. The ingester still retains every original under
  162. the normal raw-evidence and manifest protocol.
  163. Either way, one dispatcher atomically claims captures and enforces the configured per-wiki and per-profile ceilings. It can invoke Claude Code, Codex, or Grok with the exact configured model and reasoning effort. A heartbeat keeps live `.processing` work identifiable; technical failures retry up to `max_attempts`, rate limits wait without consuming attempts, and exhausted work moves to `.wiki-pending/failed/`. Semantic ingest is not reviewed by a second model on every run; quality is selected and measured through benchmarks.
  164. ### Detached-ingester trust boundary
  165. Detached provider workers are trusted local automation in v0.3.0, not a
  166. security boundary for hostile input. In particular, the Grok adapter uses
  167. `--always-approve` so a headless ingest can complete without an interactive
  168. permission prompt, and the dispatcher currently passes the launcher's full
  169. environment to the provider process. A prompt-injected capture can therefore
  170. request commands or reads available to that user account.
  171. Only ingest captures and source files you trust. Do not enable unattended
  172. ingest for collaborator-controlled repositories, downloaded prompt bundles, or
  173. other untrusted content. A project-local Grok sandbox profile can follow the
  174. current working directory and therefore works for either a project wiki or the
  175. main wiki, but that is not a complete one-file fix: Grok must retain access to
  176. its authentication state, the current semantic ingest protocol uses general
  177. shell commands, and Grok's child-process network restriction is not enforced on
  178. macOS. Provider-neutral least-privilege isolation is tracked in
  179. [`ISSUES.md`](ISSUES.md).
  180. ## Per-machine ingest configuration
  181. Tracked `.wiki-config` contains only wiki identity. Provider/model choices,
  182. concurrency, activation mode, routing, auto-commit, and the explicit local trust
  183. record live outside the checkout under the user's config home. A checkout cannot
  184. enable its own provider execution by committing configuration files.
  185. For a new general mixed-media wiki, the recommended Grok profile is Grok 4.6
  186. Medium. No fallback profile is created unless the operator supplies one:
  187. ```bash
  188. wiki config init-local <wiki> \
  189. --trust-workspace <canonical-project-or-wiki-root> \
  190. --default-provider grok --default-model grok-4.6 --default-effort medium \
  191. --max-processes 10 --dispatch-mode session_start
  192. wiki config validate <wiki>
  193. wiki config show <wiki>
  194. ```
  195. Supported provider adapters in this release are `grok`, `claude`, and `codex`;
  196. arbitrary explicit model IDs remain supported. As a convenience,
  197. `--default-provider grok` without model or effort selects the built-in
  198. `grok-4.6` Medium recommendation and keeps the stable `grok_medium` profile
  199. name. An explicit `--default-model grok-4.5 --default-effort medium` pin remains
  200. valid for historical reproduction and intentional text-only comparison.
  201. `executable` is one executable name or absolute path, never an arbitrary shell
  202. command. An executable that resolves inside the trusted project checkout is
  203. rejected, including through a symlink or `PATH`.
  204. Existing runtime files are user-owned and are never rewritten merely because
  205. the plugin is installed, updated, or started. To opt one existing profile into
  206. the new recommendation, run the explicit update command:
  207. ```bash
  208. wiki config update-runtime <wiki> \
  209. --profile grok_medium --model grok-4.6 --reasoning-effort medium
  210. ```
  211. The update changes only the named profile fields and preserves routing,
  212. activation, fallback, trust, and every other profile. Inspect the result with
  213. `wiki config show <wiki>` before draining queued work.
  214. The recommendation is workload-specific. The
  215. [2026-08-20 matched text-ingest benchmark](docs/benchmarks/2026-08-20-grok-4.5-vs-4.6-medium.md)
  216. scored Grok 4.5 Medium at 95/100 and Grok 4.6 Medium at 94/100, which correctly
  217. favored 4.5 for that text-oriented workload. The
  218. [2026-08-21 multimodal benchmark](docs/benchmarks/2026-08-21-grok-4.6-native-acp-image-qualification.md)
  219. later found that only Grok 4.6 Medium with native ACP images qualified among
  220. the three tested image configurations. Grok 4.6 through `read_file` produced
  221. one severe hallucination, and Grok 4.5 through `read_file` produced fourteen.
  222. Grok 4.5 with native image input was not tested, so the newer benchmark does
  223. not establish universal model superiority or isolate every model and transport
  224. interaction.
  225. For a chat-attached bundle, record image membership explicitly. The primary
  226. evidence file establishes the allowed directory; additional image paths must
  227. resolve below it and are delivered in the order shown:
  228. ```bash
  229. wiki capture --title "Evidence bundle" --kind chat-attached \
  230. --suggested-action create --evidence-path /absolute/bundle/notes.md \
  231. --attachment-path /absolute/bundle/page-1.jpg \
  232. --attachment-path /absolute/bundle/page-2.png < capture-body.md
  233. ```
  234. For an older tracked operational config, inspect the split before applying it:
  235. ```bash
  236. wiki config migrate <wiki> \
  237. --trust-workspace <canonical-project-or-wiki-root> --dry-run
  238. wiki config migrate <wiki> \
  239. --trust-workspace <canonical-project-or-wiki-root> \
  240. [explicit provider/model/effort options if needed]
  241. ```
  242. This only migrates configuration layout. It does not move or rewrite wiki content.
  243. If a previous plugin snapshot already created an ignored
  244. `<wiki>/.wiki-config.local`, import it into the external trust store explicitly:
  245. ```bash
  246. wiki config migrate-local <wiki> \
  247. --trust-workspace <canonical-project-or-wiki-root> --dry-run
  248. wiki config migrate-local <wiki> \
  249. --trust-workspace <canonical-project-or-wiki-root>
  250. ```
  251. The importer refuses a Git-tracked source. After a successful import, the old
  252. checkout file remains as an inactive copy so the operator can inspect and remove
  253. it deliberately.
  254. ## Activation modes
  255. - `session_start`: no scheduler installation. SessionStart injects the loader and launches one bounded scan/tick.
  256. - `scheduled`: `wiki scheduler install` installs one short-lived machine LaunchAgent. `wiki scheduler enable <wiki>` switches that trusted wiki to scheduled activation. `wiki scheduler disable <wiki>` switches it back to SessionStart. For compatibility, `wiki scheduler install <wiki>` installs the global scheduler and enables that wiki, while `wiki scheduler uninstall <wiki>` disables only that wiki and leaves the global scheduler installed.
  257. The scheduled command does not keep a model resident in memory. The coordinator wakes, enumerates trusted `wikis/*/runtime.toml` records, offers at most one worker per due wiki, enforces 10 machine-wide workers and one worker per wiki, then exits. On non-macOS systems, use `wiki scheduler tick-all` from an external scheduler. CodexBar is optional: when usable it provides advisory preflight quota data; when absent, malformed, or timed out, the dispatcher continues in reactive mode using provider CLI results.
  258. Design doc: [`docs/planning/karpathy-wiki-v2-design.md`](docs/planning/karpathy-wiki-v2-design.md). Implementation plan: [`docs/planning/2026-04-22-karpathy-wiki-v2.md`](docs/planning/2026-04-22-karpathy-wiki-v2.md).
  259. ## Status
  260. **v0.3.2.** Codex is the qualified
  261. primary interactive development host. Claude Code remains supported with its
  262. existing automated hook coverage. Codex qualification includes recorded
  263. interactive-host acceptance evidence; it does not claim equivalent automated
  264. coverage for every Codex lifecycle path. Detached ingest supports Claude Code,
  265. Codex, and Grok. Cursor, Copilot CLI, OpenCode, and Gemini loader paths remain
  266. best-effort.
  267. **What works today (v2.4 + 0.2.7 read protocol + 0.2.8 hardening + 0.3.1 scheduler and provider automation + 0.3.2 native Grok image ingestion):**
  268. - Auto-capture + detached background ingest into a git-versioned wiki.
  269. - Discovery-driven categories: any top-level `mkdir <name>/` at the wiki root creates a category. No code changes required.
  270. - Per-directory `_index.md` tree (recursive); root `index.md` is a small MOC.
  271. - Validator enforces `type: <plural-category>` matching `path.parts[0]` and rejects pages at depth ≥5.
  272. - **Read-from-wiki protocol** (restored in 0.2.7 after v2.4 split silently dropped it). Iron Rule 4 forbids answering any user question without orientation; new `karpathy-wiki-read` skill defines a deterministic 6-step ladder (orient → candidate count → inline-read for ≤5 candidates / Explore subagent for 6+ / web search + capture-the-gap for cold results) with a hard cite contract on every wiki-grounded answer.
  273. - Four-skill split with auto-loaded `using-karpathy-wiki` loader. Multi-platform SessionStart hook output: `hookSpecificOutput.additionalContext` for Claude Code, `additional_context` for Cursor, `additionalContext` for Copilot CLI / SDK-standard. Subagents and detached ingesters get only the surface they need.
  274. - Single-authority workspace resolution at capture time via `wiki-resolve.sh`. `wiki use project|main|both` writes one private selection; `wiki init-main` establishes the main-wiki pointer used when selecting `main` or `both`.
  275. - Raw-direct ingest: drop a file into `<wiki>/inbox/` and the next configured scan ingests it directly (no fabricated wrapper). Files accidentally dropped in `raw/` are recovered to `inbox/` under the manifest lock.
  276. - Deep orientation (steps 1-9) in the ingester; issues surfaced to `.ingest-issues.jsonl` and the `wiki issues` / `wiki status` commands.
  277. - Per-wiki `.ingest-runs.jsonl` for run history; status reports selective captures awaiting a decision, kept local, or promoted.
  278. - Bounded provider-aware dispatcher, optional fallback profile, heartbeat, retries, failed queue, optional CodexBar preflight, one global scheduled coordinator, and mutually exclusive SessionStart/scheduled activation per wiki.
  279. - Native Grok ACP image delivery for explicitly declared JPEG and PNG evidence, with fail-closed preflight and no `read_file` visual fallback.
  280. - `wiki status` health report; `wiki capture` / `wiki ingest-now` / `wiki issues` / `wiki use` / `wiki config` / `wiki scheduler` / `wiki tick` / `wiki init-main` CLI.
  281. - Tier-1 lint at every ingest: required frontmatter fields, link resolution, source existence, quality block ranges, type/path consistency.
  282. **What's deferred (see `TODO.md`, `ISSUES.md`, and `IDEAS.md`):**
  283. - Provider-neutral least-privilege isolation for detached ingesters: a minimal
  284. environment, deterministic privileged helpers, per-run path policy, isolated
  285. provider authentication, and macOS-specific containment tests.
  286. - `bin/wiki orient` CLI shortcut for the read protocol's Step A (deferred — observe whether prose-only fix produces reliable behavior first).
  287. - `allowed-tools` scoping on the four skills (deferred — orthogonal to read-protocol restoration).
  288. - Doctor quality re-rate and playbook rewriter (census ships; body compact is later).
  289. - `.ingest.log` → `.ingest.jsonl` migration (dual-artifact pattern, scheduled for v2.5).
  290. - Test coverage for non-Claude-Code platforms other than the qualified Codex
  291. plugin host (Cursor / Copilot CLI / OpenCode / Gemini).
  292. The shipped surface is enough for daily personal use; rough edges remain. PRs welcome once the repo opens for external contributions.
  293. ## Tests
  294. ```bash
  295. # Fast inner loop for the affected contract surface
  296. bash tests/run-all.sh skill
  297. bash tests/run-all.sh capture
  298. bash tests/run-all.sh dispatcher
  299. # Inspect a selection without executing it
  300. bash tests/run-all.sh --list provider
  301. # Deterministic final gate
  302. bash tests/run-all.sh
  303. bash tests/self-review.sh
  304. ```
  305. Focused groups are `skill`, `capture`, `scanner`, `dispatcher`, `provider`,
  306. `config`, `scheduler`, and `schema`. Tests that span multiple subsystems or
  307. cover low-frequency operator flows are assigned to `full-only` and still run
  308. from the default `full` gate. Use the smallest group that owns the changed
  309. contract during development, then run the full gate once at the integration
  310. boundary.
  311. Real provider and interactive-host acceptance evidence is retained under
  312. `tests/acceptance/` and is not part of the default deterministic loop.
  313. ## Credits
  314. Based on Andrej Karpathy's [LLM Wiki](https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f) concept and [original tweet](https://x.com/karpathy/status/2039805659525644595).
  315. The v2 SKILL.md is written in the style of, and uses techniques from, [obra/superpowers-skills](https://github.com/obra/superpowers-skills) (the `writing-skills`, `test-driven-development`, and `subagent-driven-development` skills in particular).
  316. Built by [toolbox.md](https://toolbox.md).
  317. ## License
  318. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.