obsidian-memory-wiki

Obsidian Memory Wiki

Canonical Package

obsidian-memory-wiki is the canonical parent skill for three formerly separate phases:

• obsidian → low-level vault/file operations.
• prepforreset → context-reset and end-of-session handoff capture.
• wikijanitor → scheduled or manual memory-wiki reconciliation.

The old skill names may still exist as compatibility slash-command aliases so /prepforreset, /wikijanitor, and /obsidian keep working. New automation, cron wrappers, and shared-skill installs should load/install this parent package:

--skills obsidian-memory-wiki

Do not schedule new runs with --skills wikijanitor,obsidian or --skills prepforreset,obsidian; those names are compatibility aliases and may be absent on newer profiles.

When to Use

Use this skill when:

• Reading, searching, creating, or editing notes in an Obsidian vault.
• The user says “prep for reset”, “prepare for a context window”, or invokes /prepforreset.
• A scheduled or manual wiki janitor should review recent sessions and memory-wiki notes.
• Installing or packaging this workflow for another compatible agent runtime.

Do not use it for:

• Dumping raw transcripts without distillation.
• Storing secrets or credential values in notes.
• Mutating non-wiki memory stores, project repositories, manifests, or backlogs unless the user separately asks for that mutation.
• Writing outside the resolved vault root.

Required Setup and Safety

1. Resolve the vault path before file operations.
   • Preferred in Hermes: injected skill config obsidian_memory_wiki.vault_path from the active profile config.yaml.
   • Compatibility fallback for other runtimes: OBSIDIAN_VAULT_PATH from the active process environment.
   • If neither source provides a concrete path, stop and request configuration; never guess a vault from an ambient directory.
2. Resolve the final absolute path and refuse writes whose resolved path is outside the vault root.
3. Prefer file tools for note operations: read_file, search_files, write_file, and patch.
4. Use terminal only for environment/profile checks, path resolution, or verification that genuinely needs a shell.
5. Keep durable knowledge separate from stale task progress. If it will be stale next week, put it in a handoff/session note, not a permanent concept note.
6. Never print or store raw secrets. Reference only secret locations such as .env, keychain, vault item, or config path.