wiki-setup is the first skill to run in the obsidian-wiki set. It asks where the vault and source documents live, creates the env config, builds the vault folders and special files, writes starter Obsidian settings and checks the result against a list.
It can also install a Claude Code stop hook that prompts a quick capture at the end of worthwhile sessions, and connect the vault to a private GitHub repository for backup and sync.
What You Get
- A configured vault with concepts, entities, skills, references, synthesis, journal and project folders
- Index, log, hot cache and manifest files ready for ingestion
- Obsidian app and appearance settings, with folder colors when the CLI is used
- A shared writing profile created once and never overwritten
- A verification checklist and a list of next skills to run
- Optional stop hook and GitHub sync
Common Use Cases
- Creating a new wiki vault for an agent to maintain
- Repairing a vault that lost its index or manifest
- Turning on staged writes for a team wiki that needs review
What Makes It Unique
It sets up the whole vault contract in one pass, including the timezone stored in the vault, the QMD collection check that keeps raw drafts out of the wiki index, and a staging folder for review. It never overwrites an existing writing profile or Obsidian file, and its Hermes path avoids a broad setup that would touch other agents. The hook and sync steps are opt-in questions.
Under The Hood
The skill is instructions for the agent. It creates folders and files in the vault and a config directory in the home folder, and it can run the obsidian-wiki command line tool for setup and for GitHub sync, which runs git init and sets a remote. If you accept the stop hook and its script is missing, it downloads the script with curl from the project’s GitHub repository, then edits your global Claude Code settings file to run that script when each session ends. It can also run the qmd tool and edit its config file.