- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add Ar9av/obsidian-wiki --skill session-brain -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add Ar9av/obsidian-wiki --skill session-brain -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add Ar9av/obsidian-wiki --skill session-brain -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add Ar9av/obsidian-wiki --skill session-brain -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/Ar9av/obsidian-wiki/tree/HEAD/skills/session-brainDel publicador
Builds a searchable topic graph over your agent session history. The output is a sidecar
at ~/.claude/session-brain/ — the vault is never touched.
All the heavy lifting is deterministic Python in the obsidian-wiki CLI. Your only job is to
name the clusters, which takes exactly one turn and requires reading no transcripts.
obsidian-wiki sessions-build --json
Roughly 3 seconds cold on ~1000 sessions, well under a second incrementally — it re-reads only transcripts whose size or mtime changed. Useful flags:
Report the headline numbers: total sessions, how many have transcripts vs. are history-only, edges, and cluster count.
obsidian-wiki sessions-clusters --unnamed --json
Each cluster comes with top_terms and exemplars (its three highest-degree sessions, whose
titles are already in graph.json). That is all you need. Do not open transcripts to name a
cluster — the whole design goal is that naming costs one turn regardless of corpus size.
Write a 3–5 word name and a one-sentence summary per cluster, then:
obsidian-wiki sessions-name --from - <<'EOF'
[{"id": 3, "name": "warden telemetry pipeline", "summary": "Building and debugging the redacted telemetry chain."}]
EOF
Names are stored in names.json keyed by the cluster's dominant vocabulary, not its id — so they
survive rebuilds even though cluster ids are positional and shift as the corpus grows. On repeat
runs --unnamed is usually empty and this step is free.
If a cluster's terms are genuinely incoherent, name it honestly ("mixed — short sessions")
rather than inventing a theme.
Read clusters.json and tell the user:
sizemomentum (activity in the last 30 days vs. the 60 before it)dormant: true (low recency and nothing in 60 days)bridges, the sessions that connect two otherwise separate topics.
These are often the most interesting sessions in the graph.Then offer the visualisation:
open ~/.claude/session-brain/graph.html
Node size is session length, brightness is recency, hollow rings are history-only sessions, and gold borders are bookmarked ones. The time slider and search box filter together.
wiki-history-ingest.history.jsonl; those get graph nodes and are findable, but can never be loaded. Say so plainly
rather than implying they are missing.--full rebuilds from scratch; nothing is lost.>
---name: session-braindescription: >---# skills/session-brain/SKILL.mdPreguntas frecuentes
Descarga skills/session-brain/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/Ar9av/obsidian-wiki.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.