ideas-funnel:init

Create missing Obsidian vault directories and template files for the ideas-funnel plugin.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/cosmicdreams/claude-plugins --skill ideas-funnel-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ideas-funnel:init
Source: https://github.com/cosmicdreams/claude-plugins/tree/main/ideas-funnel/skills/init
Command: npx skills add https://github.com/cosmicdreams/claude-plugins --skill ideas-funnel-init

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, Read, Write.

What problem does it solve?

This Skill removes the friction of setting up a consistent ideas-funnel vault structure by automatically creating missing directories, starter configuration, and schema scaffolding so you can start capturing and routing ideas immediately.

Core Features & Use Cases

  • Idempotent one-time bootstrap: Safely creates only missing files and folders each time you run it, preventing setup drift.
  • Vault + config verification: Ensures your Obsidian vault exists, creates required user config directories, and validates core scaffold elements.
  • Template + schema bootstrapping: Copies starter domain YAML and CRITICAL_FACTS.md when absent and appends the v2 extension block to wiki-schema.md when needed.
  • Next-steps checklist: Prints an operator-focused checklist so you know exactly what to edit next after initialization.

Use Case Example: You just installed the ideas-funnel plugin on a new machine and want the vault to have Raw/Inbox, Domains, _meta, and a working wiki schema extension without manually creating every folder and template file.

Quick Start

Ask the AI to run the initialization with: init ideas-funnel.

Frequently Asked Questions about ideas-funnel:init

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

FAQPage Schema
How do I set up an Obsidian vault structure automatically without creating duplicate folders?

To set up an Obsidian vault safely, this initialization process creates only missing scaffold directories, starter configuration files, and wiki schema extensions, ensuring idempotent bootstrap without overwriting existing files.

What is the best way to initialize a knowledge capture workflow in Obsidian?

Initializing a knowledge capture workflow requires verifying your Obsidian vault location, creating required folder structures like Raw/Inbox and Domains, and appending the v2 extension marker to wiki-schema.md for immediate idea routing.

Does this vault setup process work if I already have existing directories and template files?

Yes, the vault setup process is idempotent, meaning it verifies existing scaffold elements and repairs missing directories or configuration files without overwriting your current starter domain YAML or CRITICAL_FACTS.md templates.

How do I bootstrap wiki schema extensions and template files for a new Obsidian vault?

Bootstrapping wiki schema extensions involves copying starter domain YAML and CRITICAL_FACTS.md when absent, then appending the v2 extension block to wiki-schema.md to validate the knowledge capture structure.

Why does my Obsidian vault configuration need a scaffold directory verification?

Vault configuration needs scaffold directory verification to prevent setup drift and ensure mandatory folders like _meta exist, which allows the ideas-funnel plugin to route captured ideas correctly across repeat sessions.