Save user notes as markdown files with frontmatter in a ~/notes vault.
npx skills add https://github.com/carter2099/.dotfiles-homelab --skill note-save
Please help me install this Agent Skill. Skill: note-save Source: https://github.com/carter2099/.dotfiles-homelab/tree/main/.claude/skills/note-save Command: npx skills add https://github.com/carter2099/.dotfiles-homelab --skill note-save
Capture essential information by saving it into a centralized ~/notes vault, ensuring deduplication and consistent formatting with frontmatter, while keeping notes organized and searchable.
Provide the topic or content to save, and note-save will create a markdown note in ~/notes with frontmatter, update INDEX.md, and commit the changes.
High-intent search queries and answers about installing and using this skill.
To save markdown notes with frontmatter and auto-indexing, you provide the topic and content. The system creates a structured markdown file in ~/notes/<topic>/, enforces required frontmatter fields like title and tags, and updates an INDEX.md for quick discovery.
Organizing markdown notes with git history and deduplication involves saving files into topic-based directories while validating duplicate topics. The system commits changes to the vault's git history to preserve provenance and updates existing notes rather than creating duplicates.
Auto-indexing for a markdown notes vault works by automatically updating a global INDEX.md file every time a note is saved. This ensures all notes stored across various topic-based directories remain quickly discoverable and searchable.
Yes, saving notes to a tracked vault requires specific frontmatter fields. The system strictly enforces title, tags, source, created, and updated fields, ensuring dates are current and consistent across all markdown files for safe persistence.
Yes, you can update existing notes on duplicate topics. The system validates topic deduplication and automatically updates the existing markdown file in the ~/notes vault, committing the changes to git history rather than creating a redundant file.
When saving notes to topic-based directories, the system commits all changes directly to the vault's git history. This preserves provenance by tracking updates to existing notes and logging new markdown files as they are created.
chaimtInitialize a Git repository with an initial commit in the current directory.
spencerbeggsSearch design documentation with filters for module, category, status, and section.
SebastienDegodezInstall Husky as a dotnet tool to validate commits and format code.
brikkoAIAutomate Obsidian vault note management, wikilink updates, and content search via CLI.
