Menu
Move notes between knowledge bases, updating all links and references
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Find near-duplicate notes and merge them safely. Use when the user asks to "dedupe the KB", "find duplicate notes", "merge these notes", or after large research sessions that may have re-covered existing ground.
Re-verify time-sensitive claims in KB notes against live sources and apply visible corrections. Use when the user asks to "refresh the KB", "re-verify notes", "check what's gone stale", or on a schedule. Distinct from /kb-review (structural quality) — this checks whether the facts are still true.
Synthesize a coherent narrative explanation of a topic from multiple KB notes. Use when the user asks to "explain X from the KB", wants a structured overview/briefing woven from existing notes, or asks "what's the full picture on X".
Answer a single question and save the answer as an atomic note in the knowledge base. Use when the user poses a discrete factual/conceptual question they want captured for later, says "look this up and save it", "add this to the KB", or "note down the answer to X".
Agentic research loop that deeply investigates a topic via web search and saves findings as atomic notes
Audit the knowledge base for quality issues (orphans, broken links, missing citations, stale notes, tag drift) and suggest improvements. Use when the user asks to "review the KB", "check note quality", "find orphans/broken links/duplicates", or "what needs cleanup".
| name | kb-move |
| description | Move notes between knowledge bases, updating all links and references |
| user_invocable | true |
| arguments | Note slug(s) to move, and target KB. E.g.: 'some-note-slug --to my-domain' or 'topic-* --to my-domain' |
Move one or more notes from one KB to another, updating all cross-references.
Parse arguments — Extract from $ARGUMENTS:
topic-*)Resolve notes — For each slug/pattern:
kbs.yamlmkdir -pShow migration plan — Present what will happen:
Moving 5 notes from general → my-domain:
1. note-slug-one
2. note-slug-two
3. note-slug-three
4. note-slug-four
5. note-slug-five
This will:
- Move files from kbs/general/ to kbs/my-domain/
- Update wikilinks in OTHER notes that reference these (add cross-KB prefix if needed)
- No reference path changes needed (both KBs are at same depth under kbs/)
Proceed? (yes / no / adjust)
Move files — For each note:
mv kbs/<source>/<slug>.md kbs/<target>/<slug>.md
Update cross-references — For each moved note:
a. Notes in the SOURCE KB that link to the moved note: their [[slug]] wikilinks still resolve (same-KB resolution fails, falls through to cross-KB), but for clarity, update them to [[target:slug]].
b. Notes in OTHER KBs that link to the moved note: update [[slug]] → [[target:slug]] if they were relying on cross-KB resolution to the old KB.
c. Notes in the TARGET KB that link to the moved note: their [[slug]] now resolves directly (same-KB). Remove any [[source:slug]] prefix if present.
d. The moved note itself: update any [[source:other-note]] prefixed links that pointed to the source KB — these can now be plain [[other-note]] if the target is in the same KB.
Reference paths — Since all KBs are at kbs/<name>/, the relative path to references/ is ../../references/ regardless. No changes needed.
Rebuild index — Run:
python3 .kb/kb-index.py build --kb <source>
python3 .kb/kb-index.py build --kb <target>
This also rebuilds the unified index.
Summary — Show:
related: frontmatter and body [[wikilinks]] — don't touch other content$ARGUMENTS