agentleFS
zlatko-lakisiczlatko-lakisic/agent-coop/.cursor/skills/wiki/SKILL.md

wiki

Skill0 starsChanged 19 days agoApache-2.0View on GitHub

Keep the Agent Co-op wiki in step with changes a person can see or do. Use when a change touches commands, chat phrases, install, the board, settings, permissions, safety, agents, errors, or troubleshooting.

43 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ai-slop-cleaner, ralplan 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.
  • Jurel89Skill

    ai-slop-cleaner

    Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode

    Also in 4 projects that use this

  • ibahgatSkill

    ralplan

    Create a strict, quality-first execution plan with explicit gates and rollback-ready sequencing.

    Also in 4 projects that use this

  • Yeachan-HeoSkill

    ultragoal

    Create and execute durable repo-native multi-goal plans over Codex goal mode artifacts.

    Also in 3 projects that use this

  • woosikkimSkill

    deepinit

    Generate hierarchical AGENTS.md codebase maps for agent context

    Also in 3 projects that use this

  • ibahgatSkill

    hud

    Control omi visual HUD profile and keep status output readable in normal, compact, or hidden mode.

    Also in 3 projects that use this

  • klauswgSkill

    deep-interview

    在明确批准执行之前,通过数学化歧义门控进行苏格拉底式深度访谈

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 37 edited versions we read keep these.

  • 5

    Distinctive

    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:

    Update it when a change touches anything a person sees or does:

    line 12
  2. Distinctive:

    Add a row when you add a page.

    line 53
  3. Very specific:

    Check each command, flag, path, phrase, exit code, and message against the source.

    line 59
  4. Distinctive:

    If something is not confirmed, say that, and say what to check.

    line 61
  5. Very specific:

    Do not edit Chat-phrases.md or Command-reference.md by hand.

    line 69
  6. Distinctive:

    Do this only after the main pull request is merged, so the wiki never describes work that did not land.

    line 79
  7. Very specific:

    Add a line Wiki: <pages changed>, or No wiki change: <reason>.

    line 83
  8. Distinctive:

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

    line 89

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

Wiki

The guide people read is the GitHub wiki, in the agent-coop.wiki folder next to this repo. Its branch is master. The main repo stays the source for anything an agent follows.

1. Decide if the wiki needs an update

Update it when a change touches anything a person sees or does:

  • commands, flags, or output
  • chat phrases
  • skill or rule text
  • install, update, or uninstall steps
  • board files
  • settings
  • permissions
  • safety rules
  • supported agents
  • error messages
  • the troubleshooting cases

2. Find the pages

SourceWiki pages
src/agentcoop/cli.pyCommand reference, Exit codes
src/agentcoop/data/phrases.json, src/agentcoop/templates/Chat phrases
src/agentcoop/watch.pyKeeping agents checking, Exit codes
src/agentcoop/update.py, docs/agent-update.md, docs/update.mdUpdating, Install a specific version
src/agentcoop/updatecheck.pyUpdating, STATUS.md and the viewer
src/agentcoop/migrate.py, COMPATIBILITY.mdCompatibility, Updating
src/agentcoop/uninstall.py, docs/agent-uninstall.mdUninstall
src/agentcoop/install.py, docs/agent-setup.mdInstall on Windows, Install on macOS, Install on Linux, Your first project
src/agentcoop/confirm.pyPermissions
src/agentcoop/safety.py, docs/security.mdSafety and privacy
src/agentcoop/projects.py, src/agentcoop/schema.pyProjects, Settings files
src/agentcoop/context.py, src/agentcoop/progress.pyContext and progress, Done means verified
src/agentcoop/taskreview.py, src/agentcoop/donereport.pyDone means verified, Roles, Working with several helpers
src/agentcoop/rounds.py, docs/schedule.mdBackground runs, Keeping agents checking
src/agentcoop/ui.py, src/agentcoop/statusfile.pySTATUS.md and the viewer
src/agentcoop/tools.py, AGENTS-SUPPORT.md, docs/tools/Cursor, Claude Code, Codex and the ChatGPT desktop app, Gemini CLI, Local models, Planned agents, Claude desktop app
src/agentcoop/desktop.py, src/agentcoop/outbox.pyClaude desktop app, Troubleshooting
src/agentcoop/paths.py, SPEC.mdHow it works, Board layout, Message format
src/agentcoop/gitshim.py, src/agentcoop/worktree.pyBackground runs
src/agentcoop/session.pyTroubleshooting, Environment variables
src/agentcoop/runner.py, docs/runner.mdLocal models
docs/troubleshooting.mdTroubleshooting

Add a row when you add a page.

3. Edit them

Write for a person. Lead with what to say in chat. Put terminal commands in a details block. Sentence case. No em dashes or en dashes. Start each page with one or two sentences. Mark a new feature with Added in <version>, using the version the change will ship in. Do not write that a version is the latest. Link to the releases page.

Check each command, flag, path, phrase, exit code, and message against the source. Run command examples on a temporary board (AGENTCOOP_BOARD and HOME set to a temp folder) and paste the real output, trimmed.

If something is not confirmed, say that, and say what to check.

4. Regenerate

python3 scripts/gen_wiki.py --wiki ../agent-coop.wiki

Do not edit Chat-phrases.md or Command-reference.md by hand.

5. Check links

python3 scripts/check_wiki_links.py ../agent-coop.wiki

6. Commit and push the wiki

Do this only after the main pull request is merged, so the wiki never describes work that did not land. The commit message names that pull request number.

7. Say it in the pull request

Add a line Wiki: <pages changed>, or No wiki change: <reason>.

8. Never put on the wiki

Secrets, internal hostnames or IP addresses, personal project details, or a guess presented as a fact.

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.