obsidian-plugin/skills/publish-sync/SKILL.md
Obsidian Publish and Sync operations. Use when publishing notes, managing change sets, pausing/resuming sync, or recovering sync-deleted files.
npx skillsauth add laurigates/claude-plugins publish-syncInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| Use this skill when... | Use the alternative instead when... |
|---|---|
| Listing, adding, removing, or auditing the change set on Obsidian Publish | Creating or moving the underlying notes themselves — use vault-files |
| Pausing/resuming Obsidian Sync or checking sync status & usage | Restoring a previous sync version of a file — use file-history |
| Recovering a file that sync deleted | Recovering a file from local File Recovery — use file-history |
| Auditing which notes are currently public vs private | Discovering orphaned or unresolved-link notes — use search-discovery |
Manage Obsidian Publish and Obsidian Sync services from the CLI.
Sync version history (per-file diff and restore) lives in file-history.
# Slug, URL, status of the connected Publish site
obsidian publish:site
# All currently published files
obsidian publish:list
obsidian publish:list total
# What would change on next publish (new / changed / deleted)
obsidian publish:status
obsidian publish:status new
obsidian publish:status changed
obsidian publish:status deleted
obsidian publish:status total
# Publish the active file
obsidian publish:add
# Publish a specific file
obsidian publish:add file="Public Note"
obsidian publish:add path="blog/post.md"
# Publish *all* changed files in one shot
obsidian publish:add changed
# Unpublish
obsidian publish:remove file="Draft Post"
# Open the file's published page in the browser
obsidian publish:open file="Public Note"
# Sync state, last sync time, usage
obsidian sync:status
# Pause / resume sync
obsidian sync off
obsidian sync on
# Files removed via sync (recoverable)
obsidian sync:deleted
obsidian sync:deleted total
To restore one of those files, use file-history:
obsidian sync:restore file=X version=N.
For listing, reading, or restoring a specific sync version of a file, use
the file-history skill (sync:history, sync:read, sync:restore,
sync:open).
# Find candidates
obsidian search query="tag:#publish" format=json
# Or rely on the change set after the user tags them
obsidian publish:status new
obsidian publish:add changed
obsidian publish:status # all changes
obsidian publish:status new # adds only
obsidian publish:status deleted # removes only
obsidian publish:list > published-$(date +%F).txt
obsidian publish:site
obsidian sync:deleted
# Identify the file, then restore via file-history:
obsidian sync:restore file="Notes/Important" version=1
| Context | Command |
|---------|---------|
| Site info | obsidian publish:site |
| List published | obsidian publish:list |
| What's changed since last publish | obsidian publish:status |
| New files only | obsidian publish:status new |
| Publish all changes | obsidian publish:add changed |
| Publish one file | obsidian publish:add file=X |
| Unpublish | obsidian publish:remove file=X |
| Sync status | obsidian sync:status |
| Pause sync | obsidian sync off |
| Resume sync | obsidian sync on |
| Sync-deleted files | obsidian sync:deleted |
sync:history, sync:read, sync:restore)testing
Verify accumulated bug claims at upstream HEAD and dedup against trackers before filing issues. Use when filing upstream reports from backlogs, audit docs, or git-history findings.
documentation
Gate outward-bound text (upstream issues, docs, PR bodies) through isolated haiku fresh-reader critique before publishing. Use when an artifact must survive a reader with zero project context.
tools
Suggest improvements to SKILL.md content, descriptions, or tool config from eval results. Use when raising pass rates, fixing triggering, or iterating on a skill after evaluation.
tools
deadbranch CLI for stale-branch cleanup — dry-run preview, TUI or non-interactive delete, protects main/develop/WIP. Use when asked to clean up branches, prune branches, or remove stale branches.