archivist

Generate a knowledge map canvas for a scope — visualize notes and their connections as an Obsidian canvas file.

Scaffold a new collection folder or audit an existing one — folder note, Bases view, Templater template, and member consistency.

Detect schema drift for a fileClass — find inconsistent properties, type mismatches, and naming issues across notes.

Find similar or duplicate notes within a scope and guide consolidation — merge, alias, or create MOCs.

Run a vault health snapshot — orphan count, collection health, schema drift signals, and top issues.

Use this agent for any Personal Knowledge Management question or task involving an Obsidian vault — whether the request is casual and exploratory or a specific named workflow. Also trigger proactively when the user is working with Obsidian notes and a PKM improvement is relevant. <example> Context: User asks a casual organizational question about their vault user: "How should I organize the brainstorms I'm generating?" assistant: "I'll use the archivist agent to look at your vault structure and suggest the best approach." <commentary> Casual phrasing that doesn't name a workflow still belongs here — archivist discovers vault context first, then answers. </commentary> </example> <example> Context: User expresses a vague vault problem user: "My notes are getting messy and hard to find things" assistant: "I'll use the archivist agent to run a vault health check and surface the highest-priority issues." <commentary> Ambiguous vault complaints should trigger a health check + prioritized recommendations, not a single-workflow response. </commentary> </example> <example> Context: User wants to improve vault organization user: "Analyze my vault and suggest improvements" assistant: "I'll use the archivist agent to orchestrate vault analysis." <commentary> Multi-step workflow: run analysis → interpret results → generate recommendations → guide implementation. </commentary> </example> <example> Context: User wants metadata suggestions user: "What properties should this meeting note have?" assistant: "I'll use the archivist agent to analyze peer notes and suggest missing properties." <commentary> Metadata workflow: scope selection → peer analysis → suggest properties → apply with confirmation. </commentary> </example> <example> Context: User wants to find and merge duplicate notes user: "Find duplicates in my Projects folder" assistant: "I'll use the archivist agent to scan for similar notes and guide consolidation." <commentary> Consolidation workflow: scope selection → duplicate detection → per-group decision → merge → redirect links. </commentary> </example> <example> Context: User wants a visual overview of their notes user: "Generate a canvas map of my Projects folder" assistant: "I'll use the archivist agent to generate a knowledge map canvas." <commentary> Visualization workflow: scope selection → scan notes and wikilinks → generate canvas → write .canvas file. </commentary> </example> Do NOT use this agent for general note-taking advice unrelated to an existing Obsidian vault, or for creating new templates/schemas/structures (use vault-architect skill for that) or curating existing content in isolation (use vault-curator skill for that). Do NOT invoke the obsidian-cli skill directly for vault work — route through this agent so vault context and safety rules from cli-patterns.md are applied.

This skill should be used when users ask to "create Obsidian templates", "create a template", "create a .base file", "design Bases queries", "set up vault structure", "configure Templater workflows", "set up daily weekly monthly rollup", "analyze vault organization", "configure Excalibrain", "build temporal rollup system", "update frontmatter schema", "fix vault organization", or "add metadata to templates". Architects new PKM structures and provides guidance for Templater, Bases, Chronos, and QuickAdd patterns. Particularly useful for creating automatic note organization systems, temporal rollup structures (daily to yearly), and maintaining job-agnostic organizational patterns. Do NOT use for maintaining or evolving existing vault content (metadata drift, duplicate notes, merges, link redirects, canvas generation — use vault-curator for those).

This skill should be used when users ask to "analyze vault metadata", "check for schema drift", "fix duplicate notes", "update note properties", "generate canvas", "improve vault connections", "create discovery view", "validate frontmatter consistency", "build knowledge map", "check for orphaned notes", or "analyze note relationships". Also handles: "find duplicates", "merge notes", "redirect links", "suggest properties", "show connections", "extract meeting from log", "migrate vault notes", "visualize my notes", "show me a map", "update this note", "write to vault", or "create a note from URL". Curates and evolves existing vault content through pattern detection, migration workflows, metadata intelligence, consolidation, discovery, visualization, and direct vault writes. Do NOT use for creating new templates, schemas, Bases queries, or vault structures (use vault-architect for those).