MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
Create handoff plans for continuing work across sessions. An agent skill from jellydn/my-ai-tools.
Install Handoffs
$ npx skills add jellydn/my-ai-tools --skill handoffs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jellydn/my-ai-tools handoffs --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/handoffs .claude/skills/handoffs && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "handoffs" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/handoffs into .claude/skills/handoffs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "handoffs", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jellydn/my-ai-tools/tree/main/skills/handoffsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jellydn/my-ai-tools --skill handoffs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jellydn/my-ai-tools handoffs --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/handoffs .agents/skills/handoffs && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "handoffs" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/handoffs into .agents/skills/handoffs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "handoffs", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jellydn/my-ai-tools --skill handoffs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jellydn/my-ai-tools handoffs --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/handoffs .cursor/skills/handoffs && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "handoffs" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/handoffs into .cursor/skills/handoffs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "handoffs", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jellydn/my-ai-tools.git --path skills/handoffs--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jellydn/my-ai-tools --skill handoffs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jellydn/my-ai-tools handoffs --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/handoffs .gemini/skills/handoffs && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "handoffs" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/handoffs into .gemini/skills/handoffs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "handoffs", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jellydn/my-ai-tools handoffsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jellydn/my-ai-tools --skill handoffs -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/handoffs .github/skills/handoffs && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "handoffs" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/handoffs into .github/skills/handoffs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "handoffs", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jellydn/my-ai-tools --skill handoffs -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jellydn/my-ai-tools handoffs --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/handoffs .opencode/skills/handoffs && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "handoffs" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/handoffs into .opencode/skills/handoffs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "handoffs", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
handoffs- GitHub stars
- 123
- Token cost
- ~1.4k tokens
- SKILL.md length
- 607 words
- Files
- 1
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create handoff plans for continuing work across sessions. An agent skill from jellydn/my-ai-tools.
- Works in 4 steps: Identify the user's explicit purpose and… → Verify important paths, branch/status,… → Capture only decision-relevant file… → …
- Agent Workflows work in your project
- SKILL.md covers Goal, Process, Output Structure and Final Step
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Handoffs is an agent skill from jellydn/my-ai-tools. Create handoff plans for continuing work across sessions
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: cline, claude, opencode, amp, codex, gemini, cursor, pi
It sits in Agent Workflows. The repository describes itself as: Comprehensive configuration management for AI coding tools - Replicate my complete setup for Claude Code, OpenCode, Amp, Li, Codex and Claude Code Switch with custom… The licence is MIT.
When your agent uses it
- Agent Workflows work in your project
Example prompts
- “/handoffs”
Requirements
- Compatibility (from SKILL.md): cline, claude, opencode, amp, codex, gemini, cursor, pi
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Identify the user's explicit purpose and the current work state.
- Verify important paths, branch/status, recent command results, and unresolved blockers.
- Capture only decision-relevant file names, symbols, short snippets, and links.
- Mark uncertain or stale information explicitly.
What it can do on your machine
Read from SKILL.md and the folder at commit 62c9227. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
cline, claude, opencode, amp, codex, gemini, cursor, pi
From compatibility in the SKILL.md frontmatter.
Context cost
Handoffs loads about 1.4k tokens when it runs. Until then it costs about 16 tokens; SKILL.md has 607 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jellydn/my-ai-tools at commit 62c9227, republished under its MIT licence (© jellydn). 607 words, ~1,354 tokens.
Download SKILL.mdSave it as
.claude/skills/handoffs/SKILL.md (or your agent's skills folder).- name
- handoffs
- description
- Create handoff plans for continuing work across sessions
- compatibility
- cline, claude, opencode, amp, codex, gemini, cursor, pi
- license
- MIT
- hint
- Use when ending a session and want to continue work later with full context
- user-invocable
- true
- metadata.audience
- all
- metadata.workflow
- workflow
Session Handoff Plan
Creates a detailed handoff plan of the conversation for continuing the work in a new session.
The user specified purpose:
<purpose>$ARGUMENTS</purpose>
You are creating a summary specifically so that it can be continued by another agent. For this to work you MUST have a purpose. If no specified purpose was provided in the <purpose>...</purpose> tag you must STOP IMMEDIATELY and ask the user what the purpose is.
Do not continue before asking for the purpose as you will otherwise not understand the instructions and do not assume a purpose!
Goal
Create a detailed summary of the conversation so far, paying close attention to the user's explicit purpose for the next steps. This handoff plan should be thorough in capturing technical details, code patterns, and architectural decisions that will be essential for continuing development work without losing context.
Process
Before providing the final handoff, produce a concise evidence-based summary for the user. Do not expose private chain-of-thought or <analysis> tags. Include decisions, current state, blockers, and the exact next action instead of a chronological transcript or full code dumps.
- Identify the user's explicit purpose and the current work state.
- Verify important paths, branch/status, recent command results, and unresolved blockers.
- Capture only decision-relevant file names, symbols, short snippets, and links.
- Mark uncertain or stale information explicitly.
Your plan should include the following sections:
- Primary Request and Intent: Capture all of the user's explicit requests and intents in detail
- Key Technical Concepts: List all important technical concepts, technologies, and frameworks discussed.
- Files and Code Sections: Enumerate specific files and code sections examined, modified, or created. Pay special attention to the most recent messages and include full code snippets where applicable and include a summary of why this file read or edit is important.
- Problem Solving: Document problems solved and any ongoing troubleshooting efforts.
- Pending Tasks: Outline any pending tasks that you have explicitly been asked to work on.
- Current Work: Describe in detail precisely what was being worked on immediately before this handoff request, paying special attention to the most recent messages from both user and assistant. Include file names and code snippets where applicable.
- Next Step: List the next step that you will take that is related to the most recent work you were doing. IMPORTANT: ensure that this step is DIRECTLY in line with the user's explicit requests, and the task you were working on immediately before this handoff request. If your last task was concluded, then only list next steps if they are explicitly in line with the users request. Do not start on tangential requests without confirming with the user first. Include this section only if there is an actionable next step.
Show full SKILL.md (150 more words)Show less
Additionally create a "slug" for this handoff. The "slug" is how we will refer to it later in a few places. Examples:
- current-user-api-handler
- implement-auth
- fix-issue-42
Together with the slug create a "Readable Summary". Examples:
- Implement Current User API Handler
- Implement Authentication
- Fix Issue #42
Output Structure
The handoff file should contain the structured summary below. Do not include private chain-of-thought or a chronological transcript.
# Session Handoff Plan
## 1. Primary Request and Intent
[Detailed description of all user requests and intents]
## 2. Key Technical Concepts
- [Concept 1]
- [Concept 2]
- [...]
## 3. Files and Code Sections
### [File Name 1]
- **Why important**: [Summary of why this file is important]
- **Changes made**: [Summary of the changes made to this file, if any]
- **Code snippet**:
\`\`\`language
[Important Code Snippet]
\`\`\`
### [File Name 2]
- **Code snippet**:
\`\`\`language
[Important Code Snippet]
\`\`\`
[...]
## 4. Problem Solving
[Description of solved problems and ongoing troubleshooting]
## 5. Pending Tasks
- [Task 1 that you have been explicitly asked to work on]
- [Task 2 that you have been explicitly asked to work on]
- [...]
## 6. Current Work
[Detailed description of what was being worked on immediately before this handoff, including file names and code snippets]
## 7. Next Step
[Next step to take, directly aligned with user's explicit handoff purpose. Only include if there is an actionable next step.]Final Step
After providing your analysis and summary:
- Ensure the
.planning/handoffs/directory exists (create it if needed) - Write the handoff summary to a markdown file at
.planning/handoffs/[timestamp]-[slug].mdwhere [timestamp] is the current date in format YYYY-MM-DD and the slug is what we defined before - Read the handoff file back and verify it contains the purpose, current state, verification, blockers, and next action.
- Tell the user about this file and that they can use
/pickup $1to continue where $1 is the filename
© jellydn, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/handoffs of jellydn/my-ai-tools.
Open the folder on GitHubat commit 62c9227
Compare with similar skills
Handoffs next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Handoffs this skilljellydn/my-ai-tools | 123 | — | ~1.4k | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 63 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 38k | 10 repos | ~4.1k | Automated safety check: Notes | Apache-2.0 | |
| Using Superpowersfarm-fe/farm | 5.6k | 35 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Executing Plans Inlineobra/superpowers | 297k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Skill CreatorAzure/azqr | 795 | 89 repos | ~8.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
- Official
Hook Development for Claude Code Plugins
anthropics/claude-plugins-official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
Using Superpowers
farm-fe/farm
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Executing Plans Inline
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
- Official
Skill Creator
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
- Official
Claude Code Agent Development
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
More from jellydn/my-ai-tools
All 33 skills in this repoBabysit PR
jellydn/my-ai-tools
A skill your agent uses when monitoring an open GitHub PR for CI failures, review feedback, mergeability, and safe retries or fixes.
Visual PR
jellydn/my-ai-tools
Posts a concise visual outline as a GitHub pull request comment.
Qmd Knowledge
jellydn/my-ai-tools
Manage project knowledge with qmd — captures learnings, decisions, and conventions
Prd
jellydn/my-ai-tools
Generate Product Requirements Documents from feature ideas — plans specs and requirements
Capability Experiments
jellydn/my-ai-tools
Build an interactive report or experiment when the user asks to explore model capabilities.
PR Review
jellydn/my-ai-tools
Fix PR review comments by implementing requested changes. An agent skill from jellydn/my-ai-tools.
Related
Categories
Questions about Handoffs
What does Handoffs do?
Create handoff plans for continuing work across sessions. An agent skill from jellydn/my-ai-tools. Handoffs is an agent skill from jellydn/my-ai-tools.
When should I use Handoffs?
Handoffs fits situations like: agent Workflows work in your project.
How do I install Handoffs in Claude Code?
Run `npx skills add jellydn/my-ai-tools --skill handoffs -a claude-code`. Or copy the skill folder (skills/handoffs in jellydn/my-ai-tools) into .claude/skills/handoffs in your project. Claude Code loads it when a task matches its description.
How do I install Handoffs in Codex?
Run `npx skills add jellydn/my-ai-tools --skill handoffs -a codex`. Or copy the skill folder (skills/handoffs in jellydn/my-ai-tools) into .agents/skills/handoffs in your project. Codex loads it when a task matches its description.
Can I use Handoffs in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jellydn/my-ai-tools --skill handoffs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/handoffs, .gemini/skills/handoffs, .github/skills/handoffs and .opencode/skills/handoffs in your project.
What does Handoffs need to run?
SKILL.md names no scripts, command-line tools or credentials: Handoffs is instructions for the agent only. Compatibility (from SKILL.md): cline, claude, opencode, amp, codex, gemini, cursor, pi.
Does Handoffs access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Handoffs safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Handoffs use?
Handoffs is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Handoffs use?
About 1.4k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Handoffs?
Skills that share tags, products or a category with Handoffs: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Handoffs?
jellydn (a GitHub user) maintains it in jellydn/my-ai-tools, which has 123 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 9, 2026.
Source: jellydn/my-ai-tools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.