🎯

cloud-sync

🎯Skill

Checks or sets up cloud backup for your claude-mem memory with a cmem.ai Pro account. It shows the sync status and guides you to sign in through the installer, so your secret key never appears in the chat.

thedotmack/claude-mem417 InstallsAdded Jul 14, 2026

Installation

$npx skills add thedotmack/claude-mem --skill cloud-sync

Run it in a terminal; it asks which AI coding tools to install it for (Claude Code, Codex, Cursor and more).

Uses skills.sh Β· Node.js 22.20+

After installing

Ask for related work and the agent uses it on its own, or call it yourself.

Run it (Claude Code)/cloud-sync
Install by hand

Copy the whole skill folder from GitHub to the place below. Copying only SKILL.md can leave out files the skill uses.

Open the skill folder β†’
  • This project .claude/skills/cloud-sync/
  • All projects ~/.claude/skills/cloud-sync/

These paths are for Claude Code. For other tools, the command above puts it in the right place.

Set up or check claude-mem cloud sync with cmem.ai Pro. Use when the user says "set up cloud sync", "sync my memories", "cmem pro", "cloud backup", "sync status", or wants their memory database backed up or synced to their cmem.ai account.

Cloud Sync (cmem.ai Pro)

The installed worker syncs through SyncHub. There is one client, one durable operation log, and no separate sync daemon. This skill checks status and points the user to the installer's cmem.ai sign-in, which writes the connection.

Security rule: never ask the user to paste the sync token into this chat, and never put it in a command you write, print it, put it in argv, or log it. A secret pasted into a chat lands in the transcript, which claude-mem itself can capture and sync. The installer writes the token to ~/.claude-mem/settings.json (mode 0600) without it ever passing through this conversation.

1. Check status

Resolve the worker port and query the always-registered status route:

PORT="${CLAUDE_MEM_WORKER_PORT:-$(node -e "const fs=require('fs'),p=require('path'),os=require('os');const uid=(typeof process.getuid==='function'?process.getuid():77);const fallback=String(37700+(uid%100));try{const s=JSON.parse(fs.readFileSync(p.join(os.homedir(),'.claude-mem','settings.json'),'utf-8'));process.stdout.write(String(s.CLAUDE_MEM_WORKER_PORT||fallback));}catch{process.stdout.write(fallback);}" 2>/dev/null)}"
curl -s "http://127.0.0.1:${PORT}/api/sync/status"
  • configured: true and hub.reachable: true β†’ the worker completed an authenticated GET /v1/sync/status against SyncHub. Report deviceId, pending counts, lastFlushAt, lastError, and the Hub head/checkpoint; stop unless the user asked to replace the connection.
  • configured: true and hub.reachable: false β†’ report hub.error and say the SyncHub connection is not verified. A zero pending count or lastError: null is not success because an empty queue performs no push.
  • configured: false β†’ continue.
  • Connection refused, 404, or 503 immediately after restart β†’ retry every three seconds for about 30 seconds before diagnosing the worker.

2. Connect through the installer

Ask the user to run this in their own terminal:

npx claude-mem install

and to choose CMEM Pro when the installer asks. The installer signs them in through the browser (they approve a device code), then writes the sync token, user id and SyncHub URL into ~/.claude-mem/settings.json itself and restarts the worker. Nothing secret is typed into this chat.

If the user cannot run the installer interactively (CI, a remote box), point them to the headless setup guide, https://docs.claude-mem.ai/cmem-pro-headless, and let them apply its manual recipe in their own terminal or editor. Do not collect the values yourself.

The worker mints and persists a device id on first start and defaults the device name to the hostname.

3. Verify

Once the installer finishes, poll the status route every five seconds for up to 30 seconds. If the worker was not restarted, restart it first:

curl -s -X POST "http://127.0.0.1:${PORT}/api/admin/restart"

Success means configured: true, hub.reachable: true, and lastError: null. The local route always makes an authenticated, read-only SyncHub status probe, even when every pending count is zero; it never uses a legacy cmem.ai Pro status route and never appends or advances sync state. Pending counts describe only writes made after the SyncHub launch baseline; setup does not migrate a pre-launch local corpus.

If hub.reachable is false, report hub.error. If lastError is non-null, report it too, and suggest running npx claude-mem install again to refresh the connection. Never include the token.

4. Report

Report device id, pending counts, last successful flush, Hub reachability and checkpoint, and any Hub/flush error. End with this privacy note:

Cloud sync uploads your observation narratives and full prompt text to your cmem.ai account.

More from this repository10

πŸͺ
thedotmack-claude-memπŸͺMarketplace

Claude-Mem gives Claude Code a memory that stays after a session ends. It keeps that memory in a compressed, shorter form.

πŸ”Œ
claude-memπŸ”ŒPlugin

claude-mem gives Claude Code a memory that lasts between sessions. It records what Claude does while you work, saves short summaries, and shows that context automatically when you start a new session.

🎯
mem-search🎯Skill

Searches your saved Claude-Mem memory on cmem.ai to recall what happened in earlier sessions. It answers questions like what you did last time on a project, file or decision.

🎯
smart-explore🎯Skill

Lets your AI agent explore a codebase by looking at its outline first, such as function and class names, instead of reading whole files. This saves the agent's reading budget. It uses three companion tools to search code, show a file's structure, and open only the part you need.

🎯
make-plan🎯Skill

Helps your AI agent write a step-by-step plan before building a feature. It first checks the real documentation for what is available, then splits the work into phases. Each phase has a clear goal, examples to copy, checks to prove it works, and mistakes to avoid.

🎯
do🎯Skill

Carries out a step-by-step plan by handing each piece of work to separate helper agents. After each step it checks the result, reviews the code and saves the changes to git only when the checks pass.

🎯
timeline-report🎯Skill

Writes a story-style report of a project's whole development history, based on the notes that claude-mem has saved over time. It needs the claude-mem background service to be running.

🎯
claude-code-plugin-release🎯Skill

Automated semantic versioning and release workflow for Claude Code plugins, bumps package.json, marketplace.json, and plugin.json in lockstep, runs the build, tags the commit, creates a GitHub release, and generates changelog entries. Enforces 'nothing left uncommitted or unpushed' by running git status at the end.

🎯
knowledge-agent🎯Skill

Turns the notes claude-mem keeps about your past work into focused knowledge bases you can chat with. You pick notes by project, topic, file, or date, load them into a session, then ask questions about past decisions and fixes.

🎯
design-is🎯Skill

Reviews a design against Dieter Rams' ten principles of good design, scoring each one with evidence. It then recommends a new design, a refinement or a redesign, and writes a ready-to-use prompt for /make-plan.