agentleFS
Simple-With-UsSimple-With-Us/BotFleet/.claude/skills/pickup-seat/SKILL.md

pickup-seat

Skill4 starsChanged 12 days agoApache-2.0View on GitHub

Pick up a capped-out or abandoned peer seat's in-flight work (owner-directed only). Inventory THE BOARD, effort logs, PRs, dirty worktrees, and Slack; claim; adopt uncommitted work with authorship credit; disposition each item; hand back. Use when the owner says a seat hit a usage cap, died mid-task, or "take over X's lanes."

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are 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.

  • 4

    Very specific

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

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

    Put the same claim on Linear (board claim or board comment) and a Zulip post in the work topic.

    line 54
  2. Very specific:

    If they used FLEET incorrectly, do not echo it.

    line 56
  3. Very specific:

    Never reset --hard / checkout over dirty files.

    line 60
  4. Very specific:

    Do not kill com.jay.claude-remote-control while hunting "stuck Claude." Monet/Renoir/Claude all look like claude in ps.

    line 87
  5. Distinctive:

    Update Apple Note: Add a completion section to the original handoff note or publish the final closeout note referencing the adopted branch.

    line 114

≈ “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

Pick up a seat (MONET)

Shared ~/.claude/skills. Monet, Claude/Fable, and (when active) Renoir all load this directory. Do not treat the word Monet in examples as proof of your seat. Pin AGENT_SEAT / AGENT_TAG from the logged-in account before Slack or board --by:

  • Monet → MONET, Notes Monet, monet/, ~/apps/<app>-monet
  • Claude / Fable → CLAUDE, Notes Claude, claude/, ~/apps/<app>-claude
  • Renoir → RENOIR, Notes Renoir, renoir/, ~/apps/<app>-renoir Cursor, Grok, Grok Bot, Codex, AG, DeepSeek, Kimi, and Fx have their own skill dirs and must not take identity from here.

Owner-directed only. Do not initiate a raid on a live peer.

You are $AGENT_SEAT (MONET, CLAUDE, or RENOIR). Keep that seat's prefix. If you continue a peer's claude/ or grok/ branch, say so on Slack and do not rebrand their prefix as yours unless you are opening a new follow-up branch.

INVENTORY

board list --status in_progress --limit 50
board list --mine <THEIR_TAG> --status open,in_progress

# Live boards (skip none — pickup is often cross-app)
rg -n "In Progress" /Users/jay/apps/*EFFORT-LOG.md

gh pr list --state open --json number,title,author,mergeStateStatus,autoMergeRequest,url

git worktree list
# then git status in each dirty tree you might adopt

git for-each-ref --sort=-committerdate refs/remotes/origin --format='%(committerdate:short) %(refname:short) %(authorname)' | head -30

AGENT_SEAT="${AGENT_SEAT:?set MONET, CLAUDE, or RENOIR}" simple-chat read --channel Work-In-Progress --topic "<active work topic>" --json --limit 20

Also read their last #Work-In-Progress claim and any living Apple Note titled [APP, <Seat>] ….

CLAIM

Post repo-first, naming exactly what you are taking:

printf '%s\n' "[MONET-><SEAT>] sync-1
repo: <project>
claim: picking up <SEAT> cap — effort + PR #<n>
state: WIP
do-not: double-work these lanes" > /tmp/claim-note.md && chmod 600 /tmp/claim-note.md
AGENT_SEAT="${AGENT_SEAT:?set MONET, CLAUDE, or RENOIR}" simple-chat post --topic "<project> sync" --body-file /tmp/claim-note.md

Put the same claim on Linear (board claim or board comment) and a Zulip post in the work topic. Effort logs are archived — do not edit them.

If they used FLEET incorrectly, do not echo it. Directed <SEAT> is enough.

ADOPT uncommitted work

Never reset --hard / checkout over dirty files.

git add <files>
git commit -m "Uncommitted work from capped <SEAT> session.

Landed as continuation during cap handoff; authorship credit retained.

Co-Authored-By: Claude <noreply@anthropic.com>"

Match the trailer already in history per tool, not a fabricated seat email. Monet and Claude Code both use Claude <noreply@anthropic.com>. Codex/Grok/Cursor trailers stay those tools' trailers.

Confirm no new commits or Slack posts from that seat since the cap before you overwrite their narrative.

DISPOSITION

StateAction
Already mergedgit log origin/main; board row Deployed if prod verified, else Completed
Armed + greenbabysit; unstick-pr if it stalls
Committed, not landedland-lane
Uncommitted, finishedcommit with credit; land or hold
Uncommitted, unfinishedcomplete only if owner-directed; else note and park
Claimed, not startedrelease; Slack + board
Genuinely blockedboard comment with reason; escalate P0

Do not kill com.jay.claude-remote-control while hunting "stuck Claude." Monet/Renoir/Claude all look like claude in ps.

HAND BACK

Answer disambiguation pings fast. Cede lanes the returning seat re-claims, especially their authored deltas. Report SHAs, PR numbers, board ids, what is ready to merge.

CLOSE OUT

closeout skill: Linear resolution, docs/rollouts/YYYY-MM-DD-pickup-<seat>-cap.md, Apple Note [APP, Monet] pickup <seat> cap, Slack summary. Correct premature claims in place on Linear.

Canon

  • /Users/jay/apps/FLEET-PROTOCOL.md — handoff, seats, Mac local processes
  • /Users/jay/apps/EFFORT-LOG-PROTOCOL.md
  • Skills: session-start, board-ops, land-lane, unstick-pr, closeout

Substitute Agent Direct Slack Closeout [SUB->ORIGINAL]

Once you finish taking over a peer agent's work (or reach a clean handoff point):

  1. Post to the coordination channel: Post to #Work-In-Progress addressed to the original agent:
    [<YOUR_TAG>-><ORIGINAL_TAG>]
    repo: <repo>
    task: <Feature / PR #<num>>
    status: Completed & Deployed
    notes: <Summary of what was completed, any bugs fixed, or caveats for the original agent to review>
  2. Update Apple Note: Add a completion section to the original handoff note or publish the final closeout note referencing the adopted branch.

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.