← ClaudeAtlas

exportlisted

Export everything needed to hand the work over to another machine, session or model into one compact file (PASSATION.md by default) - the goal and context, what is done, what runs, what is left (with the exact next step), the decisions and constraints of the user, the files and branches touched, the commands / tools / scripts used and how to build, test, run, the skills to load and the MCP servers / tools to set up, the state of the environment, the traps met - written for an AI reader in the rtk way (terse facts, no prose, no token wasted), never a secret - plus the ready-to-paste prompt that makes the new session pick the work up, saying whether the file must be sent with it (not when the new session works in the folder holding it). Use whenever the user asks to export / hand over / pass the work on ("export", "passation", "handoff", "fais une passation", "fais un md de passation", "exporte le contexte", "un prompt pour reprendre", "pour une autre session / machine / IA"), or summons /export.
TsukiNi22/ai-utils · ★ 1 · AI & Automation · score 74
Install: claude install-skill TsukiNi22/ai-utils
# Export: a handover file for another session / machine / model Write **one file** another AI reads to continue the work **without this conversation**: what is wanted, what is done, what is left and exactly how to go on. Default `PASSATION.md` at the root of the project (the cwd); another name or place only when the user says so. The reader is an AI: apply `rtk` (terse facts, one per line, no prose, no decoration, nothing said twice) - complete, not pretty. ## 1. Gather (read-only) - The conversation: the requests of the user (their words for the important ones), their answers to questions, their preferences and refusals, what was decided and why. - The task lists (TaskList / todos) and their states; the background work still running (jobs, shells, builds, tests) and how to check it. - The repository: `git status` / branch / last commits / unpushed work / worktrees / stashes, the files changed and not committed (`git diff --stat`), generated or temp files that matter (scripts kept in a temp folder: copy their path, or their content when the other machine will not have them). - The environment: OS, the tools and versions that matter, how to build / test / run / install, the services or processes in use (never stop them), the settings / env vars changed. - The memory and the project instructions (CLAUDE.md, rules the user gave) that the next one must follow. - **What the next one needs loaded**: the skills used and to load first (by name), the MCP servers relied on