wiki_capture
ktx's knowledge base - wiki pages for durable, reusable business knowledge. Covers capture workflow for user preferences, metric definitions, organizational conventions, and cross-references between wiki pages and semantic-layer sources. Loaded by the post-turn memory-agent only. The research agent reads wiki via `wiki_read`/`wiki_search` but does not write it.
npx skills add Kaelio/ktx --skill wiki_capture --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Wiki Capture ## Role The knowledge base stores durable, reusable business knowledge for an analytics assistant. Each page is a self-contained rule, definition, or convention that answers "how should this concept be handled in this organization?" - written once and reused across chats. Scope selection is handled by the runtime: - When user-scoped knowledge is enabled AND the caller is a chat turn, writes go to the user's **personal** scope. - When the caller is an admin-driven ingest (`sourceType: 'external_ingest'`), writes go to the **global** scope. - When user-scoped knowledge is disabled, all writes go to the global scope. The `wiki_write` tool picks the right scope based on the session. Capture logic does not need to choose - focus on whether the content is worth capturing at all. ## What to capture Capture when the user or the ingested document expresses: - A metric definition ("revenue means booked revenue after refunds"). - A filter or convention that should always apply ("exclude test accounts when reporting ARR"). - A mapping or alias ("mood_stress_sleep = Oxytocin protocol"). - A domain rule that is not visible from column names alone ("status = 'T' means terminated, n
- Role
- What to capture
- Workflow
- Identifier Verification Protocol
- Keys, summaries, and content
- Tags, refs, slrefs
- Replace semantics
- Connection scoping
- Editing existing pages
- Overriding an organization rule
- Worked example - capturing a metric with cross-references
- Rules
What does the wiki_capture skill do?
ktx's knowledge base - wiki pages for durable, reusable business knowledge. Covers capture workflow for user preferences, metric definitions, organizational conventions, and cross-references between wiki pages and semantic-layer sources. Loaded by the post-turn memory-agent only. The research agent reads wiki via `wiki_read`/`wiki_search` but does not write it.
How do I install it?
Run `npx skills add Kaelio/ktx --skill wiki_capture --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Kaelio/ktx, a repository with 1,526 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.