handoff
Skill1 starsChanged yesterdayMITView on GitHub
Save, load, or merge AI coding session context (\"handoff\", \"lanjut handoff\", \"load handoff\") via shadow_handoff MCP. Use when context memory is full or switching/merging agent sessions. Do NOT use for client BAST project delivery (/shadow-handover).
191 other projects use a version of this.
Adopted by
Most recently taken up by
- lhotwll217/owner-operatortheir own version, first seen Nov 16, 2026
- tanishq286/tq-forgetheir own version, first seen Nov 15, 2026
- niki914/zafirotheir own version, first seen Nov 15, 2026
- davidondrej/skillstheir own version, first seen Nov 15, 2026
- quickchatai/quickreviewtheir own version, first seen Nov 15, 2026
- HiteSit/real-scientist-skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use decision-mapping, setup-ts-deep-modules and 10 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.
FabienDehopreSkilldecision-mapping
Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.
Also in 8 projects that use this
liufeng1976Skillsetup-ts-deep-modules
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.
Also in 42 projects that use this
AWSSkillto-questionnaire
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
Also in 93 projects that use this
GoogleSkillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Also in 87 projects that use this
RoentekSkillloop-me
Grill me about specs for the workflows I want to build, within this workspace.
Also in 51 projects that use this
LesaniSkillwriting-beats
Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.
Also in 54 projects that use this
Other versions191 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 191
- mattpocock/skills★ 325ksame name
- QuivrHQ/quivr★ 40ksame name
- The-Vibe-Company/quivr★ 40ksame name
- GreyDGL/PentestGPT★ 16ksame name
- ykdojo/claude-code-tips★ 10ksame name
- ArcReel/ArcReel★ 6.6ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.8ksame name
- withcoral/coral★ 5ksame name
- epicenter-md/epicenter★ 4.8ksame name
- EpicenterHQ/epicenter★ 4.8ksame name
181 more not listed
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.
In this repository51 other files it gives its agents.
- antislop-codeSkill
- antislop-copywritingSkill
- antislop-humanSkill
- antislop-layoutmobileSkill
- antislopSkill
- antislop-uiSkill
- context7Skill
- shadow-accessibilitySkill
- shadow-apiSkill
- shadow-architectSkill
- shadow-authSkill
- shadow-bootstrapSkill
- shadow-browserSkill
- shadow-cacheSkill
- shadow-compatSkill
- shadow-concurrencySkill
- shadow-dataSkill
- shadow-dbSkill
- shadow-debugSkill
- shadow-designSkill
- shadow-discoverySkill
- shadow-docSkill
- shadow-domainSkill
- shadow-eaSkill
- shadow-evalSkill
- shadow-finopsSkill
- shadow-gitSkill
- shadow-grcSkill
- shadow-handoverSkill
- shadow-integrateSkill
- shadow-maintainSkill
- shadow-mobileSkill
- shadow-modernizeSkill
- shadow-monarchSkill
- shadow-observeSkill
- shadow-opsSkill
- shadow-perfSkill
- shadow-planSkill
- shadow-pmoSkill
- shadow-presalesSkill
- shadow-privacySkill
- shadow-qualitySkill
- shadow-realtimeSkill
- shadow-refactorSkill
- shadow-releaseSkill
- shadow-resilienceSkill
- shadow-searchSkill
- shadow-secSkill
- shadow-supplychainSkill
- shadow-testSkill
- shadow-uatSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 172 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill whenever the Monarch invokes /handoff (or says "handoff" / "lanjut handoff" / "gabung handoff").
- Very specific: line 33
If the result contains unmergedSessions, the snapshot shows only one parallel session.
- Very specific: line 38
Call list_handoffs with projectPath to see saved sessions, then merge_handoffs with sessionLabels in execution order (e.g.
- Very specific: line 44
Call list_handoffs on the shadow_handoff MCP server and display the saved snapshots and any unmerged sessions.
“Common” is measured: kept by at least 6 in 10 of the 172 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.
Files
/handoff — Cross-Agent Session Handoff (Shadow Army)
Use this skill whenever the Monarch invokes /handoff (or says "handoff" / "lanjut handoff" / "gabung handoff").
This skill connects directly to the shadow_handoff MCP server (save_handoff, load_handoff, list_handoffs, merge_handoffs).
How to Execute
- Default (
/handoffwith no arguments, or/handoff save) — Save & Compact Current Session:- Immediately call the
save_handofftool on theshadow_handoffMCP server (d:/Ridhuan Ngoding Moment/SKILL/mcp-servers/shadow-handoff-mcp/index.mjsif MCP is not yet reloaded in the current window) with:projectPath: the active workspace directory pathsourceAgent: current agent name (Antigravity,Claude Code,Codex, orGemini CLI)title: short milestone titlecurrentGoal: the Monarch's active objectivecompletedWork: concise bullet list of verified completed tasksnextSteps: ordered, actionable next steps for the next sessionkeyDecisionsAndContracts: verified contracts, strict types, and architectural decisionsblockersOrBugs: any open bugs or blockersimportantFiles: key file paths to inspect firstreadinessLevel(required):PLANNED(plan only) |IMPLEMENTED|VERIFIED-LOCAL|REVIEWED|READY-TO-MERGE, per the Rigor Protocol inshadow-monarch. Pick the level the evidence supports, not the one hoped for.untestedSurfaces(required): surfaces not yet tested (e.g. "real multi-turn conversation", "topic switch", "ALL-CAPS input", "UI during streaming"). Send[]only if every surface was actually tested.claimEvidenceMap: for each readiness claim,{ claim, evidence, notMeasured }.sessionLabel: set when another session works on the same project in parallel (e.g.plan,review), so neither overwrites the other.
- Report the saved handoff ID, readiness level, and file path concisely to the Monarch. If the result contains
mergeHint, tell the Monarch that parallel sessions exist and offer/handoff merge.
- Immediately call the
- Resume (
/handoff load,/handoff lanjut, or"lanjut handoff") — Load Latest Handoff:- Immediately call the
load_handofftool on theshadow_handoffMCP server for the currentprojectPath(or globally if no project is open). - Read
untestedSurfacesandreadinessLevelbefore writing any review conclusion or readiness claim. Treat listed surfaces as unverified; do not upgrade the readiness level without new evidence. - If the result contains
unmergedSessions, the snapshot shows only one parallel session. Tell the Monarch and offer/handoff mergebefore continuing. - Present a brief 3-bullet summary of the loaded state to the Monarch and immediately proceed with Step 1 of
nextSteps.
- Immediately call the
- Merge (
/handoff mergeor"gabung handoff") — Combine Parallel Sessions Into One Agent:- Typical case: session A saved with
sessionLabel: "plan", session B withsessionLabel: "review"; the Monarch wants one agent to continue. - Call
list_handoffswithprojectPathto see savedsessions, thenmerge_handoffswithsessionLabelsin execution order (e.g.["plan", "review"]). - The merge keeps the lowest readiness level, unions untested surfaces, tags every item with its source session, and moves merged sessions to
sessions/archive/(nothing is deleted). - Decisions from different sessions are listed side by side, not reconciled. Report every entry in
warnings(different branches/commits, sessions >24h apart, possible contradictions) to the Monarch before acting on the merged steps. - Then proceed as in Resume.
- Typical case: session A saved with
- History (
/handoff list):- Call
list_handoffson theshadow_handoffMCP server and display the saved snapshots and any unmergedsessions.
- Call
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.

