agent-collaboration
Skill3.4k starsChanged 2 months agoMITView on GitHub
Standard collaboration patterns for all squad agents — worktree awareness, decisions, cross-agent communication
11 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- microsoft/fsi-banking-payments-dispute-resolution-acceleratorword for word, first seen Oct 25, 2026
- microsoft/github-vteam-industry-demosword for word, first seen Oct 25, 2026
- microsoft/wazaedited, first seen Oct 20, 2026
- kane-mar/skillstheir own version, first seen Oct 9, 2026
- kubefleet-dev/kubefleetword for word, first seen Oct 8, 2026
- github/gh-awword for word, first seen May 27, 2026
Used with
Projects with it also use personal-squad.
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.
Microsoft AzureSkillpersonal-squad
Also in 3 projects that use this
Other versions11 projects use a version of this.
Word for word · 6
- github/gh-aw★ 5.6k100% same
- Azure/fleet★ 227100% same
- kubefleet-dev/kubefleet★ 164100% same
- Azure/apiops-cli★ 32100% same
- microsoft/github-vteam-industry-demos★ 2100% same
- microsoft/fsi-banking-payments-dispute-resolution-accelerator★ 0100% same
Edited · 1
- microsoft/waza★ 1.5k65% same
Wrote their own version · 4
- pascalorg/skills★ 91same name
- othmane55/claude-collective-intelligence★ 4same name
- kane-mar/skills★ 1same name
- Danservfinn/claude-skills★ 0same 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 repository247 other files it gives its agents.
- .github/agents.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- packages/squad-cli/templates/copilot-instructions.mdCopilot instructions
- packages/squad-sdk/templates/copilot-instructions.mdCopilot instructions
- .squad-templates/copilot-instructions.mdCopilot instructions
- .squad/templates/copilot-instructions.mdCopilot instructions
- templates/copilot-instructions.mdCopilot instructions
- action-skill-contractsSkill
- agent-conductSkill
- architectural-proposalsSkill
- architectural-reviewSkill
- archival-integritySkill
- ci-validation-gatesSkill
- client-compatibilitySkill
- cli-wiringSkill
- content-scopeSkill
- distributed-meshSkill
- documentation-maintenanceSkill
- github-multi-accountSkill
- git-workflowSkill
- history-hygieneSkill
- init-modeSkill
- model-selectionSkill
- pr-lifecycleSkill
- protected-filesSkill
- release-processSkill
- reskillSkill
- reviewer-protocolSkill
- secret-handlingSkill
- security-reviewSkill
- squad-conventionsSkill
- test-disciplineSkill
- windows-compatibilitySkill
- agentic-workflow-designerSkill
- gh-aw-reliabilitySkill
- iterative-retrievalSkill
- reflectSkill
- {skill-name}Skill
- agent-collaborationSkill
- agent-conductSkill
- architectural-proposalsSkill
- ci-validation-gatesSkill
- client-compatibilitySkill
- cli-wiringSkill
- coordinator-init-modeSkill
- coordinator-response-modeSkill
- coordinator-source-of-truthSkill
- cross-machine-coordinationSkill
- cross-squad-communicationSkill
- cross-squadSkill
- distributed-meshSkill
- docs-standardsSkill
- e2e-template-testingSkill
- economy-modeSkill
- error-recoverySkill
- external-commsSkill
- fact-checkingSkill
- gh-auth-isolationSkill
- gh-aw-enlistmentSkill
- github-multi-accountSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 6 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
6
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
- Distinctive: line 11
Every agent on the team follows identical collaboration patterns for worktree awareness, decision recording, and cross-agent communication.
- Very specific: line 18
Use the TEAM ROOT path provided in your spawn prompt.
- Very specific: line 21
After making a decision that affects other team members, write it to: .squad/decisions/inbox/{your-name}-{brief-slug}.md
- Distinctive: line 33
If you need another team member's input, say so in your response.
- Distinctive: line 36
If you have reviewer authority and reject work: the original author is locked out from revising that artifact.
- Distinctive: line 39
Don't read all agent charters — you only need your own context + decisions.md
- Very specific: line 40
Don't write directly to .squad/decisions.md — always use the inbox drop-box
- Distinctive: line 41
Don't modify other agents' history.md files — that's Scribe's job
- Distinctive: line 42
Don't assume CWD is the repo root — always use TEAM ROOT
“Common” is measured: kept by at least 6 in 10 of the 5 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
Context
Every agent on the team follows identical collaboration patterns for worktree awareness, decision recording, and cross-agent communication. These were previously duplicated in every charter's Collaboration section (~300 bytes × 18 agents = ~5.4KB of redundant context). Now centralized here.
The coordinator's spawn prompt already instructs agents to read decisions.md and their history.md. This skill adds the patterns for WRITING decisions and requesting help.
Patterns
Worktree Awareness
Use the TEAM ROOT path provided in your spawn prompt. All .squad/ paths are relative to this root. If TEAM ROOT is not provided (rare), run git rev-parse --show-toplevel as fallback. Never assume CWD is the repo root.
Decision Recording
After making a decision that affects other team members, write it to:
.squad/decisions/inbox/{your-name}-{brief-slug}.md
Format:
### {date}: {decision title}
**By:** {Your Name}
**What:** {the decision}
**Why:** {rationale}Cross-Agent Communication
If you need another team member's input, say so in your response. The coordinator will bring them in. Don't try to do work outside your domain.
Reviewer Protocol
If you have reviewer authority and reject work: the original author is locked out from revising that artifact. A different agent must own the revision. State who should revise in your rejection response.
Anti-Patterns
- Don't read all agent charters — you only need your own context + decisions.md
- Don't write directly to
.squad/decisions.md— always use the inbox drop-box - Don't modify other agents' history.md files — that's Scribe's job
- Don't assume CWD is the repo root — always use TEAM ROOT
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.

