agentleFS
Sign inStart free
RevealUIStudioRevealUIStudio/revskills/skills/revealui-coordinate/SKILL.md

coordinate

Skill2 starsChanged 52 days agoMITView on GitHub

Live peer coordination packet for Grok Build (and equal adapters). Use when the user runs /coordinate, asks to coordinate with peers, or asks who else is live / what to stay off. Snapshot calls --mode=report (read-only). Checkpoint calls --mode=refresh (overwrite this session's workboard.d/active row). Manual default is full. Not /checkpoint (session-end archive). Not /pickup. Not grok-bot-handoff (cloud bots; use --bots to print a facts block for that skill).

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use addskill, apply-firmware and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ryanportfolioSkill

    addskill

    Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.

    Also in 6 projects that use this

  • ryanportfolioSkill

    apply-firmware

    Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.

    Also in 6 projects that use this

  • +10 more from ryanportfolio

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Run node "$COORD" --mode=full (add --claim / --stay-off / --bots as asked).

    line 54
  2. Distinctive:

    Do not open a checkpoint PR.

    line 56
  3. Very specific:

    After snapshot Step 2 mechanical state, run --mode=report and paste a short

    line 61
  4. Very specific:

    After checkpoint inventory, run --mode=refresh with this session's claim.

    line 66
  5. Very specific:

    Do not treat this as /checkpoint or /pickup.

    line 80
  6. Distinctive:

    Do not invent a second TRACKER.

    line 81
  7. Very specific:

    Do not gh pr merge, --admin, --auto, or --no-verify.

    line 82
  8. Very specific:

    Do not write CURRENT-HANDOFF.md or workboard.md.

    line 83
  9. Distinctive:

    Do not claim a bot was notified unless a real channel exists (v1 has none).

    line 84

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

Coordinate (/coordinate) — live peer packet

One helper, three modes. Writes only this session's $JV_REPO/.revealui/workboard.d/active/<id>.md. Never commits. Never pushes into a cloud Grok Bot session.

Load helpers:

. "$REVEALFLEET_ROOT/revskills/scripts/lib/session-state.sh"
COORD="$REVEALFLEET_ROOT/revskills/skills/revealui-coordinate/scripts/coordinate.js"

Modes

ModeWhenWrites
report/snapshot Step 2none
refresh/checkpoint after inventoryown active/<sid>.md
full/coordinate (default)own active/<sid>.md; --bots prints facts for grok-bot-handoff
node "$COORD" --mode=report
node "$COORD" --mode=refresh --claim 'GAP-494' --stay-off 'revdev'
node "$COORD" --mode=full --bots

--json for machine output. --id overrides ss_session_id / AGENT_SESSION_ID.

Manual /coordinate (full)

  1. Run node "$COORD" --mode=full (add --claim / --stay-off / --bots as asked).
  2. Print the COORDINATE report. Fold conflicts into the current task's stay-off.
  3. Do not open a checkpoint PR. Do not steal a named GAP another active row owns.
  4. --bots: pass the printed FACTS block to grok-bot-handoff. Do not emit a /pickup fence as a bot prompt.

Snapshot hook (report)

After snapshot Step 2 mechanical state, run --mode=report and paste a short Peers list into ## Active-Constraints. No writes.

Checkpoint hook (refresh)

After checkpoint inventory, run --mode=refresh with this session's claim. The existing Step 5b fragment commit ships workboard.d/active. Do not start a second PR.

Audiences (do not mix)

AudienceChannel
Grok Build peersactive_sessions.json + workboard.d/active
Cloud Grok Bot--bots facts → grok-bot-handoff (paste only)
Hosted RevealUI agentsout of v1

Do not

  • Do not treat this as /checkpoint or /pickup.
  • Do not invent a second TRACKER.
  • Do not gh pr merge, --admin, --auto, or --no-verify.
  • Do not write CURRENT-HANDOFF.md or workboard.md.
  • Do not claim a bot was notified unless a real channel exists (v1 has none).

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