From memex
Syncs Zettelkasten memory cards across devices via git push/pull/merge. Initializes remotes with URL or auto-creates private GitHub repo via gh CLI. Use when backing up or sharing cards multi-device.
How this skill is triggered — by the user, by Claude, or both
Slash command
/memex:memex-syncThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Sync your Zettelkasten cards across devices using git.
Sync your Zettelkasten cards across devices using git.
memex sync --init <url> — initialize sync with a git remotememex sync --init — auto-create a private GitHub repo via gh CLImemex sync — pull remote changes, commit local changes, pushmemex sync --status — show sync configuration and last sync timememex sync on|off — enable/disable auto-sync after every write/archivedigraph sync {
"User invokes /memex-sync" -> "memex sync --status";
"memex sync --status" -> "Configured?" [shape=diamond];
"Configured?" -> "memex sync" [label="yes"];
"Configured?" -> "Ask user for repo URL" [label="no"];
"Ask user for repo URL" -> "User provides URL?" [shape=diamond];
"User provides URL?" -> "memex sync --init <url>" [label="yes"];
"User provides URL?" -> "memex sync --init (auto-create via gh)" [label="no, use gh"];
"memex sync --init <url>" -> "Report success";
"memex sync --init (auto-create via gh)" -> "Report success";
"memex sync" -> "Report result";
}
Run memex sync --status to see if sync is already configured.
If sync is not configured:
memex sync --init <url>memex sync --init (auto-creates a private memex-cards repo on GitHub via gh CLI)If already configured, run memex sync to push and pull changes.
Tell the user the result. If sync failed, show the error message.
memex sync uses git fetch + git merge then git push~/.memexmemex sync on if the user asks about it; don't enable by defaultnpx claudepluginhub iamtouchskyer/memex --plugin memexMaintains a Zettelkasten card network by detecting orphan cards, hub cards, contradictions, and rebuilding the evolution of ideas. Run periodically or on demand to keep the card graph healthy.
Manages a multi-layered knowledge system: save, organize, sync, deduplicate, and retrieve across local files, MCP memory, vector stores, and Git repos.
Manages multi-layer knowledge systems across local files, MCP memory, Git repos, and Supabase. Handles ingestion, deduplication, sync, and retrieval for persistent knowledge.