Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nvk/wiki
LLM-compiled knowledge base manager for Codex. Use it to initialize, ingest, import source collections, collect catalogs, track inventory, index datasets, archive old topics, compile, query, lint, audit, research, plan, capture or rehydrate agent session context, and generate outputs from topic-scoped wikis. Activates when the user mentions wiki workflows, knowledge-base management, ingestion, collection ingestion, import wiki, collect, catalog, curate, find all, inventory, source queue, candida
Passed 20 of 20 test cases with the skill, and 12 of 20 without it.
and 5 more in the full report
8 fixed12 passed either way0 still failing0 broke3 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
I set up my wiki config at `~/.config/llm-wiki/config.json` pointing to `~/Library/Mobile Documents/com~apple~CloudDocs/wiki`. When accessing `topics/`, the system throws an 'Operation not permitted' error. Should I update the config file to point to `~/wiki` instead?
| Checked | Without skill | With skill |
|---|---|---|
| Advises granting system disk or iCloud permissions rather than changing the configured hub path. | Missed | Passed |
The instructions your model reads when the skill loads.
You manage an LLM-compiled knowledge base. Source documents are ingested into raw/, then incrementally compiled into a wiki of interconnected markdown articles. Codex is both the compiler and the query engine.
Codex plugins package skills, MCP servers, apps, and metadata. They do not register Claude-style custom /wiki:* commands. Treat any /wiki, /wiki:*, or command-flag examples in this skill and its references as shorthand for the same workflow expressed in natural language, or via explicit @wiki invocation.
Resolution: At the start of every operation, resolve HUB by reading ~/.config/llm-wiki/config.json first. Prefer hub_path: expand the leading ~ only (not tildes in com~apple~CloudDocs) on the current machine. Treat resolved_path as a legacy cache only: use it when no hub_path exists, or as a fallback if the expanded hub_path is unavailable and resolved_path is initialized. Do not write machine-specific resolved_path values into shared configs. If no config file exists, try ~/wiki/_index.md as a fallback. If stat/existence checks succeed but reading wikis.json or listing topics/ fails with Operation not permitted, the hub path is correct and macOS is blocking this process; tell the user to grant Full Disk Access or iCloud Drive access to the exact app launching the agent and restart. Do not switch to ~/wiki or resolved_path for that error. See references/hub-resolution.md for the full protocol.
The config file looks like:
{
"hub_path": "~/Library/Mobile Documents/com~apple~CloudDocs/wiki"
}
If no config exists and ~/wiki/ has _index.md, that works too. But config is checked first — in sandboxed environments ~/wiki/ may not be accessible. All references to ~/wiki/ below mean HUB.
Topic sub-wikis are the default. HUB is a hub — content lives in HUB/topics/<name>/. Each topic gets isolated indexes, sources, and articles. This keeps queries focused and prevents unrelated topics from polluting each other's search space.
For collection families that will grow across subjects, prefer kind-first topic
slugs such as memes-bitcoin, memes-ethereum, tools-bitcoin, or
examples-seedqr. Use subject-first slugs when the subject is the primary
research area and the collection is only one artifact within that topic.
Resolution order:
--local flag → .wiki/ in current project--wiki <name> flag → named wiki from HUB/wikis.json; resolve registry paths as <HUB>, ~, absolute, or relative to HUB, and fall back to HUB/topics/<name> if a registry path is stale.wiki/ → use itWhen a command targets the hub and the hub has no content, suggest creating a topic sub-wiki instead.
test cases passed, vs 12 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.