spine-init

Create or adopt a Spine Architecture vault with Obsidian structure and config.

21|2|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Nodewarrior/spine --skill spine-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spine-init
Source: https://github.com/Nodewarrior/spine/tree/main/skills/spine-init
Command: npx skills add https://github.com/Nodewarrior/spine --skill spine-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of starting or adopting a Spine Architecture vault by creating the required Obsidian structure, configuration, and first spine note scaffolding for Claude Code knowledge capture.

Core Features & Use Cases

  • Fresh Vault Setup: Creates a new vault root, Obsidian graph configuration, and Spine Architecture metadata for a clean start.
  • Vault Adoption: Integrates an existing markdown vault into Spine conventions without moving or deleting user content.
  • Repo and Feature Organization: Detects or creates the first repository and feature structure so future docs stay organized and linked.
  • Operational Validation: Checks naming conventions, graph color settings, and document linkage expectations to keep the vault usable over time.

Quick Start

Ask the assistant to initialize a Spine vault at your chosen path or to adopt your existing Obsidian vault into Spine conventions.

Frequently Asked Questions about spine-init

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up an Obsidian vault for Claude Code knowledge tracking?

To set up an Obsidian vault for Claude Code, you need to initialize the directory structure, graph configuration, and spine note scaffolding. This process creates the required metadata to track repositories and features without moving existing files.

Can I integrate an existing markdown vault into Spine conventions without losing files?

Yes, you can adopt an existing markdown vault into Spine conventions without moving or deleting content. The process validates vault paths, graph colors, and type-tagged documents, applying the architecture metadata directly to your current directory.

What is Spine Architecture in Obsidian used for?

Spine Architecture is an Obsidian vault structure used for Claude Code knowledge tracking. It organizes repositories and features through linked spine notes and type-tagged documents, ensuring documentation stays connected and maintainable over time.

How to validate Obsidian graph configuration and spine notes?

You validate Obsidian graph configuration and spine notes by running an operational check on the vault. This checks naming conventions, graph color settings, repo folders, and document linkage expectations to keep the vault usable.

Does initializing a new Spine vault require manually creating repository folders?

No, initializing a Spine vault does not require manually creating repository folders. The setup process automatically detects or creates the first repository and feature structure so future docs stay organized and linked.

What are the limitations of adopting an existing markdown vault into Spine?

The limitation of adopting an existing markdown vault is that the process only validates and writes configuration without moving or deleting existing files. It applies Spine conventions but requires your content to match naming and linkage expectations.