agent-coordination
Skill3 starsChanged 4 months agoApache-2.0View on GitHub
Coordination protocol for agents accessing the knowledge base. Use when any agent needs to fetch prior notes, templates, or reference documents from the vault.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- CorvidLabs/skillstheir own version, first seen Nov 8, 2026
- ruvnet/ruflotheir own version, first seen Oct 21, 2026
- jwilger/agent-skillstheir own version, first seen Oct 11, 2026
- ruvnet/claude-flowtheir own version, first seen Oct 8, 2026
- batin/five-guystheir own version, first seen Sep 22, 2026
- Soulcynics404/AgentForgetheir own version, first seen Aug 24, 2026
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- ruvnet/claude-flow★ 80ksame name
- ruvnet/ruflo★ 79ksame name
- bybren-llc/safe-agentic-workflow★ 405same name
- andy-vive/claude-code-agent★ 8same name
- jwilger/agent-skills★ 4same name
- batin/five-guys★ 2same name
- bogdanbaciu21/skills★ 2same name
- Zekiog/ruflo★ 2same name
- CorvidLabs/skills★ 1same name
- fidgetcoding/fidgetflo★ 1same name
3 more not listed
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.
- AGENTS.mdAGENTS.md
- file-namingSkill
- vault-accessSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Default: proactive checking.
- Very specific: line 37
Read .claude/knowledge-base.local.md for vault_path and vault_dir.
“Common” is measured: kept by at least 6 in 10 of the 12 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.
Files
Agent Coordination
The Rule
Call knowledge-base UNLESS you already have all context to finalize the task.
Default: proactive checking. Not reactive.
When to Call
| Category | Trigger Phrases |
| Reference docs | "the reference doc on", "our standard process for", "the how-to for" |
| Templates | "get the template", "our standard [document]", "find a template for" |
| Standing docs | "the standing document on", "our conventions for", "the runbook for" |
| Procedures | "how do we handle", "our process for", "the steps for" |
| Prior Work | "previous note on", "how did we handle [X] before", "prior agreement with" |
Skip When
- Pure code generation (no vault context)
- General knowledge (not vault-specific)
- Context already fetched this task
- Facts already covered by your project instructions (use CLAUDE.md / README)
Vault Path
Read .claude/knowledge-base.local.md for vault_path and vault_dir. Never hardcode paths. See the vault-access skill for tool selection and patterns.
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
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.