agentleFS
Sign inStart free
AhmedMerzaAhmedMerza/agent-skills/skills/handover-list/SKILL.md

handover-list

Skill2 starsChanged 41 days agoMITView on GitHub

List the saved handover plans in this project's .claude/handover/ with their title, status, and slug. Run only when the user explicitly asks for it.

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Look in .claude/handover/ for *.md files.

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

You are listing the saved handover plans for the current project so the user can pick one to resume.

1. Find them

Look in .claude/handover/ for *.md files. If the directory is missing or empty, tell the user there are no saved handovers yet (and that /handover-save creates one) — then stop.

2. For each plan, extract

  • Slug — the filename without .md (this is what you pass to /handover-resume <slug>).
  • Title — the # ... heading (first line).
  • Status — the **Status:** line.

Grep the # and **Status:** lines rather than reading whole files.

3. Present a compact table

SlugTitleStatus
add-order-exportAdd order export endpointnot started

Order by most-recently-modified first (use ls -t). Keep Status to its first clause — don't dump the whole line. End by reminding the user they can reload one with /handover-resume <slug>.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free