ellmos-ai

Cowork Protocol — Development skill for Claude Code

Development community

Reusable collaboration protocol and adaptive bridge for people, WebMCP apps, and web agents.

How to install Cowork Protocol

This entry records only its repository, not the path inside it, so there is no exact command to give. Open ellmos-ai/cowork-protocol and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Cowork Protocol does

Reusable collaboration protocol and adaptive bridge for people, WebMCP apps, and web agents.

Alternatives in Development

  • Contributing To Skill Seeker — First off, thank you for considering contributing to Skill Seeker 11.1k ★
  • IPolloWork — Enterprise-grade, local-first Agent Workbench for people and agent teams 4.9k ★
  • Tutti — Where people and agents build in tune 3.5k ★

README

Cowork Protocol

![Cowork Protocol — one protocol, one human surface, three hosts](design/banner.svg)

Cowork Protocol is a small collaboration contract for people and web agents. It gives an agent the smallest useful context, makes proposed changes visible, keeps human clicks distinct from agent calls, and supports tightly scoped solo work while the human is away.

Native when available. Bridged when necessary.

**[Try the live showcase](https://ellmos-ai.github.io/cowork-protocol/apps/formbuilder-showcase/)** · **[Watch the demo video](https://youtu.be/9CJehV7Bugk)** · [Three in one: two bridges, one vehicle](docs/hosts.md) · [Architecture](docs/architecture.md) · [Work modes](docs/work-modes.md) · [Panel tour](docs/panel-tour.md) · [Agent guide](docs/agent-guide.md) · [How to use it](docs/panel-tour.md#walkthrough-one-session-start-to-finish) · [Evidence ledger](docs/evidence.md) · [Outlook](docs/outlook.md) · [Pre-existing and new work](PREEXISTING-AND-NEW.md)

**Install it with your AI assistant:** hand [docs/install-with-your-assistant.md](docs/install-with-your-assistant.md) to Claude Code, Codex CLI or a comparable agent and say "install this for me". [`llms.txt`](llms.txt) is the machine-readable index.

Three in one: two bridges with a place, one vehicle

The protocol is the submission; everything else here exists to show it holds up wherever the human happens to be. A **bridge** has a place: it sits between one page and one model, and it is where you see what the model sees and where the click happens. A **vehicle** carries a model across it. Building the bridge twice is the whole argument — once where a page invites it, once where a page knows nothing about it.

1a. **The rails alone** — the packages, wired into your own app's own UI. The contract without a single Cowork pixel, and no bridge yet. 1b. **The bridge, built into the page** — one instrument the page itself renders, no install. The live showcase runs at this level. 2. **The same bridge,