cc
Skill6 starsChanged 2 months agoMITView on GitHub
Print a ready-made /compact line in a canonical handoff format, so the operator pastes it as the next message and shrinks working memory without losing the thread. Use at the end of a long session. Triggers: "/cc", "compact", "finish via compact".
In this repository100 other files it gives its agents.
- AGENTS.mdAGENTS.md
- 03Skill
- 1Skill
- agendaSkill
- alfa-search-recall-deepresearchSkill
- alpha-judgeSkill
- alpha-reviewSkill
- archSkill
- askSkill
- bibleSkill
- brainSkill
- busSkill
- canon-revisionSkill
- chatgpt-syncSkill
- chat-searchSkill
- chatSkill
- claudeai-syncSkill
- coachSkill
- codex-mirrorSkill
- codex-reviewSkill
- cofounderSkill
- cofounder-watchSkill
- commentsSkill
- community-alphaSkill
- content-mineSkill
- crm-syncSkill
- declinedSkill
- dedupSkill
- defuddleSkill
- dr-fanoutSkill
- episodeSkill
- faaa-syncSkill
- faSkill
- fb-postSkill
- fb-replySkill
- fb-watchSkill
- findSkill
- fireflies-syncSkill
- five-hardSkill
- fleetSkill
- follower-onboardSkill
- geminiSkill
- gitbook-importSkill
- gmailSkill
- granola-syncSkill
- handoffSkill
- health-syncSkill
- inboxSkill
- intakeSkill
- intentionSkill
- introSkill
- issue-matchSkill
- journeySkill
- last30daysSkill
- local-chatgpt-token-healSkill
- mcpSkill
- migrateSkill
- mine-channelSkill
- n8nSkill
- notebooklmSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 46
When to fire it: at a task boundary around 60% of the window.
- Very specific: line 47
Don't confuse: /tt = test what was built · /rr = full retro · /cc = quick compact handoff · /1 = resurrection after a crash.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/cc — compact in one keystroke
The pain: a bare /compact does NOT read our format (measured: 0 out of 354 — everything fell
back to the default, #14160). The ONLY thing that works is pasting an inline block right after
/compact. The operator used to fetch that block by hand. Now /cc assembles it itself, already
enriched with this session, and hands over a ready-to-paste line.
What this is NOT: it is not /retro. Retro = the full end of a session (inventory of what was
built → routing rules to their homes → and only then the compact handoff). /cc is only the
compact handoff itself, lightweight, with no inventory: for when the operator just wants to shrink
the window at a task boundary rather than close the session.
What to do when invoked
- Read the canonical template — the single source of the format (never invent headings):
The skeleton = 7 headings: DECISIONS · TODO · NOW · PATHS AND VALUES · COUNTERS · OPEN · TOOLS AND CONTRACTS.cat "$HOME/.claude/compact-prompt.md" # on Windows: %USERPROFILE%\.claude\compact-prompt.md - Enrich the block with the CURRENT session — never hand over an empty template. Walk the 7
headings and fill each one with the real, verbatim content of this chat (decisions + why, the
active error under NOW, exact paths/values/IDs, self-check counters +
/ttstatus ✅ vs not verified, what broke under OPEN). Rationales are the first thing to evaporate — preserve those first. - Emit the READY line — it starts with
/compact, followed by the enriched block, all inside a singlecodeblock so the operator can copy it whole and paste it as the next message. Plus one line above it: "➤ Copy everything in the block below and paste it as your next message." - 🧒 In plain words ([[eli5-always]]): "I'm packing our memory into a short note so nothing gets lost when the context is squeezed. Copy it and paste it."
Boundaries
- The folder name is
cc, so/ccworks natively; "compact" and similar words are text triggers for the same skill. Case does not matter ([[commands-case-insensitive]]). - The skill does NOT run the compact itself (that is a built-in command) and it sends/edits nothing — it only assembles text.
- When to fire it: at a task boundary around 60% of the window; don't wait for the auto-compact at 95% (that loses more).
- Don't confuse:
/tt= test what was built ·/rr= full retro ·/cc= quick compact handoff ·/1= resurrection after a crash.
<!--kit-footer-->Like this skill? It is one of 100 in second-brain-starter-kit: the second brain we built for ourselves and run every day at Palo Alto AI Research Lab. Install the whole set with npx skills add tonydzi/second-brain-starter-kit. Everything is open source and free, so take what you need.
Flagships worth a look on their own: secondop-panel (a second opinion from a panel of external models), claude-memory-tidy (stop your agent's memory from rotting), telegram-mcp-kit (your own Telegram over MCP in about 15 minutes).
Author: Anton Dziatkovskii, Palo Alto AI Research Lab. Telegram @tonydzi - WhatsApp +1 341 222 9178 - X @Tony_Stef_
Engineers: want to test-drive this setup? Message me. I hand out free starter seeds to engineers who test and report back, and custom skill requests are welcome.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

