markdown-vault-sync
Markdown Vault Sync
Trigger Modes
Mode A: Immediate (user asks for vault sync)
When the user mentions syncing to Obsidian, getting docs into the vault, or putting project documentation in Obsidian — invoke this skill immediately and go straight to the Sync Workflow. Do NOT create local .md files first.
Mode B: Offer (after markdown work)
After creating or substantially editing markdown outside the vault, offer to sync if the content is:
- Reference material (guides, documentation, how-tos, API notes)
- Project-related (plans, itineraries, research, decisions, specs)
- Personal notes (meeting notes, summaries, journal-style entries)
- Knowledge capture (anything the user might want to find later)
Do not offer for READMEs/CHANGELOGs (belong in codebase), throwaway content, or files already in the vault.
More from ylt/claude-plugins
quip
>
14obsidian-vault
>
1obsidian-bases
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
1plugin-creator
Guide for creating Claude Code plugins. This skill should be used when the user wants to "create a plugin", "write a plugin", "build a plugin", "scaffold a plugin", "set up plugin structure", "configure plugin.json", "add commands to a plugin", "add agents to a plugin", "add hooks to a plugin", "add MCP server to a plugin", "add LSP to a plugin", "organize plugin components", or needs guidance on Claude Code plugin architecture, manifest configuration, or plugin distribution.
1conversation-summary
Transform long conversations into granular phase analyses and narrative synthesis. Use when a user provides conversation files (ChatGPT exports, interview transcripts, message logs, Slack exports, meeting notes) and asks to summarize, analyze, or extract insights. Triggers include requests to summarize conversations, analyze chats, process ChatGPT exports, summarize a directory of conversation files, or extract insights from long transcripts. Handles conversations too large for a single context window by chunking, parallel analysis, and narrative synthesis.
1git-rebase-squash
Clean up git commit history by squashing/reorganizing commits using non-interactive rebase. Use when user asks to "tidy up commits", "squash commits", "clean up history", "rebase", or wants N specific commits total. This skill handles the mechanics of rebasing in non-interactive environments where `git rebase -i` won't work.
1