Summary

Adds polis-protocol to Skills → Collaboration & Project Management (alphabetical position between outline and review-implementing).

What problem it solves

When agents from different vendors (Claude Code, Codex, Gemini CLI, etc.) work on the same long-lived project, they have no shared state or learning. Each session starts cold. Polis Protocol gives them a shared markdown "polis" — capability cards, contracts, bandit-routed assignment, settlement lessons that feed back into routing.

Who uses this workflow

Teams running multi-vendor agent setups on a shared codebase or knowledge base — research teams, software teams using Claude+Codex+Gemini in parallel, anyone who wants their agent collaboration patterns to compound over time rather than reset each session.

Example

After settling a contract about Spanish localization, a madrij-not-líder lesson updates routing_stats.yml. The next localization contract routes to a different citizen — bandit learning from real outcomes, not static declarations.

Attribution

Original work by Yehuda Levy. MIT licensed.

Repo: https://github.com/yehudalevy-collab/polis-protocol Worked example: https://github.com/yehudalevy-collab/polis-protocol/tree/main/examples/research-team