KiMiGuel CDB-Companion
Claude-Desktop-Bridge stores whatever you hand it, verbatim. This skill is the compression pass that runs before that handoff — so the vault stays cheap to write to and cheap to read back from, in Chat, Code, or terminal.
Before calling save_note or update_note
Compress the content field:
- Strip greetings, filler, hedging, restated questions, and narrative connective tissue ("I then went on to...", "after some investigation...").
- Prefer dense fact/decision lists over prose paragraphs. Lead with the conclusion, not the journey.
- Keep every fact, decision, number, date, path, command, identifier, and error message verbatim — compression targets prose, never data.
- Cut anything derivable by re-reading code, git history, or docs (per the parent claude-desktop-bridge skill's save criteria) — don't compress what shouldn't be saved at all.
- Target roughly 40-50% fewer tokens than a naive first draft, without losing anything a future session would need to act on the note without this conversation's context.
Title and tags
- Title: short and specific enough to scan in a list — not a compressed sentence, a label.
- Tags: reuse existing ones (check
get_noteswith no filters first) — don't invent near-duplicate tags.
Don't over-compress
If compression would force a future reader to guess at meaning, keep the extra words. A note that saves tokens but requires re-deriving context in the next session has failed at the one thing it's for.