Store Claude-generated plan and design documents into a structured Obsidian vault.
npx skills add https://github.com/sukeun1997/claude-config --skill docs-save
Please help me install this Agent Skill. Skill: docs-save Source: https://github.com/sukeun1997/claude-config/tree/main/skills/docs-save Command: npx skills add https://github.com/sukeun1997/claude-config --skill docs-save
Claude-generated plan and design documents are often scattered and hard to archive with project context. This skill automatically saves those documents into an Obsidian vault under a structured path that preserves project and branch information, reducing manual copy-paste and naming errors.
Provide the source file path; the tool will save the document to your vault under the detected project and branch, injecting frontmatter and naming it correctly.
High-intent search queries and answers about installing and using this skill.
To save Claude-generated plan and spec documents to an Obsidian vault, provide the source file path. The skill detects the project from your current directory, derives the branch from git, and writes the document with merged frontmatter to the correct vault path.
Automatic project and branch detection works by reading your current working directory to identify the project, then deriving the branch slug from git. If git detection fails, it defaults to 'main', constructing the destination path under your vault accordingly.
No, the Obsidian document automation tool does not require manual frontmatter injection. It automatically merges frontmatter including title, type, project, branch, created date, and status fields to ensure consistency across all saved plan and design documents.
The file naming convention for saving files into an Obsidian vault assigns the destination filename as plan.md or spec.md based on the source type. The file is placed under the structured path ~/vault/{project}/{branch-slug}/.
Yes, you can use this automation to organize project documentation without manual copy-paste. It automatically structures files under ~/vault/{project}/{branch-slug}/ and injects consistent frontmatter, eliminating naming errors and scattered archives.
If git branch detection fails during the vault save process, the destination path construction defaults to the 'main' branch. This ensures your document is still saved under ~/vault/{project}/main/ with the correct plan.md or spec.md filename and frontmatter.
OmarHosamCodesInitialize and configure an Obsidian wiki vault with standardized folders and templates.
family3253Generate and edit Obsidian-flavored Markdown with wikilinks, embeds, callouts, and frontmatter.
elsa-workflowsValidate Git branch naming conventions and verify associated spec directories.
allenaiExport and organize research artifacts into markdown or HTML formats.
