What problem does it solve?
Research projects scatter notes across folders with no consistent structure, making it hard to track sources, experiments, results, and writing over time. This Skill establishes and maintains a vault-first, project-scoped Obsidian knowledge base rooted at Research/{project-slug}/ so every durable note has a defined place, a registry entry, and navigable links.
Core Features & Use Cases
- Project Bootstrap and Binding: Detects the current repository, scaffolds the standard directory skeleton (Sources, Knowledge, Experiments, Results, Writing, Daily, Maps, Archive, _system), and binds the repo to a vault project root via .claude/project-memory.
- Registry, Hub, and Index Maintenance: Keeps _system/registry.md as the single machine-parsed registry with stable IDs, refreshes 02-Index.md auto-index blocks, and updates 00-Hub.md recent changes.
- Lifecycle Management: Handles note and project lifecycle actions including create, rename, archive, purge, detach, and link repair across Markdown notes and canvas files.
- Deterministic Lint Checks: Runs scripts for registry coverage, broken wikilinks, index coverage, canvas validation, and aggregated lint reports written to _system/lint-report.md.
- Use Case: A researcher starts a new paper replication project, asks the assistant to bootstrap the knowledge base, then logs daily notes, promotes stable findings into Results, and runs a lint check before a weekly review to catch broken links and unregistered notes.
Quick Start
Ask the assistant to bootstrap a new Obsidian project knowledge base for the current repository and point it at your vault path.
