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
- jaywedgeworth22/BotFleetword for word, first seen Nov 3, 2026
Other versions1 project uses a version of this.
Word for word · 1
- jaywedgeworth22/BotFleet★ 4100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/merge-when-ready.mdcCursor rule
- apple-notesSkill
- board-opsSkill
- closeoutSkill
- codex-triageSkill
- deploy-verifySkill
- dns-and-registrarsSkill
- drive-grok-tuiSkill
- fleet-coordinationSkill
- fleet-infraSkill
- land-laneSkill
- mac-cleanupSkill
- owner-copySkill
- secret-handoffSkill
- sentence-gapSkill
- session-startSkill
- unstick-prSkill
- windows-releaseSkill
- phone-harnessSkill
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
- Very specific: line 54
Put the same claim on Linear (board claim or board comment) and a Zulip post in the work topic.
- Very specific: line 56
If they used FLEET incorrectly, do not echo it.
- Very specific: line 60
Never reset --hard / checkout over dirty files.
- Very specific: line 87
Do not kill com.jay.claude-remote-control while hunting "stuck Claude." Monet/Renoir/Claude all look like claude in ps.
- Distinctive: line 114
Update Apple Note: Add a completion section to the original handoff note or publish the final closeout note referencing the adopted branch.
≈ “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.
Files
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. PinAGENT_SEAT/AGENT_TAGfrom the logged-in account before Slack orboard --by:
- Monet →
MONET, NotesMonet,monet/,~/apps/<app>-monet- Claude / Fable →
CLAUDE, NotesClaude,claude/,~/apps/<app>-claude- Renoir →
RENOIR, NotesRenoir,renoir/,~/apps/<app>-renoirCursor, 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 20Also 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.mdPut 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
| State | Action |
| Already merged | git log origin/main; board row Deployed if prod verified, else Completed |
| Armed + green | babysit; unstick-pr if it stalls |
| Committed, not landed | land-lane |
| Uncommitted, finished | commit with credit; land or hold |
| Uncommitted, unfinished | complete only if owner-directed; else note and park |
| Claimed, not started | release; Slack + board |
| Genuinely blocked | board 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):
- Post to the coordination channel: Post to
#Work-In-Progressaddressed 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> - Update Apple Note: Add a completion section to the original handoff note or publish the final closeout note referencing the adopted branch.
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
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.

