name	obsidianify
description	Use when setting up, refreshing, debugging, or explaining Obsidianify for Codex or Claude sessions. Reads Obsidian vaults, ranks graph memory by project proximity, creates session context packets, and records valuable completed turn outcomes into typed Obsidian session notes.

Obsidianify

Current version: 0.4.11

Authoritative update source: https://github.com/aesopscott/obsidianify

Use this skill when a user wants to inject Obsidian-derived memory into a Codex or Claude project session, or record agent turn outcomes back into an Obsidian vault.

Workflow

Prefer global install unless the user needs a project-local override.
Run python scripts/install_global.py --vault <vault> --agent codex --agent claude from the plugin repo for global install.
For project-local install, run python scripts/install.py --target <project> --project <name> --agent codex --agent claude. If --vault or --write-root is omitted, the installer prompts for local paths, stores them in ~/.obsidianify/config.json, and writes agent-visible reminders to <project>/.obsidian-memory/sidecar_memory.json.
Start a new agent session in the target project.
Ask what Obsidian graph memory was injected.
If memory is missing, inspect <target>/.obsidian-memory/STATUS.json.

Reliability

SessionStart hooks refresh the packet.
UserPromptSubmit hooks record lightweight turn markers.
Stop hooks classify the latest prompt plus completed turn outcome and write valuable entries into typed notes under <vault>/<project>/sessionYYYY-MM-DD/.
Turn notes include distilled prompt memory and assistant outcome summaries; raw full prompts stay in the local marker store unless the user explicitly asks for transcript capture.
Pure Git bookkeeping prompts/outcomes, such as commit, push, status, branch, and origin/main updates, are skipped as noise unless the turn also contains durable implementation, architecture, configuration, or design details.
Any response containing direct Git command text, such as git add, git commit, or git push, is skipped even when it also mentions implementation details or files like config.json.
Obsidianify release/update bookkeeping, such as refreshing desktop/CLI environments, hook version updates, and origin/main status, is skipped as noise unless it includes real code-change details.
A project config can set vaultPath to choose the recording vault for that project: projects.<name>.vaultPath.
A project config can set writeRoot to write turn notes under a project-specific root instead: projects.<name>.writeRoot/sessionYYYY-MM-DD/.
Installer-managed sidecar entries for vaultPath and writeRoot are synced back into ~/.obsidianify/config.json during refresh-global and turn recording.
On Windows, Codex hooks use PowerShell call syntax and Claude hooks use a bash-safe powershell.exe -Command wrapper. Claude templates must use whole-command placeholders so they cannot emit raw quoted Python commands.
AGENTS.md or CLAUDE.md tells the agent to read the packet.
The first user prompt can force verification.

Do not claim the model remembered Obsidian by itself. The injected context comes from the generated packet.

Obsidianify

Current version: 0.4.11

Use this skill when a user wants to inject Obsidian-derived memory into a Codex or Claude project session, or record agent turn outcomes back into an Obsidian vault.

Workflow

Prefer global install unless the user needs a project-local override.

Run python scripts/install_global.py --vault <vault> --agent codex --agent claude from the plugin repo for global install.

For project-local install, run python scripts/install.py --target <project> --project <name> --agent codex --agent claude. If --vault or --write-root is omitted, the installer prompts for local paths, stores them in ~/.obsidianify/config.json, and writes agent-visible reminders to <project>/.obsidian-memory/sidecar_memory.json.

Start a new agent session in the target project.

Ask what Obsidian graph memory was injected.

If memory is missing, inspect <target>/.obsidian-memory/STATUS.json.

Reliability

SessionStart hooks refresh the packet.

UserPromptSubmit hooks record lightweight turn markers.

Stop hooks classify the latest prompt plus completed turn outcome and write valuable entries into typed notes under <vault>/<project>/sessionYYYY-MM-DD/.

Turn notes include distilled prompt memory and assistant outcome summaries; raw full prompts stay in the local marker store unless the user explicitly asks for transcript capture.

Pure Git bookkeeping prompts/outcomes, such as commit, push, status, branch, and origin/main updates, are skipped as noise unless the turn also contains durable implementation, architecture, configuration, or design details.

Any response containing direct Git command text, such as git add, git commit, or git push, is skipped even when it also mentions implementation details or files like config.json.

Obsidianify release/update bookkeeping, such as refreshing desktop/CLI environments, hook version updates, and origin/main status, is skipped as noise unless it includes real code-change details.

A project config can set vaultPath to choose the recording vault for that project: projects.<name>.vaultPath.

A project config can set writeRoot to write turn notes under a project-specific root instead: projects.<name>.writeRoot/sessionYYYY-MM-DD/.

Installer-managed sidecar entries for vaultPath and writeRoot are synced back into ~/.obsidianify/config.json during refresh-global and turn recording.

On Windows, Codex hooks use PowerShell call syntax and Claude hooks use a bash-safe powershell.exe -Command wrapper. Claude templates must use whole-command placeholders so they cannot emit raw quoted Python commands.

AGENTS.md or CLAUDE.md tells the agent to read the packet.

The first user prompt can force verification.

Do not claim the model remembered Obsidian by itself. The injected context comes from the generated packet.