Pka Bootstrap

ALWAYS use this skill when the user mentions PKA, personal knowledge, repo map, knowledge base setup, replacing Obsidian/Notion/Tana/Heptabase, organizing notes and files into a unified system, adding roles to their AI team, project lifecycle management, transitioning or archiving projects, restoring archived projects, checking which projects are stale or winding down, bootstrapping any kind of personal knowledge assistant, OR setting up Obsidian coexistence / a hybrid monorepo (root .git + child repos at knowledge/ and projects/* coordinated via .meta). Triggers also include: "bootstrap obsidian", "bootstrap vault", "MOC stubs", "frontmatter retrofit", "bootstrap git", "initialize the hybrid repo", "set up the meta monorepo", "bootstrap all", "bootstrap everything". This skill handles first-run setup (scanning folders, inferring structure, writing CLAUDE.md, creating SQLite indexes, defining roles) AND ongoing management (updating the repo map, adding team roles, transitioning completed projects to a knowledge archive, checking project activity) AND the additive Obsidian / hybrid-monorepo bootstraps (idempotent, user-triggered, never auto-run). Use it even if the user doesn't say "PKA" explicitly — if they want to unify scattered notes, set up AI-powered file organization, or manage workspace lifecycle, this is the right skill.

mkdir -p ~/.claude/skills/pka-bootstrap
curl -L https://claudskills.com/skills/pka-bootstrap/SKILL.md \
  -o ~/.claude/skills/pka-bootstrap/SKILL.md

@misc{pka-bootstrap-2026,
  author    = {rappdw},
  title     = {Pka Bootstrap [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/pka-bootstrap/}
}