Skill

memex-sync

Syncs Zettelkasten cards across devices via git remotes. Initializes repos with URLs or auto-creates GitHub repos via gh CLI, pulls/merges/pushes changes, checks status, toggles auto-sync.

Git

Github

git-workflow

cli-tools

npx claudepluginhub iamtouchskyer/memex --plugin memex

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Sync your Zettelkasten cards across devices using git.

SKILL.md

Similar Skills

memex-organize

194

Maintains Zettelkasten card network by detecting orphans, hubs, contradictions in recent pairs, resolving conflicts, and rebuilding keyword index. For organize requests or scheduled maintenance.

memex

git-notes-memory

586

Manages branch-aware persistent memory using git notes to store/retrieve context, decisions, tasks, learnings across sessions via silent CLI commands.

2 files

sundial-org-awesome-openclaw-skills-4

multi-device

Syncs projects via git to enable working from multiple devices. Guides git setup for beginners or assumes knowledge as needed.

autocode

Stats

Stars194

Forks44

Last CommitApr 6, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Memory Sync

Sync your Zettelkasten cards across devices using git.

Tools Available

memex sync --init <url> — initialize sync with a git remote

memex sync --init — auto-create a private GitHub repo via gh CLI

memex sync — pull remote changes, commit local changes, push

memex sync --status — show sync configuration and last sync time

memex sync on|off — enable/disable auto-sync after every write/archive

Process

digraph 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"; }

Step 1: Check status

Run memex sync --status to see if sync is already configured.

Step 2: Initialize (if needed)

If sync is not configured:

Ask the user if they have a git repo URL for their cards

If yes: memex sync --init <url>

If no: memex sync --init (auto-creates a private memex-cards repo on GitHub via gh CLI)

Step 3: Sync

If already configured, run memex sync to push and pull changes.

Step 4: Report

Tell the user the result. If sync failed, show the error message.

Rules

Never force-push — memex sync uses git fetch + git merge then git push

On conflict — report the error and tell the user to resolve manually in ~/.memex

Auto-sync — only suggest memex sync on if the user asks about it; don't enable by default

Memory Sync

Sync your Zettelkasten cards across devices using git.

Tools Available

memex sync --init <url> — initialize sync with a git remote
memex sync --init — auto-create a private GitHub repo via gh CLI
memex sync — pull remote changes, commit local changes, push
memex sync --status — show sync configuration and last sync time
memex sync on|off — enable/disable auto-sync after every write/archive

Process

digraph 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";
}

Step 1: Check status

Run memex sync --status to see if sync is already configured.

Step 2: Initialize (if needed)

If sync is not configured:

Ask the user if they have a git repo URL for their cards
If yes: memex sync --init <url>
If no: memex sync --init (auto-creates a private memex-cards repo on GitHub via gh CLI)

Step 3: Sync

If already configured, run memex sync to push and pull changes.

Step 4: Report

Tell the user the result. If sync failed, show the error message.

Rules

Never force-push — memex sync uses git fetch + git merge then git push
On conflict — report the error and tell the user to resolve manually in ~/.memex
Auto-sync — only suggest memex sync on if the user asks about it; don't enable by default