How do I install the Wiki Initialize skill?

Run npx skillmds@latest add yarlson/wiki-initialize in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Wiki Initialize safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Wiki Initialize?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Wiki Initialize free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Wiki Initialize?

yarlson (@yarlson) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Wiki Initialize by yarlson — Agent Skill

Name: Wiki Initialize
Author: yarlson

Wiki Initialize

Create or adopt a user-controlled Yarbrain Markdown vault and configure lifecycle hooks to find it. Use when setting up Yarbrain, moving its vault, or repairing a missing vault structure; do not use for routine capture or maintenance.

yarlson Updated Sep 17, 2026

File contents

Initialize a Yarbrain Wiki

Create the canonical vault only at a location the user approves. Never initialize or reconfigure a vault as an implicit side effect of installing the plugin.

Workflow

Confirm the vault path, whether it is personal or shared, and whether an existing directory must be adopted without overwriting content.
Confirm authority to write the Yarbrain config. Its default location is ~/.config/yarbrain/config.json; YARBRAIN_CONFIG can select another file.
Resolve ../../scripts/yarbrain.py relative to this SKILL.md and run:
```
python3 <helper> init <vault-path>
```
Use --config only for an explicitly selected config path. Use --no-write-config when the user wants a vault without automatic hooks.
Verify that the command preserved existing files and created INDEX.md plus episodes/, notes/, skills/, inbox/, archive/, reports/, and .cache/.
Run the helper's lint command against the configured vault.
Report the vault and config paths, whether hooks can now find the vault, and any existing content that still needs adoption work.

The vault owns canonical Markdown. The config only locates it. Search indexes, session queues, and plugin installation directories are not canonical knowledge.

Do not import transcripts, create semantic notes, enable network access, or replace an existing index during initialization.

Frequently asked questions