engramme-assist

A profile-driven overlay for obsidian-wiki (by Ar9av). It keeps the upstream skill framework and adds a config profile so the personal skills (morning-brief, weekly-retro, jot, daily-update) read your identity, sources and scoring from a private YAML instead of hardcoding them. The skill code stays generic and shareable; your real values live in a gitignored profile.

obsidian-wiki (Ar9av)          engramme-assist (this overlay)
──────────────────────         ──────────────────────────────
vault structure, ingest,   +   profile.yml  ·  6 skills  ·  gardener/insights scripts
query, lint, export …          (identity & sources injected via {{profile.*}})

What it adds

• Profile — ~/.obsidian-wiki/profile.yml (global identity) merged with $VAULT/_meta/profile.yml (vault-local sources, tool prefs, brief scoring grid). Skills resolve {{profile.*}} placeholders from the merged result.
• 6 skills (see below) — wiki-init, wiki-profile, jot, morning-brief, weekly-retro, daily-update.
• gardener.py / insights.py — programmatic-first maintenance scripts dropped into $VAULT/_meta/scripts/.
• AGENTS.generic.md — framework conventions + profile-loading protocol, no personal values.

The skills

Each skill is invoked from your agent by a slash command or a natural phrase (EN + FR triggers).

Setup skills (run once)

Daily-use skills

Maintenance scripts (called by the skills, runnable by hand)

Install

pip install engramme-assist          # pulls obsidian-wiki (pinned) as a dependency
engramme-assist install --vault /path/to/your/vault

pip install -e .
python -m engramme_assist install --vault /path/to/your/vault

The overlay's skills and scripts ship inside the package (engramme_assist/_data/), so a plain pip install is self-contained — no clone required.

install does three things:

1. delegates the base install to obsidian-wiki setup (all upstream skills, global config, bootstrap files);
2. lays this overlay's six skills on top, into every agent obsidian-wiki supports — not just Claude (Gemini, Codex, Cursor, Windsurf, Hermes, Copilot, …). The target list is read from the pinned upstream, so it stays in sync automatically;
3. drops AGENTS.generic.md, profile.example.yml and the gardener scripts into the vault — non-destructively (an existing file is never clobbered).

Then, in your agent, say "set up my wiki" → wiki-init runs the structure setup and fills your profile interactively.

Install scope

--copy copies skill files instead of symlinking (forced automatically on Windows — see Platform notes).

Routines

Once the vault is set up, the rhythm is: a brief in the morning, a retro once a week, capture anytime.

Every working day

# in your agent, working directory = your vault
/morning-brief            # what you missed + what to prepare today
#   …or the evening before:  /morning-brief --night
/jot <a thought>          # capture goals / tasks / notes in <5s, any time of day

The maintenance pass (daily-update → gardener.py) keeps the index, hot.md and _raw/ lifecycle current. Run it explicitly with /daily-update, or let the 9 AM cron do it (set up once via daily-update, "set up the daily cron"). To run the mechanics directly:

export OBSIDIAN_VAULT_PATH=/path/to/your/vault
python3 $OBSIDIAN_VAULT_PATH/_meta/scripts/gardener.py            # dry-run report
python3 $OBSIDIAN_VAULT_PATH/_meta/scripts/gardener.py --apply    # apply lifecycle changes

Once a week (your retro day)

/weekly-retro             # interactive retro, primed by the week's data

It then runs the weekly maintenance tail automatically (cross-linker, hot-topics regeneration, lint report, history ingests). On the last retro of the month it also triggers the monthly review + brag compilation. The retro-day morning-brief adds a nudge to run it.

/weekly-retro annual [year]   # compile the year's retros into a self-assessment draft

Occasionally

python3 $OBSIDIAN_VAULT_PATH/_meta/scripts/insights.py   # refresh graph insights → _insights.md

Platform notes

• macOS / Linux: skills are symlinked to the installed package; a pip upgrade is picked up automatically. After upgrading obsidian-wiki, re-run engramme-assist install to re-seat the overlay copies.
• Windows: symlinks need Developer Mode/admin, so install defaults to copy mode (--copy forces it everywhere). After any pip upgrade, re-run engramme-assist install to resync. Maintenance scripts use the python launcher on Windows (python3 on macOS/Linux). The 9 AM cron + terminal notification (daily-update) is macOS-only (launchd) for now.

Privacy

Your real profile.yml and state/channels.yml (Slack IDs, colleague names, private channels) are gitignored and never published. Only generic code + *.example.yml are tracked.

Credit

Built on obsidian-wiki by Ar9av. MIT licensed.