agentleFS
Sign inStart free
wublinuxwublinux/supply-chain-local-agent/skills/create-handoff/SKILL.md

create-handoff

Skill0 starsChanged 3 months agoMITView on GitHub

Use when the user wants to turn current work into a structured, reviewable handoff draft.

6 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions6 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 6

    1. parcadei/Continuous-Claude★ 3.9ksame name
    2. parcadei/Continuous-Claude-v2★ 3.9ksame name
    3. parcadei/Continuous-Claude-v3★ 3.9ksame name
    4. EnkrateiaLucca/skills★ 3same name
    5. corticalstack/flow★ 1same name
    6. charly-vibes/incitaciones★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

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

    Call kb_status and verify the required knowledge is approved.

    line 10
  2. Very specific:

    Call handoff_prepare with the handoff subject and separate queries for each important business area.

    line 11
  3. Very specific:

    Use kb_get when exact wording or surrounding context matters.

    line 12
  4. Very specific:

    Keep the evidence chunkId on every item supported by the knowledge base.

    line 23
  5. Very specific:

    Do not invent contacts, deadlines, owners, decisions, or completion status.

    line 24

“Common” is measured: kept by at least 6 in 10 of the 6 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

Create a Work Handoff

Workflow:

  1. Call kb_status and verify the required knowledge is approved.
  2. Call handoff_prepare with the handoff subject and separate queries for each important business area.
  3. Use kb_get when exact wording or surrounding context matters.
  4. Collect and confirm:
  • current status;
  • completed work;
  • pending actions, owners, and deadlines;
  • risks and blocking conditions;
  • confirmed contacts;
  • decisions and reasons;
  • source files and page references.
  1. Keep the evidence chunkId on every item supported by the knowledge base. Items that come only from the current conversation must have an empty source list and be described as unverified conversation input.
  2. Do not invent contacts, deadlines, owners, decisions, or completion status. A contact can be marked confirmed only when it exists in approved/contacts.csv.
  3. Show the complete proposed handoff to the user. Call create_handoff only after explicit confirmation.
  4. The saved file remains a draft. Only the user can approve it with /handoff-approve <id>.

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