Claude Skills by kritird

Capture the durable knowledge produced in the current build session into the local Mnemex staging tier — cheap, fast, no lock, no graph mutation. Use this when a user finishes building or designing and wants to persist what was learned — domain facts AND the patterns/decisions from human review — or says "save this to the knowledge graph", "remember this for next time", "capture this", "stage this". Run it INCREMENTALLY at natural checkpoints too, not only at session end — after a sub-task la...

View or change a Mnemex Context Graph's behavior configuration (decay half-life, memory tiers, freshness horizon, usage boosts, budgets, death policy) with a guided explanation of each knob. Use this whenever the user wants to see the current config, understand what a setting does, tune how fast the graph forgets or goes stale, or change any value in mnemex.config.md — instead of hand-editing YAML. Runs in DISPLAY mode (explain the current settings) or MODIFY mode (validate, write, and safely...

INTERNAL maintenance pass over a Mnemex graph — compact usage stamps, recompute decay and structural strength, re-tier hot/warm/cold, tombstone stale nodes, chain over-budget indexes, and regenerate navigation. This is the BACK HALF of /mnemex:mnx-promote (run over the post-merge graph inside promote's single plan/lock/transaction), NOT a user-facing command. There is no /mnemex:mnx-consolidate slash command — do not invoke this standalone; run /mnemex:mnx-promote, which calls it. Strictly sn...

Validate and repair a Mnemex Context Graph knowledge graph. Use this whenever the user wants to check the integrity/health of the knowledge graph, fix drift, after a manual edit to nodes, or as a gate before committing graph changes — and it runs automatically at the end of every mnx-promote apply (including its folded consolidate). Checks all integrity invariants (edge targets exist, index matches the folder, denormalized copies are fresh, reverse-map consistent, no dangling edges, hot bound...

Bootstrap or update a Mnemex knowledge graph from an EXISTING code or documentation repository (a local folder or a git remote) — no live session required. Use this when the user wants to seed a graph from a repo, says "ingest this repo", "bootstrap the graph from <repo>", "import our docs/code into memory", "index this codebase into the graph", or wants to re-sync a previously ingested corpus. Walks the source, DISTILLS durable atoms (never transcribes), discovers a deduped entity catalog, w...

Set up Mnemex for the user — bind the current project (or the user account) to a knowledge-graph repo, or scaffold a brand-new graph. Use this when no Mnemex graph is configured yet (a read/write skill reported "No Mnemex graph configured"), when the user says "set up mnemex", "create a knowledge graph", "point mnemex at my repo", or wants to change which graph this project uses. Establishes the binding that every other Mnemex skill resolves.

Promote the locally-staged Mnemex captures into the shared knowledge graph — the deliberate, batched, attention-heavy half of memory (the `git push`/PR to capture's `git commit`). Use this when the user wants to merge captured knowledge into the graph, says "promote", "flush staging", "merge my captures", "publish to the knowledge graph", or when a nag reports staged atoms pending / consolidation overdue. Flushes usage stamps, reconciles + merges every staged atom (clean-context sub-agent, hu...

Retrieve knowledge from a Mnemex Context Graph knowledge graph. Invoke this PROACTIVELY at the start of any substantive task that touches a domain the graph may cover — before designing, implementing, debugging, or answering a domain/architecture question — not only when the user names mnemex. Trigger it whenever the user asks something that should draw on accumulated domain knowledge or team patterns, references "the knowledge graph", "what we know about", "our patterns for", or pivots mid-s...

Show an at-a-glance status of the user's Mnemex knowledge graph — what graph is bound, its kind (git-remote / git-local / plain-local), node and hot/warm/cold tier counts per space, pending (un-pushed) usage stamps, last gc per space, a structural health summary, and every OTHER graph Mnemex knows about. Use this when the user asks "what's in my graph", "is mnemex set up / healthy", "what's bound here", "mnemex status", "how big is my knowledge graph", "what graphs do I have", "what other gra...