agentleFS
Sign inStart free
zlatko-lakisiczlatko-lakisic/agent-coop/.cursor/skills/compatibility/SKILL.md

compatibility

Skill0 starsChanged 19 days agoApache-2.0View on GitHub

Update the Agent Co-op compatibility table when a change can affect an older version. Use when editing messages, the board, settings, roles, migrations, skills, setup, update, or the schedule.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. orangehrm/orangehrm★ 1.1ksame name
    2. geeks-accelerator/in-bed-ai★ 26same 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.

  • In this repository3 other files it gives its agents.

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. Distinctive:

    Before you finish, see if the change touches any of these:

    line 12
  2. Very specific:

    If something in that list changed, edit the Unreleased row in src/agentcoop/data/compat.json.

    line 25
  3. Very specific:

    If an older version would break, add a migration with a down step, raise board_format, and set min_version.

    line 39
  4. Very specific:

    Leave the table alone. In the pull request body, add a line No compatibility change: and the reason.

    line 43
  5. Distinctive:

    Every change must work on Windows, macOS, and Linux.

    line 49

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

Compatibility

The table is src/agentcoop/data/compat.json. COMPATIBILITY.md is generated from it. Cursor reads this skill from .cursor/skills/ (project skills).

1. Check the change

Before you finish, see if the change touches any of these:

  • message fields, message types, or the v value (core.py, schema.py, SPEC.md)
  • board folders: inbox, done, sent, files, archive, context, progress, outbox, requests, watchers, STATUS.md, or any new board file
  • keys in projects.json, agents.json, config.json, or the integrity hash
  • role rules
  • board_format, min_version, or migrations
  • skill, rule, AGENTS.md, GEMINI.md, or Claude desktop skill text
  • setup or update flags that older versions call, or that docs/agent-setup.md and docs/agent-update.md tell an agent to run
  • the background schedule entry or the PATH wrapper

2. Update the Unreleased row

If something in that list changed, edit the Unreleased row in src/agentcoop/data/compat.json. Then run:

python3 scripts/gen_compat.py

3. Write what a downgrade loses

Say what the person loses, in plain words. Write Nothing only when that is true.

4. Keep old boards readable

Additive is the default. An older version should ignore the new key or file.

If an older version would break, add a migration with a down step, raise board_format, and set min_version. Explain in the pull request why that was needed.

5. When nothing in the list changed

Leave the table alone. In the pull request body, add a line No compatibility change: and the reason.

6. Version bump

In the version bump pull request, turn the Unreleased row into the new version and the release date. Add a new Unreleased row with Nothing and None.

Every change must work on Windows, macOS, and Linux. Test on all three in CI, and list any skips in the PR.

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