ray-obsidian

Initialize and audit a local Obsidian vault structure for long-term knowledge and content production.

160|18|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/imraywang/rayskills --skill ray-obsidian-imraywang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ray-obsidian
Source: https://github.com/imraywang/rayskills/tree/main/skills/ray-obsidian
Command: npx skills add https://github.com/imraywang/rayskills --skill ray-obsidian-imraywang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Setting up a knowledge base that supports a full content pipeline—from raw materials to published drafts—usually means inventing folder structures by hand and risking damage to existing notes. This Skill safely creates, checks, or incrementally adapts a local Obsidian vault with a proven layered structure, without overwriting, moving, or deleting anything the user already has. ## Core Features & Use Cases - Safe Initialization: Creates missing directories, templates, and a .ray-obsidian.json manifest via a dry-run preview first, preserving all existing files. - Structure Auditing: Runs a check command that reports vault status (ready, incomplete, missing, invalid manifest) so you know exactly what is lacking. - Legacy Upgrade: Recognizes ray-content-v1 manifests and upgrades them to ray-content-v2 incrementally while keeping old notes and directories in place. - Use Case: You want to start writing with an AI-assisted content pipeline but have no knowledge base. The Skill locates or asks for a target directory, previews the changes, builds the full skeleton (materials, knowledge, candidate topics, writing tasks, drafts, publish feedback), and hands the vault path off to downstream writing skills. ## Quick Start Ask the AI to set up a local Obsidian knowledge base at a chosen directory that can later feed the ray-writer content workflow.

Frequently Asked Questions about ray-obsidian

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

FAQPage Schema
How do I set up an Obsidian vault for a content production workflow?▼

Run the vault setup script with the init command pointing at your target directory, after a dry-run preview. It creates layered directories for materials, knowledge, candidate topics, writing tasks, drafts, and publish feedback, plus templates and a manifest file.

How do I check if my Obsidian vault structure is complete?▼

Run the vault setup script with the check command and your vault path. It audits required directories, template files, and the manifest, returning a status of ready, incomplete, missing, or invalid-manifest with a list of what is missing.

Will initializing the vault overwrite my existing Obsidian notes?▼

No. The initialization only creates missing directories and files, and lists existing files as preserved. It never overwrites, moves, renames, or deletes user notes, and it does not touch the .obsidian configuration folder.

Can I upgrade an old ray-content-v1 vault to the new structure?▼

Yes. Vaults with a ray-content-v1 manifest are detected as upgradeable. After a dry-run preview, the init command upgrades the manifest to ray-content-v2 and adds missing directories while leaving all old notes and folders in place.

What happens if the vault manifest is corrupted or unknown?▼

The script refuses to proceed. An unparseable manifest or an unrecognized schema version causes initialization to stop with an error rather than attempting any repair or overwrite.

Does this require Obsidian plugins, Git, or cloud sync?▼

No. The structure works with plain Markdown in any editor. The Skill does not install plugins, enable sync services, or initialize Git; those remain optional user choices.