How do I install the Bring Home From Server skill?

Run npx skillmds@latest add thomirel/bring-home-from-server in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Bring Home From Server safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Bring Home From Server?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Bring Home From Server free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Bring Home From Server?

ThomirEL (@thomirel) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Bring Home From Server by thomirel — Agent Skill

Name: Bring Home From Server
Author: ThomirEL

Bring Home From Server

Pull work back from my home server to this machine and continue locally — the reverse of handover-to-server. Fetches the repo (with server-created branches), the project's configured extra paths and guarded files, Claude memory, and the newest server session transcript so I can resume the conversation here. Use for "bring it back from the server", "pull my server work down", "sync down from the server", "continue on my computer", "come back home from the server".

ThomirEL 6525677 2 files · 5.5 KB Updated Sep 17, 2026

File contents

bring-home-from-server

Where the scripts live. ${SKILLS} below means the skills/ directory this SKILL.md sits in: ${CLAUDE_PLUGIN_ROOT}/skills when installed as the server-handover plugin, or ~/.claude/skills when installed with install.sh. Resolve it once, then run the scripts from there.

The return trip for handover-to-server. Pulls the home server's work back (server → this machine): repo with any branches made there, HANDOVER_SYNC_PATHS, HANDOVER_GUARDED_FILES (usually the reason to come home — that is where the latest state lives), Claude memory, and the newest server session transcript so you can resume the conversation locally.

Driver: ${SKILLS}/bring-home-from-server/bring-home.sh. Run it from inside the project; do not re-derive it. Uses the same server.env + .handover.env as the forward skill (exit 2/3 → run /setup-server).

Run

${SKILLS}/bring-home-from-server/bring-home.sh

Ends by printing how to continue here — the user's interactive step, hand it over:

cd '<launch dir>' && claude --resume <session-id>

Test safely first

Pulls real server content but writes under a scratch prefix:

BRINGHOME_DEST_PREFIX=/tmp/bh-test ${SKILLS}/bring-home-from-server/bring-home.sh
git -C /tmp/bh-test$HOME/repos/<proj> branch
rm -rf /tmp/bh-test

Knobs

HANDOVER_FORCE=1 — overwrite guarded files even if the local copy is newer
BRINGHOME_SKIP_GUARDED=1 — leave guarded files alone
BRINGHOME_DEST_PREFIX=/dir — scratch prefix (testing)
HANDOVER_PROJECT_CONFIG — explicit .handover.env path

Gotchas

Symmetric guard. handover refuses to overwrite a newer server copy; bring-home refuses to overwrite a newer local copy (you worked here since the last sync). Local is always backed up (*.bak-<timestamp>) before an overwrite, and the result is sha256-verified.
Server is canonical on the pull. Repo working tree + .git are overwritten from the server (rsync, no --delete). Commit or stash local work first, otherwise the server's refs win.
"Newest" transcript = most recently modified *.jsonl in the server's project dir, copied into the local slug dir where claude --resume looks. Older server sessions stay on the server. No transcript yet (idle session never used) → it just prints plain claude.
Slugs differ per side (-home-me-repos-x vs -Users-me-repos-x); the driver maps between them.

---name: bring-home-from-serverdescription: Pull work back from my home server to this machine and continue locally — the reverse of handover-to-server. Fetches the repo (with server-created branches), the project's configured extra paths and guarded files, Claude memory, and the newest server session transcript so I can resume the conversation here. Use for "bring it back from the server", "pull my server work down", "sync down from the server", "continue on my computer", "come back home from the server".---# bring-home-from-server> **Where the scripts live.** `${SKILLS}` below means the `skills/` directory this SKILL.md sits in: `${CLAUDE_PLUGIN_ROOT}/skills` when installed as the `server-handover` plugin, or `~/.claude/skills` when installed with `install.sh`. Resolve it once, then run the scripts from there.The return trip for [handover-to-server](../handover-to-server/SKILL.md). Pullsthe home server's work back (server → this machine): repo with any branchesmade there, `HANDOVER_SYNC_PATHS`, `HANDOVER_GUARDED_FILES` (usually the reasonto come home — that is where the latest state lives), Claude memory, and thenewest server session transcript so you can resume the conversation locally.Driver: `${SKILLS}/bring-home-from-server/bring-home.sh`. Run it frominside the project; do not re-derive it. Uses the same `server.env` +`.handover.env` as the forward skill (exit 2/3 → run `/setup-server`).## Run```bash${SKILLS}/bring-home-from-server/bring-home.sh```Ends by printing how to continue here — the user's interactive step, hand it over:```cd '<launch dir>' && claude --resume <session-id>```## Test safely firstPulls real server content but writes under a scratch prefix:```bashBRINGHOME_DEST_PREFIX=/tmp/bh-test ${SKILLS}/bring-home-from-server/bring-home.shgit -C /tmp/bh-test$HOME/repos/<proj> branchrm -rf /tmp/bh-test```## Knobs- `HANDOVER_FORCE=1` — overwrite guarded files even if the local copy is newer- `BRINGHOME_SKIP_GUARDED=1` — leave guarded files alone- `BRINGHOME_DEST_PREFIX=/dir` — scratch prefix (testing)- `HANDOVER_PROJECT_CONFIG` — explicit `.handover.env` path## Gotchas- **Symmetric guard.** handover refuses to overwrite a newer *server* copy; bring-home refuses to overwrite a newer *local* copy (you worked here since the last sync). Local is always backed up (`*.bak-<timestamp>`) before an overwrite, and the result is sha256-verified.- **Server is canonical on the pull.** Repo working tree + `.git` are overwritten from the server (rsync, no `--delete`). Commit or stash local work first, otherwise the server's refs win.- **"Newest" transcript** = most recently modified `*.jsonl` in the server's project dir, copied into the local slug dir where `claude --resume` looks. Older server sessions stay on the server. No transcript yet (idle session never used) → it just prints plain `claude`.- **Slugs differ per side** (`-home-me-repos-x` vs `-Users-me-repos-x`); the driver maps between them.

Frequently asked questions