Import Obsidian vaults, markdown folders, or git repositories into llm-wiki vaults.
npx skills add https://github.com/RonanCodes/llm-wiki --skill vault-import
Please help me install this Agent Skill. Skill: vault-import Source: https://github.com/RonanCodes/llm-wiki/tree/main/.claude/skills/vault-import Command: npx skills add https://github.com/RonanCodes/llm-wiki --skill vault-import
Importing existing markdown collections, Obsidian vaults, or git repos into an llm-wiki requires repeated manual steps: moving or copying files, preserving history, adding consistent frontmatter, creating wiki structure, and auditing content placement. This Skill reduces friction by analyzing an existing repository or folder, proposing a migration plan, and creating the llm-wiki scaffolding while preserving user data and git history.
Run the command /vault-import ~/path/to/source --name my-research --domain ai-research to analyze the source and interactively import it into vaults/my-research.
High-intent search queries and answers about installing and using this skill.
You can import an existing Obsidian vault into llm-wiki by running the vault-import command with a local path or remote git repository. The Skill detects Obsidian configurations, proposes a migration plan, and preserves git history while adding structured frontmatter.
When migrating a knowledge base, the Skill classifies markdown files into raw sources, wiki pages, and concepts. It creates vault directories, generates index.md and CLAUDE.md, and patches YAML frontmatter while avoiding destructive file moves without user confirmation.
Yes, you can import a remote git repository into llm-wiki vaults by providing the repo path. The Skill analyzes the repo structure, counts markdown files, and interactively suggests classification while preserving git history during the migration.
The vault migration process does not automatically overwrite existing frontmatter; it adds or patches YAML frontmatter for wiki pages while creating structural files like index.md and CLAUDE.md. It prompts the user before moving or modifying original files to prevent destructive changes.
The best way to structure a public knowledge repo for LLM summarization is to use an interactive migration plan that classifies content into raw sources, wiki pages, and concepts. This creates llm-wiki scaffolding and consistent YAML frontmatter for incremental ingestion.
Using an interactive migration plan when onboarding markdown folders prevents automatic, destructive file moves. The Skill scans the source, detects configurations, and prompts you to confirm classification and placement of raw sources and wiki pages before applying any changes.
ZorroCheng-MCAutomate Obsidian vault organization and publishing to GitHub Pages.
HelloWorldSunginReport page counts, category breakdowns, and structural insights for Obsidian vaults.
ignromanovScaffold a complete LLM Wiki vault with directory structure, config, and templates.
winsorllcSearch, list, create, read, append, and link Obsidian markdown notes.
