{ "id": "handoff-note", "slug": "handoff-note", "name": "Handoff Note", "tagline": "Work that survives every handoff.", "description": "A compact handoff with the goal, what's done, where everything is, decisions, open questions and the next step, for another bot, a person or its own future self.", "category": "For bots", "platforms": [ "Grok Bot", "Muse", "Dots" ], "schedule": "On demand", "outputType": "note", "previewImage": "previews/handoff-note.png", "installSteps": { "grokBot": { "label": "Grok Bot", "status": "verified", "steps": [ "Copy skills/handoff-note/SKILL.md (the whole file, including the --- header).", "Open a one-to-one chat with your Grok Bot and paste the prompt below, with the file where it says.", "Try it once now: \"Run Handoff Note.\"" ], "prompt": "Save the following as a skill called \"Handoff Note\". No routine needed: apply it automatically whenever you pass work to another bot, to a person, or to your future self. Before the first run, ask me the setup questions in the skill and remember my answers.\n\n", "note": "Skills and routines are saved by asking the Bot; no settings to dig through.", "promptFull": "Save the following as a skill called \"Handoff Note\". No routine needed: apply it automatically whenever you pass work to another bot, to a person, or to your future self. Before the first run, ask me the setup questions in the skill and remember my answers.\n\n---\nname: handoff-note\ndescription: Use when a bot passes work to another bot, to a person, or to its own future self (before a long pause, a context reset, or the end of a session). Writes a compact handoff with the goal, what's done, where everything is, decisions made, open questions, and the very next step, so the receiver can continue without re-asking anything.\nmetadata:\n id: handoff-note\n version: \"1.0.0\"\n author: BotPlaza\n---\n\n# Handoff Note\n\n## What it does\n\nThe note that makes work survive a handoff. It captures exactly what the next bot (or person, or your own future self after a memory reset) needs to continue: the goal, what's done, where the files are, what was decided and why, what's still open, and the single next action. Nothing gets re-asked and nothing gets lost.\n\n## When to use\n\n- Handing a task to a teammate bot, ending a long session, before a scheduled pause, or when the context is about to be summarized.\n\n## Requires\n\nNothing. It works with any chat, file, or bot-to-bot message.\n\n## Schedule\n\nOn demand, at every handoff.\n\n## Inputs\n\n| Setting | Default | Notes |\n|---|---|---|\n| `receiver` | required | A bot, a person, or \"future me\". |\n| `length` | under 200 words | Longer only for complex work. |\n| `include_facts` | only the receiver's scope | See Fact Scope Guard. |\n\n## Steps\n\n1. **Goal** in one sentence, in the person's own words if possible.\n2. **Done:** what's finished, with links.\n3. **Where things are:** file paths, docs, URLs, and IDs.\n4. **Decisions:** what was decided, by whom, and why (one line each).\n5. **Open:** questions waiting on the person, and blockers.\n6. **Next step:** the single next action, specific enough to start right away.\n7. **Check:** could the receiver continue with only this note? If not, add what's missing.\n\n## Output format\n\n```markdown\n**HANDOFF \u2192 {receiver} \u00b7 {date, time, zone}**\n**Goal:** {one sentence}\n**Done:** {items, with links}\n**Where:** {paths, links}\n**Decided:** {decision}, by {who}, because {why}\n**Open:** {question}, waiting on {who}\n**Next:** {one concrete action}\n```\n\n## Edge cases\n\n- **The receiver is a person:** drop internal paths they can't open and use links instead.\n- **The work is half-done:** say exactly where it stopped, for example \"filled through page 3 of 5; nothing submitted\".\n\n## Boundaries\n\n- Never include passwords, codes, or card numbers.\n- A handoff passes information, not permission. Approvals still come from the person." }, "muse": { "label": "Muse", "status": "partially-verified", "steps": [ "Copy skills/handoff-note/SKILL.md.", "Open Muse and paste the prompt below with the file where it says.", "Try it: \"Run Handoff Note.\" Muse has no skill install for outside skills, so it follows the pasted instructions.", "Muse Code (developer CLI): unzip downloads/handoff-note.zip, run `muse skills validate ./handoff-note` then `muse skills install ./handoff-note --scope user`. Optional: add the BotPlaza connector (https://botplaza.lol/api/mcp) under mcpServers in ~/.config/muse/settings.json." ], "sourceUrl": "https://www.meta.com/help/superintelligence/1484325780075655/", "note": "Recurring tasks and Muse Code skill install are documented by Meta. Installing outside skills in the Muse app is not.", "prompt": "Here are instructions for a task called \"Handoff Note\". Follow them whenever I say \"Run Handoff Note\". Ask me the setup questions first and remember my answers.\n\n\n\nIf you can save this as a skill, please do.", "promptFull": "Here are instructions for a task called \"Handoff Note\". Follow them whenever I say \"Run Handoff Note\". Ask me the setup questions first and remember my answers.\n\n---\nname: handoff-note\ndescription: Use when a bot passes work to another bot, to a person, or to its own future self (before a long pause, a context reset, or the end of a session). Writes a compact handoff with the goal, what's done, where everything is, decisions made, open questions, and the very next step, so the receiver can continue without re-asking anything.\nmetadata:\n id: handoff-note\n version: \"1.0.0\"\n author: BotPlaza\n---\n\n# Handoff Note\n\n## What it does\n\nThe note that makes work survive a handoff. It captures exactly what the next bot (or person, or your own future self after a memory reset) needs to continue: the goal, what's done, where the files are, what was decided and why, what's still open, and the single next action. Nothing gets re-asked and nothing gets lost.\n\n## When to use\n\n- Handing a task to a teammate bot, ending a long session, before a scheduled pause, or when the context is about to be summarized.\n\n## Requires\n\nNothing. It works with any chat, file, or bot-to-bot message.\n\n## Schedule\n\nOn demand, at every handoff.\n\n## Inputs\n\n| Setting | Default | Notes |\n|---|---|---|\n| `receiver` | required | A bot, a person, or \"future me\". |\n| `length` | under 200 words | Longer only for complex work. |\n| `include_facts` | only the receiver's scope | See Fact Scope Guard. |\n\n## Steps\n\n1. **Goal** in one sentence, in the person's own words if possible.\n2. **Done:** what's finished, with links.\n3. **Where things are:** file paths, docs, URLs, and IDs.\n4. **Decisions:** what was decided, by whom, and why (one line each).\n5. **Open:** questions waiting on the person, and blockers.\n6. **Next step:** the single next action, specific enough to start right away.\n7. **Check:** could the receiver continue with only this note? If not, add what's missing.\n\n## Output format\n\n```markdown\n**HANDOFF \u2192 {receiver} \u00b7 {date, time, zone}**\n**Goal:** {one sentence}\n**Done:** {items, with links}\n**Where:** {paths, links}\n**Decided:** {decision}, by {who}, because {why}\n**Open:** {question}, waiting on {who}\n**Next:** {one concrete action}\n```\n\n## Edge cases\n\n- **The receiver is a person:** drop internal paths they can't open and use links instead.\n- **The work is half-done:** say exactly where it stopped, for example \"filled through page 3 of 5; nothing submitted\".\n\n## Boundaries\n\n- Never include passwords, codes, or card numbers.\n- A handoff passes information, not permission. Approvals still come from the person.\n\nIf you can save this as a skill, please do." }, "dots": { "label": "Dots", "status": "partially-verified", "steps": [ "Copy skills/handoff-note/SKILL.md.", "Paste the prompt below into your dot's conversation in ChatGPT, with the file where it says.", "Optional: in ChatGPT, Plugins > + > Add custom MCP server with https://botplaza.lol/api/mcp (no authentication). Dots can use installed plugins, but OpenAI hasn't said whether that includes custom ones.", "Business, Enterprise, Healthcare and Edu workspaces can also upload downloads/handoff-note.zip under Plugins > Skills > Create > Upload from your computer." ], "sourceUrl": "https://learn.chatgpt.com/docs/dots", "note": "Dots are available on ChatGPT Pro, Business Premium and Enterprise, and are still rolling out. Pasting instructions in and scheduled check-ins are documented.", "prompt": "Here are instructions for a task called \"Handoff Note\". Take this on as an ongoing responsibility and follow them whenever I say \"Run Handoff Note\". Ask me the setup questions first and remember my answers.\n\n", "promptFull": "Here are instructions for a task called \"Handoff Note\". Take this on as an ongoing responsibility and follow them whenever I say \"Run Handoff Note\". Ask me the setup questions first and remember my answers.\n\n---\nname: handoff-note\ndescription: Use when a bot passes work to another bot, to a person, or to its own future self (before a long pause, a context reset, or the end of a session). Writes a compact handoff with the goal, what's done, where everything is, decisions made, open questions, and the very next step, so the receiver can continue without re-asking anything.\nmetadata:\n id: handoff-note\n version: \"1.0.0\"\n author: BotPlaza\n---\n\n# Handoff Note\n\n## What it does\n\nThe note that makes work survive a handoff. It captures exactly what the next bot (or person, or your own future self after a memory reset) needs to continue: the goal, what's done, where the files are, what was decided and why, what's still open, and the single next action. Nothing gets re-asked and nothing gets lost.\n\n## When to use\n\n- Handing a task to a teammate bot, ending a long session, before a scheduled pause, or when the context is about to be summarized.\n\n## Requires\n\nNothing. It works with any chat, file, or bot-to-bot message.\n\n## Schedule\n\nOn demand, at every handoff.\n\n## Inputs\n\n| Setting | Default | Notes |\n|---|---|---|\n| `receiver` | required | A bot, a person, or \"future me\". |\n| `length` | under 200 words | Longer only for complex work. |\n| `include_facts` | only the receiver's scope | See Fact Scope Guard. |\n\n## Steps\n\n1. **Goal** in one sentence, in the person's own words if possible.\n2. **Done:** what's finished, with links.\n3. **Where things are:** file paths, docs, URLs, and IDs.\n4. **Decisions:** what was decided, by whom, and why (one line each).\n5. **Open:** questions waiting on the person, and blockers.\n6. **Next step:** the single next action, specific enough to start right away.\n7. **Check:** could the receiver continue with only this note? If not, add what's missing.\n\n## Output format\n\n```markdown\n**HANDOFF \u2192 {receiver} \u00b7 {date, time, zone}**\n**Goal:** {one sentence}\n**Done:** {items, with links}\n**Where:** {paths, links}\n**Decided:** {decision}, by {who}, because {why}\n**Open:** {question}, waiting on {who}\n**Next:** {one concrete action}\n```\n\n## Edge cases\n\n- **The receiver is a person:** drop internal paths they can't open and use links instead.\n- **The work is half-done:** say exactly where it stopped, for example \"filled through page 3 of 5; nothing submitted\".\n\n## Boundaries\n\n- Never include passwords, codes, or card numbers.\n- A handoff passes information, not permission. Approvals still come from the person." }, "chatgpt": { "label": "ChatGPT", "status": "unverified", "verified": false, "steps": [ "Download https://botplaza.lol/downloads/handoff-note.zip (don't unzip).", "ChatGPT sidebar \u2192 Plugins \u2192 Skills tab \u2192 Create \u2192 Upload from your computer.", "Wait for the scan; if it says Needs Review, read it and approve.", "Use it with @handoff-note or just ask." ], "sourceUrl": "https://help.openai.com/en/articles/20001066-skills-in-chatgpt", "note": "Business, Enterprise, Edu and Healthcare plans only. Other plans fall back to pasting the prompt.", "prompt": "Here are instructions for a task called \"Handoff Note\". Follow them whenever I say \"Run Handoff Note\". Ask me the setup questions first and remember my answers.\n\n", "promptFull": "Here are instructions for a task called \"Handoff Note\". Follow them whenever I say \"Run Handoff Note\". Ask me the setup questions first and remember my answers.\n\n---\nname: handoff-note\ndescription: Use when a bot passes work to another bot, to a person, or to its own future self (before a long pause, a context reset, or the end of a session). Writes a compact handoff with the goal, what's done, where everything is, decisions made, open questions, and the very next step, so the receiver can continue without re-asking anything.\nmetadata:\n id: handoff-note\n version: \"1.0.0\"\n author: BotPlaza\n---\n\n# Handoff Note\n\n## What it does\n\nThe note that makes work survive a handoff. It captures exactly what the next bot (or person, or your own future self after a memory reset) needs to continue: the goal, what's done, where the files are, what was decided and why, what's still open, and the single next action. Nothing gets re-asked and nothing gets lost.\n\n## When to use\n\n- Handing a task to a teammate bot, ending a long session, before a scheduled pause, or when the context is about to be summarized.\n\n## Requires\n\nNothing. It works with any chat, file, or bot-to-bot message.\n\n## Schedule\n\nOn demand, at every handoff.\n\n## Inputs\n\n| Setting | Default | Notes |\n|---|---|---|\n| `receiver` | required | A bot, a person, or \"future me\". |\n| `length` | under 200 words | Longer only for complex work. |\n| `include_facts` | only the receiver's scope | See Fact Scope Guard. |\n\n## Steps\n\n1. **Goal** in one sentence, in the person's own words if possible.\n2. **Done:** what's finished, with links.\n3. **Where things are:** file paths, docs, URLs, and IDs.\n4. **Decisions:** what was decided, by whom, and why (one line each).\n5. **Open:** questions waiting on the person, and blockers.\n6. **Next step:** the single next action, specific enough to start right away.\n7. **Check:** could the receiver continue with only this note? If not, add what's missing.\n\n## Output format\n\n```markdown\n**HANDOFF \u2192 {receiver} \u00b7 {date, time, zone}**\n**Goal:** {one sentence}\n**Done:** {items, with links}\n**Where:** {paths, links}\n**Decided:** {decision}, by {who}, because {why}\n**Open:** {question}, waiting on {who}\n**Next:** {one concrete action}\n```\n\n## Edge cases\n\n- **The receiver is a person:** drop internal paths they can't open and use links instead.\n- **The work is half-done:** say exactly where it stopped, for example \"filled through page 3 of 5; nothing submitted\".\n\n## Boundaries\n\n- Never include passwords, codes, or card numbers.\n- A handoff passes information, not permission. Approvals still come from the person." }, "gemini": { "label": "Gemini", "status": "unverified", "verified": false, "steps": [ "gemini.google.com \u2192 Customize \u2192 Skills \u2192 Create \u2192 Upload \u2192 pick the SKILL.md at https://botplaza.lol/skills/handoff-note.md (or https://botplaza.lol/downloads/handoff-note.zip).", "Review, then Create.", "Use it with /handoff-note." ], "sourceUrl": "https://support.google.com/gemini/answer/17094296", "note": "Personal accounts 18+. Workspace users must recreate the skill in Workspace Studio.", "prompt": "Here are instructions for a task called \"Handoff Note\". Follow them whenever I say \"Run Handoff Note\". Ask me the setup questions first and remember my answers.\n\n", "promptFull": "Here are instructions for a task called \"Handoff Note\". Follow them whenever I say \"Run Handoff Note\". Ask me the setup questions first and remember my answers.\n\n---\nname: handoff-note\ndescription: Use when a bot passes work to another bot, to a person, or to its own future self (before a long pause, a context reset, or the end of a session). Writes a compact handoff with the goal, what's done, where everything is, decisions made, open questions, and the very next step, so the receiver can continue without re-asking anything.\nmetadata:\n id: handoff-note\n version: \"1.0.0\"\n author: BotPlaza\n---\n\n# Handoff Note\n\n## What it does\n\nThe note that makes work survive a handoff. It captures exactly what the next bot (or person, or your own future self after a memory reset) needs to continue: the goal, what's done, where the files are, what was decided and why, what's still open, and the single next action. Nothing gets re-asked and nothing gets lost.\n\n## When to use\n\n- Handing a task to a teammate bot, ending a long session, before a scheduled pause, or when the context is about to be summarized.\n\n## Requires\n\nNothing. It works with any chat, file, or bot-to-bot message.\n\n## Schedule\n\nOn demand, at every handoff.\n\n## Inputs\n\n| Setting | Default | Notes |\n|---|---|---|\n| `receiver` | required | A bot, a person, or \"future me\". |\n| `length` | under 200 words | Longer only for complex work. |\n| `include_facts` | only the receiver's scope | See Fact Scope Guard. |\n\n## Steps\n\n1. **Goal** in one sentence, in the person's own words if possible.\n2. **Done:** what's finished, with links.\n3. **Where things are:** file paths, docs, URLs, and IDs.\n4. **Decisions:** what was decided, by whom, and why (one line each).\n5. **Open:** questions waiting on the person, and blockers.\n6. **Next step:** the single next action, specific enough to start right away.\n7. **Check:** could the receiver continue with only this note? If not, add what's missing.\n\n## Output format\n\n```markdown\n**HANDOFF \u2192 {receiver} \u00b7 {date, time, zone}**\n**Goal:** {one sentence}\n**Done:** {items, with links}\n**Where:** {paths, links}\n**Decided:** {decision}, by {who}, because {why}\n**Open:** {question}, waiting on {who}\n**Next:** {one concrete action}\n```\n\n## Edge cases\n\n- **The receiver is a person:** drop internal paths they can't open and use links instead.\n- **The work is half-done:** say exactly where it stopped, for example \"filled through page 3 of 5; nothing submitted\".\n\n## Boundaries\n\n- Never include passwords, codes, or card numbers.\n- A handoff passes information, not permission. Approvals still come from the person." }, "cli": { "label": "Skills CLI", "status": "verified", "steps": [ "All agents: `npx skills add https://botplaza.lol --skill handoff-note` (add `-a claude-code`, `-a codex`, or `-a cursor` to choose one).", "Claude Code marketplace: `/plugin marketplace add https://botplaza.lol/.claude-plugin/marketplace.json` then `/plugin install handoff-note@botplaza`.", "Fallback, Claude Code: `curl -fsSL https://botplaza.lol/downloads/handoff-note.zip -o s.zip && unzip s.zip -d ~/.claude/skills/`.", "Fallback, Codex and other .agents readers: `curl -fsSL https://botplaza.lol/downloads/handoff-note.zip -o s.zip && unzip s.zip -d ~/.agents/skills/`.", "Fallback, Cursor project: `curl -fsSL https://botplaza.lol/downloads/handoff-note.zip -o s.zip && unzip s.zip -d .cursor/skills/`." ], "sourceUrl": "https://www.skills.sh/docs", "note": "The skills CLI reads /.well-known/agent-skills/index.json and installs each SKILL.md. The zip fallback uses the existing downloads/.zip folder layout.", "prompt": "npx skills add https://botplaza.lol --skill handoff-note", "promptFull": "npx skills add https://botplaza.lol --skill handoff-note" } }, "author": "BotPlaza", "tags": [ "handoff", "multi-agent", "continuity", "context" ], "featured": false, "longDescription": "Handoff Note captures exactly what the receiver needs to continue without re-asking: goal, progress, locations, decisions with reasons, open questions and one concrete next action. It's for bot-to-bot handoffs, end-of-session notes and context resets.", "customization": [ { "key": "length", "label": "Length", "type": "select", "question": "How long should notes be?", "default": "Under 200 words", "options": [ "Under 100 words", "Under 200 words", "As needed" ] } ], "whatYouGet": [ "Goal, done, where, decided, open, next", "Nothing re-asked", "No secrets in the note" ], "dataSources": [], "setupTime": "None", "sampleOutput": "samples/handoff-note.md", "skillFile": "skills/handoff-note/SKILL.md", "version": "1.0.0", "license": "", "previewAlt": "A compact handoff card with lines for goal, done, where, decided, open and next.", "writesOrSends": "Messages the receiver only.", "audience": "bots", "setup": [ { "key": "length", "question": "How long should notes be?", "type": "select", "default": "Under 200 words", "options": [ "Under 100 words", "Under 200 words", "As needed" ] } ], "safety": { "dataAccess": [ "The current task's context only" ], "writesOrSends": "Messages the receiver only.", "estCost": "Very low: one short note per handoff.", "costLevel": "medium", "warnings": [ "A handoff is not approval: the receiving bot still asks you before sending or submitting anything." ] }, "checked": { "instructionOnly": true, "scripts": false, "runtimeFetch": false, "sha256": "f533d93c94c2da9d422820d2f6fd99d0efcbffa212e79c4983b44d4ab02aa295", "checkedOn": "2026-10-31" }, "urls": { "page": "https://botplaza.lol/skills/handoff-note/", "markdown": "https://botplaza.lol/skills/handoff-note.md", "skillMd": "https://botplaza.lol/skills/handoff-note/SKILL.md", "json": "https://botplaza.lol/skills/handoff-note.json", "zip": "https://botplaza.lol/downloads/handoff-note.zip", "mcp": "https://botplaza.lol/api/mcp" } }