Onboarding
agentuse/agentuse
Guide a new AgentUse user from a confirmed project to one validated first agent and its first CLI or Web UI run.
Structured multi-agent collaboration for backend + frontend builds.
Install Agent Collaboration Protocol
$ npx skills add LeoYeAI/openclaw-master-skills --skill agent-collaboration-protocol -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills agent-collaboration-protocol --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/agent-collaboration-protocol .claude/skills/agent-collaboration-protocol && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "agent-collaboration-protocol" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/agent-collaboration-protocol into .claude/skills/agent-collaboration-protocol/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-collaboration-protocol", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/agent-collaboration-protocolType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add LeoYeAI/openclaw-master-skills --skill agent-collaboration-protocol -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills agent-collaboration-protocol --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/agent-collaboration-protocol .agents/skills/agent-collaboration-protocol && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "agent-collaboration-protocol" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/agent-collaboration-protocol into .agents/skills/agent-collaboration-protocol/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-collaboration-protocol", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill agent-collaboration-protocol -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills agent-collaboration-protocol --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/agent-collaboration-protocol .cursor/skills/agent-collaboration-protocol && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "agent-collaboration-protocol" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/agent-collaboration-protocol into .cursor/skills/agent-collaboration-protocol/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-collaboration-protocol", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/LeoYeAI/openclaw-master-skills.git --path skills/agent-collaboration-protocol--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add LeoYeAI/openclaw-master-skills --skill agent-collaboration-protocol -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills agent-collaboration-protocol --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/agent-collaboration-protocol .gemini/skills/agent-collaboration-protocol && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "agent-collaboration-protocol" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/agent-collaboration-protocol into .gemini/skills/agent-collaboration-protocol/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-collaboration-protocol", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install LeoYeAI/openclaw-master-skills agent-collaboration-protocolInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add LeoYeAI/openclaw-master-skills --skill agent-collaboration-protocol -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/agent-collaboration-protocol .github/skills/agent-collaboration-protocol && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "agent-collaboration-protocol" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/agent-collaboration-protocol into .github/skills/agent-collaboration-protocol/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-collaboration-protocol", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill agent-collaboration-protocol -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills agent-collaboration-protocol --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/agent-collaboration-protocol .opencode/skills/agent-collaboration-protocol && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "agent-collaboration-protocol" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/agent-collaboration-protocol into .opencode/skills/agent-collaboration-protocol/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-collaboration-protocol", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
agent-collaboration-protocol- GitHub stars
- 2.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 308 words
- Files
- 8 (incl. scripts, references)
- Skills in repo
- 972
- Repo updated
- First seen
- Licence
- MIT
At a glance
Structured multi-agent collaboration for backend + frontend builds.
- Works in 4 steps: Orchestrator Creates the Build Directory… → Orchestrator Spawns Agents → Both Build Simultaneously → …
- An orchestrator needs to coordinate a backend engineer and frontend engineer on the same feature
- SKILL.md covers How It Works, Workflow, Setup Script and Reference Files, plus 2 more sections
- Runs Shell scripts from its folder
What it does
Agent Collaboration Protocol is an agent skill from LeoYeAI/openclaw-master-skills. Structured multi-agent collaboration for backend + frontend builds. Use when an orchestrator needs to coordinate a backend engineer and frontend engineer on the same feature. Triggered by multi-role build requests like "build a dashboard with an API and UI" or "create a full-stack feature" or any task requiring both backend (API, data, infra) and frontend (UI, templates, design) work.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including scripts and reference files (for example `.clawhub/origin.json`, `_meta.json` and `clawhub.json`).
It sits in Frontend & Design, covering Frontend development and Multi-agent orchestration. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.
When your agent uses it
- An orchestrator needs to coordinate a backend engineer and frontend engineer on the same feature
- Tasks that involve Frontend development
- Tasks that involve Multi-agent orchestration
Example prompts
- “build a dashboard with an API and UI”
- “create a full-stack feature”
- “/agent-collaboration-protocol”
Requirements
- A Bash shell
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Shell), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Agent Collaboration Protocol loads about 1.1k tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 104 tokens; SKILL.md has 308 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 308 words, ~1,082 tokens.
Download SKILL.mdSave it as
.claude/skills/agent-collaboration-protocol/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.- name
- agent-collaboration-protocol
- description
- Structured multi-agent collaboration for backend + frontend builds. Use when an orchestrator needs to coordinate a backend engineer and frontend engineer on the same feature. Triggered by multi-role build requests like "build a dashboard with an API and UI" or "create a full-stack feature" or any task requiring both backend (API, data, infra) and frontend (UI, templates, design) work.
Agent Collaboration Protocol
How It Works
Three roles collaborate through a shared workspace:
| Role | Responsibility |
|---|---|
| Orchestrator | Defines the contract, spawns both builders, verifies integration, merges |
| Backend Engineer | Writes API code, data models, infrastructure |
| Frontend Engineer | Writes UI components, templates, styles |
The contract lives in shared/build-{YYYYMMDD}/. Both builders write to the same directory. The orchestrator inspects and merges when both are done.
Workflow
Step 1: Orchestrator Creates the Build Directory and Contract
shared/build-{YYYYMMDD}/
SPEC.md ← Integration contract
backend/ ← Backend Engineer writes here
frontend/ ← Frontend Engineer writes here
integration.md ← Both update as they workWrite SPEC.md with these sections:
# SPEC: {Feature Name}
## Contract
- API base path, auth scheme, content type
- Data models (all entities, fields, types, relationships)
- Endpoints (method, path, request/response shapes)
- Error format
## Routes
Backend Engineer implements these. Frontend Engineer consumes them.
## UI Components
Frontend Engineer builds these. Backend Engineer doesn't touch them.
## Success Criteria
Observable behavior. Not "tests pass" — "user can log in and see calendar."Step 2: Orchestrator Spawns Agents
Spawn two subagents with sessions_spawn:
Backend Engineer:
task: >
Implement the API spec in shared/build-{YYYYMMDD}/SPEC.md.
Write all backend code to shared/build-{YYYYMMDD}/backend/.
Update shared/build-{YYYYMMDD}/integration.md with progress.
Use {backend framework} (FastAPI, Express, etc.).Frontend Engineer:
task: >
Implement the UI for the spec in shared/build-{YYYYMMDD}/SPEC.md.
Write all frontend code to shared/build-{YYYYMMDD}/frontend/.
Use the API contract in SPEC.md for your fetch calls.
Update shared/build-{YYYYMMDD}/integration.md with progress.
Use {frontend stack} (HTMX+Tailwind, React, etc.).Set mode: "run" for one-shot completion.
Step 3: Both Build Simultaneously
Backend Engineer writes to shared/build-{YYYYMMDD}/backend/:
- Router/handler code
- Data models and schemas
- Config and infrastructure files
- Updates
integration.mdwith progress and any blockers
Frontend Engineer writes to shared/build-{YYYYMMDD}/frontend/:
- UI components / templates
- Styles and layout
- API client code
- Updates
integration.mdwith progress and any blockers
Step 4: Orchestrator Verifies and Merges
- Read
integration.mdfrom both agents - Inspect files in
backend/andfrontend/ - Verify API responses match UI expectations
- If mismatches found, send corrections to the responsible agent
- Move code to production paths
- Archive the build directory (or delete it)
Setup Script
Run once per project to initialize the collaboration structure:
scripts/init_collab.sh /path/to/projectCreates shared/ with template SPEC.md and .gitignore.
Reference Files
For deeper patterns and templates:
references/spec-template.md— Full SPEC.md template with examplesreferences/integration-log.md— integration.md status formatreferences/handoff-format.md— Task handoff message template
When Not to Use
- Single-file changes (just do it directly)
- Solo tasks that don't cross backend/frontend boundaries
- Bug fixes that are purely backend or purely frontend
- Tasks where one agent can handle both sides (use a single subagent instead)
Limitations
- Requires the
sessions_spawntool (OpenClaw v1.0+) - Works best with model pairs that have complementary strengths (e.g., backend-specialized + frontend-specialized)
- Not a replacement for a design system — frontend engineer should have access to design tokens separately
© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 7 other files (scripts, references) in skills/agent-collaboration-protocol of LeoYeAI/openclaw-master-skills.
- SKILL.md
- .clawhub/origin.json
- _meta.json
- clawhub.json
- references/handoff-format.md
- references/integration-log.md
- references/spec-template.md
- scripts/init_collab.sh
Open the folder on GitHubat commit e5199b5
Compare with similar skills
Agent Collaboration Protocol next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Agent Collaboration Protocol this skillLeoYeAI/openclaw-master-skills | 2.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Onboardingagentuse/agentuse | 205 | — | ~928 | Automated safety check: Pass | Custom licence | |
| Preline UI Components via MCPhtmlstreamofficial/preline | 6.5k | — | ~2.9k | Automated safety check: Pass | Custom licence | |
| Stitch Build Loopgoogle-labs-code/stitch-skills | 8.4k | 5 repos | ~2.6k | Automated safety check: Notes | Apache-2.0 | |
| UI Code Guidelinesrazorpay/blade | 656 | — | ~866 | Automated safety check: Pass | MIT | |
| State ManagementOwl-Listener/ai-design-skills | 181 | — | ~1.5k | Automated safety check: Pass | MIT |
Similar skills
Preline UI Components via MCP
htmlstreamofficial/preline
Adds Preline UI components and blocks to HTML files by querying the Preline MCP server, with rules for exact slugs and for clarifying vague requests.
- Official
Stitch Build Loop
google-labs-code/stitch-skills
Builds a website page by page with Stitch in an autonomous loop, passing a baton file from one iteration to the next that names the next page and prompt.
UI Code Guidelines
razorpay/blade
Important guidelines for writing frontend UI code. An agent skill from razorpay/blade.
State Management
Owl-Listener/ai-design-skills
Managing shared context, memory, and state across multiple agents.
Frontend Dev
nteract/nteract
Frontend development for nteract UI/product surfaces, Elements fixtures, hot reload, dev daemon setup, MCP server workflow, TypeScript bindings via ts-rs, and reactive state work that touches RxJS…
More from LeoYeAI/openclaw-master-skills
All 972 skills in this repoDevOps Pipeline Management
LeoYeAI/openclaw-master-skills
Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.
Feishu Document Collaboration
LeoYeAI/openclaw-master-skills
Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.
Files Memory System
LeoYeAI/openclaw-master-skills
Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.
GEO-Claw AI Visibility Agent
LeoYeAI/openclaw-master-skills
Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.
Google Workspace CLI
LeoYeAI/openclaw-master-skills
Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.
HealthFit Health Advisors
LeoYeAI/openclaw-master-skills
Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.
Related
Categories
Questions about Agent Collaboration Protocol
What does Agent Collaboration Protocol do?
Structured multi-agent collaboration for backend + frontend builds. Agent Collaboration Protocol is an agent skill from LeoYeAI/openclaw-master-skills. Structured multi-agent collaboration for backend + frontend builds.
When should I use Agent Collaboration Protocol?
Agent Collaboration Protocol fits situations like: an orchestrator needs to coordinate a backend engineer and frontend engineer on the same feature; tasks that involve Frontend development; tasks that involve Multi-agent orchestration.
How do I install Agent Collaboration Protocol in Claude Code?
Run `npx skills add LeoYeAI/openclaw-master-skills --skill agent-collaboration-protocol -a claude-code`. Or copy the skill folder (skills/agent-collaboration-protocol in LeoYeAI/openclaw-master-skills) into .claude/skills/agent-collaboration-protocol in your project. Claude Code loads it when a task matches its description.
How do I install Agent Collaboration Protocol in Codex?
Run `npx skills add LeoYeAI/openclaw-master-skills --skill agent-collaboration-protocol -a codex`. Or copy the skill folder (skills/agent-collaboration-protocol in LeoYeAI/openclaw-master-skills) into .agents/skills/agent-collaboration-protocol in your project. Codex loads it when a task matches its description.
Can I use Agent Collaboration Protocol in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill agent-collaboration-protocol -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agent-collaboration-protocol, .gemini/skills/agent-collaboration-protocol, .github/skills/agent-collaboration-protocol and .opencode/skills/agent-collaboration-protocol in your project.
What does Agent Collaboration Protocol need to run?
Going by SKILL.md and its folder, Agent Collaboration Protocol needs a shell for the scripts in its folder. Our summary lists: A Bash shell.
Does Agent Collaboration Protocol access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Agent Collaboration Protocol safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Agent Collaboration Protocol use?
Agent Collaboration Protocol is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Agent Collaboration Protocol use?
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 874 tokens, read only when the agent opens those files.
What are the alternatives to Agent Collaboration Protocol?
Skills that share tags, products or a category with Agent Collaboration Protocol: Onboarding (agentuse/agentuse, 205 stars), Preline UI Components via MCP (htmlstreamofficial/preline, 6.5k stars), Stitch Build Loop (google-labs-code/stitch-skills, 8.4k stars) and UI Code Guidelines (razorpay/blade, 656 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Agent Collaboration Protocol?
LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,159 GitHub stars. The repository holds 972 skills in this directory. The repository was last updated on July 20, 2026.
Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.