Watchmen Setup
firstbatchxyz/watchmen
Walks through installing watchmen, running its init wizard, wiring the plugin into Codex or Claude Code and checking the result with doctor.
Pairs the claude-mem Cowork plugin with a cmem.ai account by writing the sync token, user id and SyncHub URL into the plugin config without exposing the secret.
Install Claude-Mem Cowork Pairing
$ npx skills add thedotmack/claude-mem --skill mem-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedotmack/claude-mem mem-setup --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/thedotmack/claude-mem.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cowork/skills/mem-setup .claude/skills/mem-setup && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "mem-setup" agent skill from https://github.com/thedotmack/claude-mem/tree/main/cowork/skills/mem-setup into .claude/skills/mem-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mem-setup", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/thedotmack/claude-mem/tree/main/cowork/skills/mem-setupType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add thedotmack/claude-mem --skill mem-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedotmack/claude-mem mem-setup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedotmack/claude-mem.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cowork/skills/mem-setup .agents/skills/mem-setup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "mem-setup" agent skill from https://github.com/thedotmack/claude-mem/tree/main/cowork/skills/mem-setup into .agents/skills/mem-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mem-setup", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedotmack/claude-mem --skill mem-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedotmack/claude-mem mem-setup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedotmack/claude-mem.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cowork/skills/mem-setup .cursor/skills/mem-setup && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "mem-setup" agent skill from https://github.com/thedotmack/claude-mem/tree/main/cowork/skills/mem-setup into .cursor/skills/mem-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mem-setup", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/thedotmack/claude-mem.git --path cowork/skills/mem-setup--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add thedotmack/claude-mem --skill mem-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedotmack/claude-mem mem-setup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedotmack/claude-mem.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cowork/skills/mem-setup .gemini/skills/mem-setup && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "mem-setup" agent skill from https://github.com/thedotmack/claude-mem/tree/main/cowork/skills/mem-setup into .gemini/skills/mem-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mem-setup", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install thedotmack/claude-mem mem-setupInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add thedotmack/claude-mem --skill mem-setup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/thedotmack/claude-mem.git skills-src && mkdir -p .github/skills && cp -r skills-src/cowork/skills/mem-setup .github/skills/mem-setup && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "mem-setup" agent skill from https://github.com/thedotmack/claude-mem/tree/main/cowork/skills/mem-setup into .github/skills/mem-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mem-setup", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedotmack/claude-mem --skill mem-setup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install thedotmack/claude-mem mem-setup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedotmack/claude-mem.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cowork/skills/mem-setup .opencode/skills/mem-setup && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "mem-setup" agent skill from https://github.com/thedotmack/claude-mem/tree/main/cowork/skills/mem-setup into .opencode/skills/mem-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mem-setup", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
mem-setup- GitHub stars
- 98k
- Used in
- 1 other repo
- Token cost
- ~659 tokens
- SKILL.md length
- 309 words
- Files
- 1
- Skills in repo
- 26
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Pairs the claude-mem Cowork plugin with a cmem.ai account by writing the sync token, user id and SyncHub URL into the plugin config without exposing the secret.
- Works in 3 steps: sync token (starts with cm_) — used as… → user id (UUID) → SyncHub URL (a workers.dev or cmem.ai URL)
- Pairing the claude-mem Cowork plugin with a cmem.ai account
- SKILL.md covers What to collect, Secret handling — non-negotiable, Steps and Alternate source
- Calls node; needs CLAUDE_MEM_CLOUD_SYNC_TOKEN and CMEM_API_KEY
What it does
This skill fills in the credentials that the claude-mem-cowork plugin needs to capture and inject memory through cmem.ai. You supply three values from the Connect page: a sync token that starts with cm_, a user id and a SyncHub URL. If you paste the whole Connect text, the agent pulls the values out itself, and only the token is required.
Secrets are handled with care. The token is never echoed in the conversation, placed on a command line or logged, and it moves only through file writes and reads. The agent edits the plugin's config.json (apiKey, userId, syncHubUrl) and leaves the other settings alone unless you ask.
Cowork containers are ephemeral, so the skill explains that a permanent pairing means repackaging the plugin as a .plugin zip for you to reinstall. If a local ~/.claude-mem directory exists, it can also write matching keys to settings.json with restricted permissions. Success is checked with the plugin's cmem-hook.mjs status command, which prints a masked result, and environment variables such as CMEM_API_KEY can replace the file edits.
When your agent uses it
- Pairing the claude-mem Cowork plugin with a cmem.ai account
- Adding a cmem sync token after copying the Connect values
- Turning on cloud sync for claude-mem in a Cowork session
Example prompts
- “Set up claude-mem in Cowork, I will paste the cmem.ai Connect text next.”
- “Add my cmem key to the plugin config and check that the pairing worked.”
- “Connect cmem so cloud sync works in this session, and tell me how to keep it after the container resets.”
Requirements
- A cmem.ai account with the Connect values (sync token, user id, SyncHub URL)
- The claude-mem-cowork plugin installed
- Node.js to run the cmem-hook.mjs status check
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- sync token (starts with cm_) — used as the bearer API key
- user id (UUID)
- SyncHub URL (a workers.dev or cmem.ai URL)
What it can do on your machine
Read from SKILL.md and the folder at commit 71ddd11. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
node
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
CLAUDE_MEM_CLOUD_SYNC_TOKENCMEM_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Claude-Mem Cowork Pairing loads about 659 tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 309 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from thedotmack/claude-mem at commit 71ddd11, republished under its Apache-2.0 licence (© thedotmack). 309 words, ~659 tokens.
Download SKILL.mdSave it as
.claude/skills/mem-setup/SKILL.md (or your agent's skills folder).- name
- mem-setup
- description
- This 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.
- metadata.version
- 0.1.0
Claude-Mem Setup (Cowork pairing)
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.
What to collect
From cmem.ai → Connect, the user has three values:
- sync token (starts with
cm_) — used as the bearer API key - user id (UUID)
- SyncHub URL (a workers.dev or cmem.ai URL)
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.
Secret handling — non-negotiable
- Never echo the token back in conversation, put it in a shell argv, or log it.
- Move it only via file writes (Write/Edit tool) and file reads.
Steps
Locate the installed plugin root (this skill's own plugin). Update its
config.json: setapiKeyto the sync token,userId, andsyncHubUrl. Leave other settings unless the user asks (injecttoggles). 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>.pluginand 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), optionally write the same values to~/.claude-mem/settings.jsonwith mode 0600 (CLAUDE_MEM_CLOUD_SYNC_TOKEN,CLAUDE_MEM_CLOUD_SYNC_USER_ID,CLAUDE_MEM_CLOUD_SYNC_HUB_URLkeys — the same keys the local claude-mem cloud-sync pairing writes) — the hook script and the local worker both read it.Verify without exposing the secret:
bash node "${CLAUDE_PLUGIN_ROOT}/scripts/cmem-hook.mjs" statusReport the masked output. A
MISSINGkey means the write didn't land; a 404 on/api/hooks/contextis expected until the Pro endpoints deploy (search/injection still work via/api/mcp).
Alternate source
Env vars override everything and need no file edits: CMEM_API_KEY,
CMEM_USER_ID, CMEM_SYNC_HUB_URL, CMEM_API_BASE.
© thedotmack, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in cowork/skills/mem-setup of thedotmack/claude-mem.
Open the folder on GitHubat commit 71ddd11
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in thedotmack/claude-mem, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Claude-Mem Cowork Pairing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Claude-Mem Cowork Pairing this skillthedotmack/claude-mem | 98k | 1 repos | ~659 | Automated safety check: Pass | Apache-2.0 | |
| Watchmen Setupfirstbatchxyz/watchmen | 296 | — | ~1.1k | Automated safety check: Notes | MIT | |
| OmniRoute Plugins, Skills and Memory CLIdiegosouzapw/OmniRoute | 74k | — | ~1k | Automated safety check: Pass | MIT | |
| Agentmemory Capture Hooksrohitg00/agentmemory | 29k | — | ~444 | Automated safety check: Pass | Apache-2.0 | |
| mnemon Persistent Memory for NanoClawnanocoai/nanoclaw | 31k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 38k | 11 repos | ~4.1k | Automated safety check: Notes | Apache-2.0 |
Similar skills
OmniRoute Plugins, Skills and Memory CLI
diegosouzapw/OmniRoute
Command reference for the omniroute CLI's memory, plugin, marketplace and skills commands: search and manage stored memory, install and scaffold plugins, and find skill packages.
Agentmemory Capture Hooks
rohitg00/agentmemory
Describes the lifecycle hooks in the agentmemory Claude Code plugin that record observations automatically, and what to check when observations go missing.
mnemon Persistent Memory for NanoClaw
nanocoai/nanoclaw
Installs mnemon in the agent container so agents recall relevant past context before replying and store new insights after every turn.
- Official
Hook Development for Claude Code Plugins
anthropics/claude-plugins-official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
- Official
Claude Code Agent Development
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
More from thedotmack/claude-mem
All 26 skills in this repoCustom Mode Creator for claude-mem
thedotmack/claude-mem
Walks you through creating, installing and verifying a custom claude-mem mode, including note types, tags and optional Telegram alerts for chosen memories.
Claude-Mem Cloud Sync
thedotmack/claude-mem
Checks claude-mem cloud sync status and guides you through connecting a cmem.ai Pro account without the sync token ever passing through the chat.
Claude-Mem Search
thedotmack/claude-mem
Searches the user's persistent cross-session memory for timestamped observations synthesized from past agent sessions on cmem.ai.
Project Timeline Report
thedotmack/claude-mem
Writes a narrative Journey Into report on a project's whole development history, built from the timeline that claude-mem has recorded.
Pull Request Babysitter
thedotmack/claude-mem
Keeps watching a pull request, fixing real review and CI problems and resolving stale threads, until it is clean and ready to merge.
Claude-Mem Install for Grok Bot
thedotmack/claude-mem
Use this when setting up claude-mem on Grok Bot: local worker plus CMEM Pro observer (default), optional host-login observer, or remote cmem.ai. No Cursor…
Related
Categories
Questions about Claude-Mem Cowork Pairing
What does Claude-Mem Cowork Pairing do?
Pairs the claude-mem Cowork plugin with a cmem.ai account by writing the sync token, user id and SyncHub URL into the plugin config without exposing the secret. ai. You supply three values from the Connect page: a sync token that starts with cm_, a user id and a SyncHub URL.
When should I use Claude-Mem Cowork Pairing?
Claude-Mem Cowork Pairing fits situations like: pairing the claude-mem Cowork plugin with a cmem.ai account; adding a cmem sync token after copying the Connect values; turning on cloud sync for claude-mem in a Cowork session.
How do I install Claude-Mem Cowork Pairing in Claude Code?
Run `npx skills add thedotmack/claude-mem --skill mem-setup -a claude-code`. Or copy the skill folder (cowork/skills/mem-setup in thedotmack/claude-mem) into .claude/skills/mem-setup in your project. Claude Code loads it when a task matches its description.
How do I install Claude-Mem Cowork Pairing in Codex?
Run `npx skills add thedotmack/claude-mem --skill mem-setup -a codex`. Or copy the skill folder (cowork/skills/mem-setup in thedotmack/claude-mem) into .agents/skills/mem-setup in your project. Codex loads it when a task matches its description.
Can I use Claude-Mem Cowork Pairing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thedotmack/claude-mem --skill mem-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mem-setup, .gemini/skills/mem-setup, .github/skills/mem-setup and .opencode/skills/mem-setup in your project.
What does Claude-Mem Cowork Pairing need to run?
Going by SKILL.md and its folder, Claude-Mem Cowork Pairing needs the command-line tools its instructions call (node) and credentials named CLAUDE_MEM_CLOUD_SYNC_TOKEN and CMEM_API_KEY. Our summary lists: A cmem.ai account with the Connect values (sync token, user id, SyncHub URL); The claude-mem-cowork plugin installed; Node.js to run the cmem-hook.mjs status check.
Does Claude-Mem Cowork Pairing access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Claude-Mem Cowork Pairing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Claude-Mem Cowork Pairing use?
Claude-Mem Cowork Pairing is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Claude-Mem Cowork Pairing use?
About 659 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Claude-Mem Cowork Pairing?
Skills that share tags, products or a category with Claude-Mem Cowork Pairing: Watchmen Setup (firstbatchxyz/watchmen, 296 stars), OmniRoute Plugins, Skills and Memory CLI (diegosouzapw/OmniRoute, 74k stars), Agentmemory Capture Hooks (rohitg00/agentmemory, 29k stars) and mnemon Persistent Memory for NanoClaw (nanocoai/nanoclaw, 31k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Claude-Mem Cowork Pairing?
thedotmack (a GitHub user) maintains it in thedotmack/claude-mem, which has 97,851 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on October 7, 2026.
Source: thedotmack/claude-mem on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.