How do I install the Handoff List skill?

Run npx skillmds@latest add danielsitek/handoff-list 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 Handoff List 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 Handoff List?

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 Handoff List free to use?

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

Who published Handoff List?

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

Handoff List by danielsitek — Agent Skill

Name: Handoff List
Author: danielsitek

Handoff List

List all saved handoff files in .handoffs/ with their summaries so the user can see what tasks they have parked. Use this skill whenever the user wants an overview of their handoffs — phrases like "list handoffs", "what handoffs do I have", "show my parked tasks", "what did I stash", "vypiš handoffy". Trigger whenever the user wants to know what is waiting in the handoff queue, even without the exact word "list".

danielsitek f9e407a 2.1 KB Updated Sep 17, 2026

File contents

Handoff: List

Give the user a quick, scannable overview of every handoff they have parked, so they can decide what to pick up next.

Step 1 — Find the handoffs

Look in .handoffs/ in the project root for files named handoff-NNNN.md.

If the directory does not exist or is empty, tell the user there are no saved handoffs yet and mention they can create one with handoff-create. Stop there.

Step 2 — Read each handoff's summary

For every file, read the frontmatter (handoff, title, created) and the <handoff-summary> block. The summary is written to be self-contained — that is the part the user wants to see.

If a file's frontmatter or summary cannot be parsed, mark it with ⚠ malformed and continue listing the rest.

Step 3 — Present the overview

Show the handoffs ordered by number. For each one, give the number, title, created date, and the summary in the user's own language if they are not writing in English. (Handoff files are stored in English; translate summaries into the user's language for display only.) A compact table works well when there are several:

#	Title	Created	Summary
0001	Add rate limiting to the API	2026-05-12
0002	Migrate config to TypeScript	2026-05-18

If there are only one or two handoffs, a short prose description of each reads better than a table — use judgment.

Close by reminding the user they can dive into one with handoff-invoke <number> or clear a finished one with handoff-close <number>.

---name: handoff-listdescription: List all saved handoff files in .handoffs/ with their summaries so the user can see what tasks they have parked. Use this skill whenever the user wants an overview of their handoffs — phrases like "list handoffs", "what handoffs do I have", "show my parked tasks", "what did I stash", "vypiš handoffy". Trigger whenever the user wants to know what is waiting in the handoff queue, even without the exact word "list".---# Handoff: ListGive the user a quick, scannable overview of every handoff they have parked, sothey can decide what to pick up next.## Step 1 — Find the handoffsLook in `.handoffs/` in the project root for files named `handoff-NNNN.md`.If the directory does not exist or is empty, tell the user there are no savedhandoffs yet and mention they can create one with `handoff-create`. Stop there.## Step 2 — Read each handoff's summaryFor every file, read the frontmatter (`handoff`, `title`, `created`) and the`<handoff-summary>` block. The summary is written to be self-contained — thatis the part the user wants to see.If a file's frontmatter or summary cannot be parsed, mark it with `⚠ malformed`and continue listing the rest.## Step 3 — Present the overviewShow the handoffs ordered by number. For each one, give the number, title,created date, and the summary in the user's own language if they are notwriting in English. (Handoff files are stored in English; translate summariesinto the user's language for display only.) A compact table works well whenthere are several:| # | Title | Created | Summary ||------|-------------------------------|------------|----------------------------------|| 0001 | Add rate limiting to the API | 2026-05-12 | <one-line gist of the summary> || 0002 | Migrate config to TypeScript | 2026-05-18 | <one-line gist of the summary> |If there are only one or two handoffs, a short prose description of each readsbetter than a table — use judgment.Close by reminding the user they can dive into one with `handoff-invoke <number>`or clear a finished one with `handoff-close <number>`.

Frequently asked questions