agentleFS
TsukiNi22TsukiNi22/ai-utils/skills/ai/export/SKILL.md

export

Skill1 starsChanged 3 days agoMITView on GitHub

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.

  • Reads credentials

26 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use menu, import and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • sasly2048Skill

    menu

    Point the user to cc-atlas's full interactive menu (dashboard, project comparison, session replay, team activity, anomalies, goals) — screens that need a real terminal.

    Also in 3 projects that use this

  • michaelenglandSkill

    import

    This skill should be used when the user wants to import an existing .pptx file into deckwright, bring in a PowerPoint that was created outside this tool, reverse-engineer a presentation for editing, or invoke /deckwright:import. Converts a .pptx into a PptxGenJS generation script so it can be edited and regenerated through the deckwright pipeline.

    Also in 3 projects that use this

  • kv0906Skill

    preview

    Render vault notes as styled HTML and open in browser. Turn markdown docs, decisions, progress reports into readable previews. Use for "/preview docs/project-a/checkout-flow.md", "/preview progress all", "/preview decide auth-approach", or when user wants to see a doc before sharing.

    Also in 3 projects that use this

  • AnthropicSkill

    search

    Search across all connected sources in one query. Trigger with "find that doc about...", "what did we decide on...", "where was the conversation about...", or when looking for a decision, document, or discussion that could live in chat, email, cloud storage, or a project tracker.

    Also in 4 projects that use this

  • GoogleSkill

    dashboard

    Configures and launches the GKE Capacity & Triage Dashboard scoped to a GCP project ID, GKE cluster name, or target ML workload ID. Uses the configure-and-launch-dashboard action and launch-workload-dashboard workflow to verify local dashboard health, discover cluster capacity, trigger live scans, and generate deep-linked URLs. Use when the user types "/dashboard", says "launch dashboard", "open dashboard", "show capacity", or "view triage dashboard" with a project, cluster, or workload. Don't use for general workload log querying or automated failure attribution (use the troubleshoot skill).

    Also in 4 projects that use this

  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 1 is distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Stop and resume in the same project, at the next continue: the pause skill, not this one.

    line 10
  2. Very specific:

    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 …

    line 12
  3. Very specific:

    Every item actionable: a path, a command, an id, a version, an exact error text - never "see above" or "as discussed".

    line 51
  4. Very specific:

    Never a secret: no token, password, key, cookie, private URL with credentials, personal data beyond what the project needs.

    line 55
  5. Very specific:

    Add the one or two things the next one must do first (the exact next step of the top todo, a check of what still runs) and what it must …

    line 69
  6. Distinctive:

    Read the file as the next AI: can it continue alone (what, where, how, in which order, what not to touch)?

    line 73

“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Export: a handover file for another session / machine / model

Stop and resume in the same project, at the next continue: the pause skill, not this one.

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 (claude mcp list, .mcp.json: name, whether the new session has them, how to add a missing one), the CLI tools and their versions, the permissions / modes that mattered (auto mode, allowed tools), the subagents / background jobs pattern used.

2. Write it (sections in this order, empty ones dropped)

# PASSATION <project> <date> (<from: model / machine>)
## goal          the request(s) in one or two lines each; the user's own words when they matter
## rules         constraints of the user: git (commit / push allowed?), language, style, what never to do
## state         = done N · running N · todo N · blocked N
## done          - <what> (<where: file / commit / version>), checked how
## running       - <what> · check: <command> · expected: <result>
## todo          - [P1] <what> · next step: <exact action> · files: <paths>  (ordered: what to do first)
## blocked       - <what> · why · what unblocks it
## decisions     - <choice> · why · rejected: <alternative>
## files         $P=<common dir>; - $P/a.cpp: <what changed, uncommitted?>
## repo          branch · last commit · uncommitted / unpushed · worktree · how the release / commit is done
## env           os · tools (versions) · build: <cmd> · test: <cmd> · run: <cmd> · install: <cmd>
## tools         the scripts / helpers used and for what (path + one line)
## load          skills to load first: <names> · MCP needed: <name> (present? add: <cmd>) · CLI: <tool version> · mode: <auto / plan...>
## traps         - <what went wrong> → <how it is avoided> (flaky tests, quotas, guards, aliases...)
## refs          docs, issues, URLs, paths of logs / screenshots / reports
  • Every item actionable: a path, a command, an id, a version, an exact error text - never "see above" or "as discussed". Relative paths under a $P written once.
  • todo is the core: ordered, each with its next step precise enough to start without asking.
  • What the next one must not do (destructive commands, processes to keep, settings not to change) goes in rules.
  • Never a secret: no token, password, key, cookie, private URL with credentials, personal data beyond what the project needs; write where it lives instead (keyring: claude-cluster, env: API_KEY).
  • Long logs / diffs: never pasted; their path, or the 1-3 lines that matter.

3. The prompt for the new session

A short prompt the user pastes into the new session (a code block, in the language the user writes to it, French by default here), that makes it pick the work up at once:

  • The file reachable from there (the new session works in the project folder, or in claude-cluster on that project, or on this machine with access to the path): no need to send it - the prompt says to read it first, by its absolute path: lis <path>/PASSATION.md entièrement, charge les skills et vérifie les MCP listés dans "load", puis reprends au premier todo (P1) sans refaire ce qui est "done" ; respecte "rules".
  • Not reachable (another machine, claude.ai, a model without this folder, another project): say plainly that the file must be sent with the prompt (attached, or pasted after it), and write the prompt so it refers to "the file attached". Nothing reachable at all and the file short: offer the file content inlined in the prompt instead.
  • Add the one or two things the next one must do first (the exact next step of the top todo, a check of what still runs) and what it must never do (from rules); never repeat the whole file.

4. Check and report

  • Read the file as the next AI: can it continue alone (what, where, how, in which order, what not to touch)? Fill the holes; remove what it does not need.
  • Measure (wc -c, ~4 chars per token) and keep it short: a big context compressed, not copied.
  • Tell the user the path, the size and the counts in one or two lines, then the prompt (its code block) and whether the file must be sent with it; not committed unless they ask (or the project's rules allow it and they asked for a commit).
  • With claude-cluster running and the user wanting it: the new session can be started with that prompt directly (a new session in the project folder) - offered, never done without their go.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.