agentleFS
Sign inStart free
chinkanchinkan/RustFox/.agents/skills/handoff/SKILL.md

handoff

Skill11 starsChanged 41 days agoMITView on GitHub

Compact the current conversation into a handoff document for another agent to pick up.

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 154 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write a handoff document summarising the current conversation so a fresh agent can continue the work.

    line 8
  2. Distinctive:

    Do not duplicate content already captured in other artifacts (specs, plans, ADRs, issues, commits, diffs).

    line 12
  3. Distinctive:

    If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.

    line 16

“Common” is measured: kept by at least 6 in 10 of the 154 edited versions of this file we could read. “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

Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the temporary directory of the user's OS - not the current workspace.

Include a "suggested skills" section in the document, naming which skills the next agent should call the Skill tool for.

Do not duplicate content already captured in other artifacts (specs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.

Redact any sensitive information, such as API keys, passwords, or personally identifiable information.

If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.

Download now (ZIP)

Trending

Rising: 16 new projects took it in the last 4 weeks, 2× the 4 weeks before.

Week of Aug 30: 1 new projectWeek of Sep 6: 2 new projectsWeek of Sep 13: 4 new projectsWeek of Sep 20: 1 new projectWeek of Sep 27: 4 new projectsWeek of Oct 4: 5 new projectsWeek of Oct 11: 5 new projectsWeek of Oct 18: 2 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read.

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