agentleFS
Sign inStart free
danielrosehilldanielrosehill/Claude-Hopper/skills/clipboard-handover/SKILL.md

clipboard-handover

Skill1 starsChanged 7 months agoMITView on GitHub

Short YAML handover displayed in chat and copied to clipboard. No files, no spawn. Use when user says "clipboard handover", "copy handover", "handover to clipboard".

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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. Distinctive:

    No files created, no session spawned

    line 56
  2. Very specific:

    If user passes args (e.g. /clipboard-handover focus on API changes), incorporate into summary

    line 58

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Clipboard Handover

Generate a terse YAML handover, display in chat, copy to clipboard. Nothing written to disk.

When to use

  • User wants a portable summary to paste into Slack, a ticket, or another Claude session
  • Quick context capture without file clutter

Procedure

1. Gather context

Run in parallel:

  • git rev-parse --show-toplevel
  • git branch --show-current
  • git log --oneline -3
  • git status --short
  • git diff --stat

2. Compose handover

Review conversation context and git state. Use this exact format, terse telegraphic English, no articles/filler:

# Clipboard Handover
repo: name
branch: name
last_commit: hash msg
goal: one sentence
done: comma-separated items or ~
next: single most important step — be specific
watch_out: one warning/gotcha or ~
uncommitted: yes/no + brief desc

Keep under 12 lines.

3. Display and copy

  1. Display the YAML in chat as a code block.
  2. Copy to clipboard:
    echo "<the handover text>" | wl-copy
    Fall back to xclip -selection clipboard if wl-copy fails.
  3. Confirm: "Copied to clipboard."

Notes

  • No files created, no session spawned
  • For file-based handover use /session-transfer:write-handover or /session-transfer:quick-handover
  • If user passes args (e.g. /clipboard-handover focus on API changes), incorporate into summary

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