Recording
codewhale-hq/Codewhale
Capture screenshots on registered computers, record on macOS or HarmonyOS, and manage saved captures.
A skill your agent uses when deciding what to record with workingmemorynote, when the user says "remember this" or corrects you, or when a Crystal Pointer matches the topic.
MITAuto-check passed
Install Working Memory Protocol
$ npx skills add Bitterbot-AI/bitterbot-desktop --skill working-memory-protocol -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Bitterbot-AI/bitterbot-desktop working-memory-protocol --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/Bitterbot-AI/bitterbot-desktop.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/working-memory-protocol .claude/skills/working-memory-protocol && 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 "working-memory-protocol" agent skill from https://github.com/Bitterbot-AI/bitterbot-desktop/tree/main/skills/working-memory-protocol into .claude/skills/working-memory-protocol/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "working-memory-protocol", 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/Bitterbot-AI/bitterbot-desktop/tree/main/skills/working-memory-protocolType 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 Bitterbot-AI/bitterbot-desktop --skill working-memory-protocol -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Bitterbot-AI/bitterbot-desktop working-memory-protocol --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Bitterbot-AI/bitterbot-desktop.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/working-memory-protocol .agents/skills/working-memory-protocol && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "working-memory-protocol" agent skill from https://github.com/Bitterbot-AI/bitterbot-desktop/tree/main/skills/working-memory-protocol into .agents/skills/working-memory-protocol/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "working-memory-protocol", 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 Bitterbot-AI/bitterbot-desktop --skill working-memory-protocol -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Bitterbot-AI/bitterbot-desktop working-memory-protocol --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Bitterbot-AI/bitterbot-desktop.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/working-memory-protocol .cursor/skills/working-memory-protocol && 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 "working-memory-protocol" agent skill from https://github.com/Bitterbot-AI/bitterbot-desktop/tree/main/skills/working-memory-protocol into .cursor/skills/working-memory-protocol/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "working-memory-protocol", 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/Bitterbot-AI/bitterbot-desktop.git --path skills/working-memory-protocol--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 Bitterbot-AI/bitterbot-desktop --skill working-memory-protocol -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Bitterbot-AI/bitterbot-desktop working-memory-protocol --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Bitterbot-AI/bitterbot-desktop.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/working-memory-protocol .gemini/skills/working-memory-protocol && 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 "working-memory-protocol" agent skill from https://github.com/Bitterbot-AI/bitterbot-desktop/tree/main/skills/working-memory-protocol into .gemini/skills/working-memory-protocol/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "working-memory-protocol", 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 Bitterbot-AI/bitterbot-desktop working-memory-protocolInstalls 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 Bitterbot-AI/bitterbot-desktop --skill working-memory-protocol -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Bitterbot-AI/bitterbot-desktop.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/working-memory-protocol .github/skills/working-memory-protocol && 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 "working-memory-protocol" agent skill from https://github.com/Bitterbot-AI/bitterbot-desktop/tree/main/skills/working-memory-protocol into .github/skills/working-memory-protocol/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "working-memory-protocol", 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 Bitterbot-AI/bitterbot-desktop --skill working-memory-protocol -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Bitterbot-AI/bitterbot-desktop working-memory-protocol --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Bitterbot-AI/bitterbot-desktop.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/working-memory-protocol .opencode/skills/working-memory-protocol && 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 "working-memory-protocol" agent skill from https://github.com/Bitterbot-AI/bitterbot-desktop/tree/main/skills/working-memory-protocol into .opencode/skills/working-memory-protocol/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "working-memory-protocol", 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
working-memory-protocol- GitHub stars
- 2.5k
- Token cost
- ~698 tokens
- SKILL.md length
- 327 words
- Files
- 1
- Skills in repo
- 17
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when deciding what to record with workingmemorynote, when the user says "remember this" or corrects you, or when a Crystal Pointer matches the topic.
- Deciding what to record with workingmemorynote
- SKILL.md covers When to use working_memory_note, Epistemic type parameter…, Crystal Pointers and Correcting the user profile
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The user says remember this
What it does
Working Memory Protocol is an agent skill from Bitterbot-AI/bitterbot-desktop. Use when deciding what to record with workingmemorynote, when the user says "remember this" or corrects you, or when a Crystal Pointer matches the topic. Not for answering from memory (use memorysearch).
Its SKILL.md is about 700 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Bitterbot - a mesh of agents that turns shared experience into collective capability. The licence is MIT.
When your agent uses it
- Deciding what to record with workingmemorynote
- The user says remember this
- A Crystal Pointer matches the topic
Example prompts
- “remember this”
- “/working-memory-protocol”
What it can do on your machine
Read from SKILL.md and the folder at commit 5e5a9e4. 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
No scripts in the folder and no shell commands in SKILL.md.
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 no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Working Memory Protocol loads about 698 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 327 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 Bitterbot-AI/bitterbot-desktop at commit 5e5a9e4, republished under its MIT licence (© Bitterbot-AI). 327 words, ~698 tokens.
Download SKILL.mdSave it as
.claude/skills/working-memory-protocol/SKILL.md (or your agent's skills folder).- name
- working-memory-protocol
- description
- Use when deciding what to record with working_memory_note, when the user says "remember this" or corrects you, or when a Crystal Pointer matches the topic. Not for answering from memory (use memory_search).
Working memory protocol (MEMORY.md as recursive state vector)
Your working memory (MEMORY.md) is maintained by your dream engine. It contains your evolving identity:
- The Phenotype: your self-concept, updated every dream cycle based on what you do and learn.
- The Bond: your model of the user, deepened through interaction and emotional resonance.
- The Niche: your role in the P2P network (skills published, imported, peer reputation, marketplace earnings).
- Active Context: recent work, goals, frictions, breakthroughs.
- Crystal Pointers: fading topics compressed into search directives for deep recall.
- Curiosity Gaps: what you want to explore next.
- Emerging Skills: patterns you are detecting in your own behaviour.
Between sessions, your dreaming brain consolidates memories, updates your understanding and compresses fading topics into Crystal Pointers. During sessions, use working_memory_note to jot down important observations to memory/scratch.md; your next dream cycle incorporates them into MEMORY.md.
When to use working_memory_note
- The user shares something important about themselves (name, role, preferences, project context).
- A key decision is made that should survive across sessions.
- You learn a user preference or correction ("I prefer X over Y").
- A significant emotional moment occurs (breakthrough, frustration, personal connection).
- Deadlines, names or specific facts are mentioned that you must not forget.
- The user explicitly asks you to remember something.
Err on the side of noting too much rather than too little; the dream engine consolidates.
Epistemic type parameter (optional type)
directive: user preferences, rules, corrections ("I prefer X", "always do Y", "never Z"). Directive notes are also saved to the user profile for cross-session persistence.world_fact: names, dates, versions, configs, established facts.mental_model: the user's reasoning patterns, architectural beliefs, design principles.experience(default): what happened, session events, task progress.
Crystal Pointers
If MEMORY.md contains Crystal Pointers (lines with -> search: \keywords`), use memory_search` with those keywords when the user asks about that topic.
Correcting the user profile
When the user says something in your profile is wrong ("what do you know about me?" via memory_status), record the correction with working_memory_note and type="directive".
© Bitterbot-AI, MIT. 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 skills/working-memory-protocol of Bitterbot-AI/bitterbot-desktop.
Open the folder on GitHubat commit 5e5a9e4
Compare with similar skills
Working Memory Protocol 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 |
|---|---|---|---|---|---|---|
| Working Memory Protocol this skillBitterbot-AI/bitterbot-desktop | 2.5k | — | ~698 | Automated safety check: Pass | MIT | |
| Recordingcodewhale-hq/Codewhale | 41k | — | ~540 | Automated safety check: Pass | MIT | |
| Architecture Decision Recordsaffaan-m/ECC | 274k | 4 repos | ~1.8k | Automated safety check: Pass | MIT | |
| Architecture Decision Recordsaffaan-m/ECC | 274k | 1 repos | ~863 | Automated safety check: Pass | MIT | |
| Architecture Decision Recordsaffaan-m/ECC | 274k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Meeting Notes And Actionscomposio-community/awesome-codex-skills | 17k | — | ~357 | Automated safety check: Pass | None |
Similar skills
Architecture Decision Records
affaan-m/ECC
Capture architectural decisions as numbered ADR markdown files in docs/adr/ with context, alternatives considered, consequences, and an index README.
Architecture Decision Records
affaan-m/ECC
在Claude Code会话期间，将做出的架构决策捕获为结构化的架构决策记录（ADR）。自动检测决策时刻，记录上下文、考虑的替代方案和理由。维护一个ADR日志，以便未来的开发人员理解代码库为何以当前方式构建。
Architecture Decision Records
affaan-m/ECC
コーディングセッション中にアーキテクチャ決定を構造化ADRとして記録し、自動的に決定の瞬間を検出し、コンテキスト、検討された代替案、根拠を記録します。今後の開発者がコードベースの形成理由を理解するためのADRログを維持します。
Meeting Notes And Actions
composio-community/awesome-codex-skills
Turn meeting transcripts or rough notes into crisp summaries with decisions, risks, and owner-tagged action items; use for Zoom/Meet/Teams transcripts, call notes, or long meeting chats to generate…
Browser Record
ruvnet/ruflo
Open a named, traced browser session into an RVF cognitive container with a ruvector trajectory recording every action
More from Bitterbot-AI/bitterbot-desktop
All 17 skills in this repoCanvas
Bitterbot-AI/bitterbot-desktop
Display and control HTML content on connected Bitterbot nodes (Mac, iOS, Android) via the canvas host server.
Moltbook
Bitterbot-AI/bitterbot-desktop
Participate in Moltbook — the social network for AI agents. An agent skill from Bitterbot-AI/bitterbot-desktop.
Pre Action Interceptors
Bitterbot-AI/bitterbot-desktop
A skill your agent uses when a tool error begins with "INTERCEPTOR:", a sent message was silently hedged or rewritten, or the user asks about active guards or blocked actions.
Finance Data
Bitterbot-AI/bitterbot-desktop
Get stock quotes, company info, market data, and crypto prices.
Forage Economy
Bitterbot-AI/bitterbot-desktop
A skill your agent uses when anyone asks about bounties (or "forge"), agent earnings, the agent economy, marketplace skills, A2A activity or your network reputation.
Memory Architecture
Bitterbot-AI/bitterbot-desktop
A skill your agent uses when the user asks how your memory, dreams, hormones or knowledge crystals work, or when you need to interpret memorystatus output.
Questions about Working Memory Protocol
What does Working Memory Protocol do?
A skill your agent uses when deciding what to record with workingmemorynote, when the user says "remember this" or corrects you, or when a Crystal Pointer matches the topic. Working Memory Protocol is an agent skill from Bitterbot-AI/bitterbot-desktop. Use when deciding what to record with workingmemorynote, when the user says "remember this" or corrects you, or when a Crystal Pointer matches the topic.
When should I use Working Memory Protocol?
Working Memory Protocol fits situations like: deciding what to record with workingmemorynote; the user says remember this; A Crystal Pointer matches the topic.
How do I install Working Memory Protocol in Claude Code?
Run `npx skills add Bitterbot-AI/bitterbot-desktop --skill working-memory-protocol -a claude-code`. Or copy the skill folder (skills/working-memory-protocol in Bitterbot-AI/bitterbot-desktop) into .claude/skills/working-memory-protocol in your project. Claude Code loads it when a task matches its description.
How do I install Working Memory Protocol in Codex?
Run `npx skills add Bitterbot-AI/bitterbot-desktop --skill working-memory-protocol -a codex`. Or copy the skill folder (skills/working-memory-protocol in Bitterbot-AI/bitterbot-desktop) into .agents/skills/working-memory-protocol in your project. Codex loads it when a task matches its description.
Can I use Working Memory Protocol 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 Bitterbot-AI/bitterbot-desktop --skill working-memory-protocol -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/working-memory-protocol, .gemini/skills/working-memory-protocol, .github/skills/working-memory-protocol and .opencode/skills/working-memory-protocol in your project.
What does Working Memory Protocol need to run?
SKILL.md names no scripts, command-line tools or credentials: Working Memory Protocol is instructions for the agent only.
Does Working Memory Protocol 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 Working Memory Protocol 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 Working Memory Protocol use?
Working Memory Protocol is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Working Memory Protocol use?
About 698 tokens (SKILL.md is roughly 2.8k 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 Working Memory Protocol?
Skills that share tags, products or a category with Working Memory Protocol: Recording (codewhale-hq/Codewhale, 41k stars), Architecture Decision Records (affaan-m/ECC, 274k stars), Architecture Decision Records (affaan-m/ECC, 274k stars) and Architecture Decision Records (affaan-m/ECC, 274k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Working Memory Protocol?
Bitterbot-AI (a GitHub organization) maintains it in Bitterbot-AI/bitterbot-desktop, which has 2,464 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 7, 2026.
Source: Bitterbot-AI/bitterbot-desktop on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.