agentleFS
shreyasnivasshreyasnivas/samepage/skills/samepage/SKILL.md

samepage

Skill4 starsChanged 2 months agoMITView on GitHub

One command that puts this pane on the same page as every other agent pane on this repository: it pings them for a one-line status, gathers the shared memory, and prints a short digest. Use when the user says samepage, /samepage, get on the same page, I am opening another terminal, or before starting work in a new pane.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. bcbarnespublic/skills★ 4same 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.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Run samepage (add --task "<what you are about to do>" when you know it).

    line 8
  2. Distinctive:

    Read the digest. If OVERLAP names a pane, tell the user which files it touches and ask before editing them.

    line 13
  3. Very specific:

    Write your own note early: samepage wip "<one line>".

    line 14
  4. Distinctive:

    Do not re-ask the user for anything the digest already says.

    line 16
  5. Very specific:

    If a one-line message arrives in this pane asking you to run samepage wip, that is another pane's sonar: run that one command with a …

    line 18

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

samepage

Run samepage (add --task "<what you are about to do>" when you know it). One command; it needs nothing else from you.

What it does in a few seconds: creates the shared brain if this repository has none, pings every other live agent pane on this repository for a one-line status (only the ones whose note is stale; never the same pane twice in ten minutes), waits briefly for their answers, and prints a digest of at most forty lines: who is open and what each is doing, the live memory rows, the last lessons, and OVERLAP if your task touches what another pane is working on.

Then:

  • Read the digest. If OVERLAP names a pane, tell the user which files it touches and ask before editing them.
  • Write your own note early: samepage wip "<one line>". A crash saves nothing.
  • A durable lesson: samepage remember "<one line>". Search: samepage recall <word>.
  • Do not re-ask the user for anything the digest already says.

If a one-line message arrives in this pane asking you to run samepage wip, that is another pane's sonar: run that one command with a one-line status and carry on. Do not run samepage prime or samepage init by hand; samepage does what is needed.

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.