skillboardUpdated every 6 hours
skillboardThis skill should be used when the user asks to "set up claude-mem", "pair claude-mem", "connect cmem", "add my cmem key", "set up cloud sync in Cowork", or provides cmem.ai Connect values (sync token, user id, SyncHub URL) for this plugin. Configures the claude-mem-cowork plugin credentials.
Configure this plugin with the user's own cmem.ai credentials so hooks can capture and inject memory. Anyone can pair — credentials are per-user configuration, never hardcoded in plugin logic.
From cmem.ai → Connect, the user has three values:
cm_) — used as the bearer API keyhttps://sync.cmem.ai)If the user pastes the whole Connect blurb, extract the three values from it. If any are missing, ask for the sync token at minimum — the other two are optional.
Locate the installed plugin root (this skill's own plugin). Update its
config.json: set apiKey to the sync token, userId, and syncHubUrl.
Leave other settings unless the user asks (inject toggles). Project naming
is automatic (cmem_work_*) and is not configurable.
Cowork containers are ephemeral: edits to the installed copy last only for
this session. To make pairing permanent, repackage — zip the plugin
directory as <plugin-name>.plugin and send it to the user to re-install
(the cowork-plugin skill's packaging flow). Tell the user this is why.
If this machine also has a local claude-mem install (a ~/.claude-mem/
directory exists), write the same values to
~/.claude-mem/settings.json with mode 0600 (CLAUDE_MEM_CLOUD_SYNC_TOKEN,
CLAUDE_MEM_CLOUD_SYNC_USER_ID, CLAUDE_MEM_CLOUD_SYNC_HUB_URL keys — the
same keys the local claude-mem cloud-sync pairing writes). This plugin's
hooks stay off wherever claude-mem is installed locally, so that pairing is
what carries this machine's work to cmem.ai. The worker reads those keys
only at startup: restart it and run the claude-mem cloud-sync skill's
Verify step, which must report configured: true and hub.reachable: true.
Don't report success before it does; if it never does, pair through that
skill's installer flow instead.
Verify without exposing the secret:
node "${CLAUDE_PLUGIN_ROOT}/scripts/cmem-hook.mjs" status
Report the masked output. A MISSING key means the write didn't land;
a 404 on /api/hooks/context is expected until the Pro endpoints deploy
(search/injection still work via /api/mcp).
Env vars override everything and need no file edits: CMEM_API_KEY,
CMEM_USER_ID, CMEM_SYNC_HUB_URL, CMEM_API_BASE.
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/mem-setup · pinned to the source commit
# Run from your project root
git clone https://github.com/thedotmack/claude-mem.git .skillboard-tmp
git -C .skillboard-tmp checkout fef3402e674bebbf72a23aeb735e91c92cd34afd
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/cowork/skills/mem-setup" ".claude/skills/"
rm -rf .skillboard-tmpReview the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
sudo apt update && sudo apt install -y gitnpm install -g @anthropic-ai/claude-code# Run from your project root
git clone https://github.com/thedotmack/claude-mem.git .skillboard-tmp
git -C .skillboard-tmp checkout fef3402e674bebbf72a23aeb735e91c92cd34afd
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/cowork/skills/mem-setup" ".claude/skills/"
rm -rf .skillboard-tmpDestination: .claude/skills/mem-setup
Scanner static-checks@0.1.0 · commit fef3402e674b. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
References credentials, tokens or secret files that a skill should not need.
Evidence: [redacted]· fingerprint 61ea4113f56ba6e8