Scan the Obsidian wiki and automatically discover missing cross-references between pages. Use this skill when the user says "link my pages", "find missing links", "cross-reference", "connect my wiki", "add wikilinks", "what pages should be linked", or after any large ingestion to ensure new pages are woven into the existing knowledge graph. Also trigger when the user mentions "orphan pages" in the context of wanting to connect them, or says things like "my wiki feels disconnected" or "pages aren't linked well". This is a write-heavy skill — it actually modifies pages to add links, unlike wiki-lint which just reports issues.
Run the daily wiki maintenance cycle: check all source freshness, update the index, and regenerate hot.md. Use this skill when the user says "/daily-update", "run the daily update", "update everything", "morning sync", "refresh the wiki index", or when triggered by the launchd cron at 9 AM. Also use to set up or verify the cron + terminal notification infrastructure for the first time ("set up the daily cron", "install the terminal notification", "how do I get the morning reminder?").
Audit and maintain the health of the Obsidian wiki. Use this skill when the user wants to check their wiki for issues, find orphaned pages, detect contradictions, identify stale content, fix broken wikilinks, or perform general maintenance on their knowledge base. Also triggers on "clean up the wiki", "what needs fixing", "audit my notes", or "wiki health check".
Initialize a new Obsidian wiki vault with the correct structure, special files, and configuration. Use this skill when the user wants to set up a new wiki from scratch, initialize the vault structure, create the .env file, or says things like "set up my wiki", "initialize obsidian", "create a new vault", "get started with the wiki". Also use when the user needs to reconfigure their existing vault or fix a broken setup.
Show the current state of the wiki — what's been ingested, what's pending, and the delta between sources and wiki content. Use this skill when the user asks "what's the status", "how much is ingested", "what's left to process", "show me the delta", "what changed since last ingest", "wiki dashboard", or wants an overview of their knowledge base health and completeness. Also use before deciding whether to append or rebuild. Includes an insights mode triggered by "wiki insights", "what's central", "show me the hubs", "central pages", "what's connected", "wiki structure" — analyzes the shape of the wiki itself to surface top hubs, cross-domain bridges, and orphan-adjacent pages.
Answer a MemoryLane question and return a structured TASK object the frontend renders as a tab in the right panel. Performs the same retrieval as `wiki-query`, but reshapes the result into the JSON contract defined in `memorylane/knowledge-frontend/data.jsx` — `activatedNodeIds`, `moments[]`, `entities[]`, `insight`, `blocks[]`, `sessionMeta`, `subassemblyTags`. Use this skill when the user invokes `wiki-ask <question>` or when a backend route (`POST /api/ask`) spawns claw with the question as the prompt. Distinct from `wiki-query` (returns prose with citations for human reading); this one returns machine-readable JSON for componentized rendering.
Resolve a vault page (moment, entity, session, or synthesis) into the JSON shape the MemoryLane frontend's evidence sheet renders. Given a `block_id` (file basename without `.md`) and optional `node_type` hint, parses the page's YAML frontmatter, tokenizes the markdown body into typed blocks (h1, h2, p, quote, links), resolves `[[wikilinks]]` to connected node ids, and emits a single JSON object to stdout. Use this skill when the user invokes `wiki-evidence <block_id> [<node_type>]`, or when a backend route (`/api/evidence/{block_id}`) spawns claw with that prompt. NOT a user-facing conversational skill — the output is machine-readable JSON for the frontend.
Export the vault as NODES + EDGES JSON for the MemoryLane frontend graph canvas. Walks moments/, sessions/, entities/{people,places,objects}/, and synthesis/, reads frontmatter, parses [[wikilinks]] for edges, computes a force-directed layout in a 1600×1100 viewport, and writes the result to $OBSIDIAN_VAULT_PATH/_meta/graph.json. Use this skill when the user says "export the graph", "rebuild the graph", "refresh frontend data", "regenerate graph.json", or after a batch of moments has been ingested. Distinct from `wiki-export` (which targets Gephi/Neo4j/GraphML for external graph tools) — this skill produces the in-app constellation viewer's exact data shape.