Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →syncable-dev/memtrace-fleet-first
Coordinate fleets of coding agents sharing one repo+branch: publish typed intents, classify edit episodes, and resolve conflicts before they collide. Use FIRST when multiple agents work the same repo+branch, before reading/planning/editing, when joining a fleet or handing work off, and when the user says two agents are changing the same thing, asks who should proceed, has a decision waiting, or asks you to mediate a Class C conflict. Covers branch-scoped publish-edit-record plus verdict, human-r
Passed 18 of 22 test cases with the skill, and 6 of 22 without it.
and 13 more in the full report
14 fixed7 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
When polling `fleet_get_escalation` returns `your_directive`: 'review', what specific field in the response payload must the agent inspect to learn the guidance?
| Checked | Without skill | With skill |
|---|---|---|
| Directs the agent to read the resolution field. | Missed | Passed |
The instructions your model reads when the skill loads.
The coordination layer for fleets of coding agents working the same repo at the same time. It stops agents from silently clobbering each other's edits, and turns unsafe overlaps into a clear decision instead of a merge-time surprise.
IN A FLEET → FLEET TOOLS BEFORE EDITS. NO EXCEPTIONS.
1. fleet_publish_intent (declare what you'll touch; get blast radius + conflicts)
2. edit (your normal edit loop)
3. fleet_record_episode (classify A/B/C; if C, the loop resolves it)
A typed intent serializes to ~20 tokens; a prose "I'm going to change X" averages 200+. A 10-agent fleet × 100 edits = tens of thousands of tokens saved per fleet-turn — and zero silent overwrites — when the protocol is followed.
Coordination is branch-scoped. Two agents only coordinate when they're on the
same (repo, branch). The branch name is the fleet identifier: a session
branch is how a group of agents opts into one coordinating fleet.
session/auth-revamp)? Pass branch on every
fleet call. Your fleet coordinates together and stays isolated from agents on
other branches.branch only for the shared default pool (single, unnamed fleet).{ "repo_id": "myrepo", "branch": "session/auth-revamp",
"agent_id": "agent-a", "touched": ["auth::verify_token"],
"intent": {"refactor": {"pattern": "change_signature"}},
"assignment": "widen verify_token signature for pagination" }
Always include assignment — your natural-language task. When a conflict
test cases passed, vs 6 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.