agentleFS
0xSero0xSero/parcels/skills/parcel/SKILL.md

parcel

Skill171 starsChanged 4 months agoMITView on GitHub

Ship the current work — repo, uncommitted changes, .env files, and the live agent session — to another machine over Tailscale SSH, where the agent resumes in tmux and keeps working. Use when the user says /parcel, "hand off to <machine>", "send this work to another machine", "keep this running after I close the laptop", or wants to move a coding session (Claude Code, Codex, pi, Droid, or Grok Build) to a remote box.

  • Reads credentials

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. G1Joshi/Agent-Skills★ 15same name
    2. kvyb/context-parcel★ 2same name
    3. theYahia/pochta-russia-mcp★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    If you are Claude Code, your session id is the UUID in your scratchpad path (.../<uuid>/scratchpad).

    line 31
  2. Very specific:

    Only git repos can be parceled (parcel send runs from inside the repo).

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.

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

Parcel — hand off work to another machine

The parcel CLI is on PATH. Targets are machines defined in ~/.parcels/targets/<name>.conf; list them with parcel targets.

Workflow

  1. Write intent into HANDOFF.md at the repo root before shipping. This is the most valuable part of the handoff — the remote agent (possibly a different one) reads it first. Include:

    • what you were working on and why
    • current state (what works, what's verified, what's mid-flight)
    • concrete next steps, in order
    • known gotchas and how to verify progress

    Preserve any existing ## Machine state (auto-generated by parcel section — parcel regenerates it on every send.

  2. Ship. From inside the repo:

    parcel send <target> --agent <claude|codex|pi|droid|grok> [--session <id>]
    • If you are Claude Code, your session id is the UUID in your scratchpad path (.../<uuid>/scratchpad). If you are Grok Build, it is the session directory name under ~/.grok/sessions/<encoded-cwd>/<uuid>/. If unsure, omit --session — parcel picks the newest session for this cwd.
    • --agent grok (alias: grok-build) transplants a Grok Build session.
    • --prompt "..." steers what the remote agent does first (default: read HANDOFF.md and continue).
    • --idle ships without launching anything.
  3. Verify it is actually running — never assume. parcel status <target> tails the remote tmux pane; you should see the agent producing output. If the launch failed, run parcel doctor <target> and report exactly what is missing.
  4. Tell the user how to reach it: ssh -t <host> tmux attach -t parcel-<repo-name>.

Fixing missing auth (from parcel doctor)

  • claude — user runs claude login once on the target, or mints a token on an authed machine with claude setup-token and sets CLAUDE_CODE_OAUTH_TOKEN in the target's shell profile.
  • codex / pi / grok — parcel auth <target> copies the credential files. Grok alternative: set XAI_API_KEY on the target, or run grok login.
  • droid — user runs droid once on the target to log in.

Notes

  • Only git repos can be parceled (parcel send runs from inside the repo).
  • The whole working tree ships — including untracked files and .envs — so warn the user before sending a repo with secrets to a shared machine.
  • Re-sending the same repo overwrites the remote copy (rsync --delete) and restarts the tmux session.

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.