Skill → Agent → Cluster Flow

Skill → Agent → Cluster Flow An architecture diagram generated by Archify. /wiki-ingest · skill · Architecture component /wiki-ingest skill /wiki-ask · skill · Architecture component /wiki-ask skill /wiki-init · skill · Architecture component /wiki-init skill /wiki-watch · skill · Architecture component /wiki-watch skill /save-conversation · skill · Architecture component /save-conversation skill wiki-ingest agent · Sonnet · Architecture component wiki-ingest agent Sonnet wiki-researcher · agent · Haiku · Architecture component wiki-researcher agent · Haiku Ingestion Pipeline · cluster · Architecture component Ingestion Pipeline cluster Search · cluster · Architecture component Search cluster Vault Ops · cluster · Architecture component Vault Ops cluster Watch · cluster · Architecture component Watch cluster Session Capture · cluster · Architecture component Session Capture cluster hook session-start · hooks.json event · hooks.json (Claude Code events) hook session-start hooks.json event hook post-tool-use · hooks.json event · hooks.json (Claude Code events) hook post-tool-use hooks.json event Stats · cluster · Architecture component Stats cluster dispatches one subagent per file hands off raw file records transcript_path logs tool calls hooks.json (Claude Code events) Legend Frontend Backend Database Cloud Security Message bus

Shared Agent

  • • /wiki-watch and /save-conversation both reuse the same wiki-ingest agent
  • • No duplicate ingestion pipeline — one agent dispatched from multiple entry points

Hooks

  • • Hooks run from hooks.json — not from a skill, unattended
  • • session-start records the transcript path /save-conversation later reads
  • • post-tool-use appends one JSON line per tool call for tool-call-stats

/wiki-init

  • • No agent involved — calls enchiridion init directly
  • • Pure scaffolding via vault.ts + vaultgit.ts (Vault Ops cluster)