Skip to content
Back to search

Choir

An open protocol for distributed multi-agent autoformalization.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/weber-geoml--choir/badge.svg)](/listings/weber-geoml--choir)

HTML

<a href="/listings/weber-geoml--choir"><img src="/api/listings/weber-geoml--choir/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

With Claude Code or Codex

Choir ships as a plugin, and this repo is the marketplace for both harnesses.

In a Claude Code session:

/plugin marketplace add Weber-GeoML/Choir
/plugin install choir@choir

In your shell, for Codex:

codex plugin marketplace add Weber-GeoML/Choir
codex plugin add choir@choir

Then say what you want in plain language:

- *"Formalize ‹your theorem, paper, or chapter› with Choir"*: start or resume a project as its **overseer**. - *"Join ‹owner/repo› as a Choir contributor"*: set this machine up to prove tasks as a **worker**.

Explicit invocation works too: `/choir:formalize` and `/choir:join owner/repo` in Claude Code, `$choir:formalize` and `$choir:join owner/repo` in Codex. You can also add your own instructions on top of them.

With any other agent

The plugin defines no behaviour. Its skills only run the setup scripts and defer to the playbooks, so any agent can drive Choir. Both roles work the same way: read a playbook, call the CLI. Paste the relevant prompt:

**To run a project (overseer):**

> Clone `https://github.com/Weber-GeoML/Choir` to `~/.choir/checkout` if it isn't already there, then read `~/.choir/checkout/docs/agents/ORCHESTRATOR.md` and act as the orchestrator for ‹goal, sources, or owner/repo›. Follow that playbook; don't improvise steps its scripts already own.

**To contribute proofs (worker):**

> Clone `https://github.com/Weber-GeoML/Choir` to `./choir`, run `sh ./choir/scripts/join.sh ‹owner/repo›` and fix whatever it flags until it reports READY, then read `./choir/docs/agents/CONTRIBUTOR.md` and work by it. You do the proving yourself: claim a task, close the placeholder, submit.

The playbooks in [`docs/agents/`](./docs/agents/) cover both roles in full.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 11 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. {
  2. "name": "choir",
  3. "owner": { "name": "Weber-GeoML" },
  4. "plugins": [
  5. {
  6. "name": "choir",
  7. "source": "./plugin",
  8. "description": "Community-led formalization in kernel-checked proof assistants (Lean 4, Isabelle, Rocq) — start a project as overseer or join one as a contributor."
  9. }
  10. ]
  11. }
README.md · README · 67 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <p align="center">
  2. <picture>
  3. <source srcset="assets/logo/choir-lockup-dark.svg" media="(prefers-color-scheme: dark)">
  4. <img src="assets/logo/choir-lockup.svg" alt="Choir" height="96">
  5. </picture>
  6. </p>
  7. <p align="center">An open protocol for distributed multi-agent autoformalization.</p>
  8. <p align="center">
  9. <a href="https://github.com/Weber-GeoML/Choir/actions/workflows/ci.yml"><img src="https://github.com/Weber-GeoML/Choir/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
  10. <a href="./LICENSE"><img src="https://img.shields.io/badge/license-Apache%202.0-blue.svg" alt="License: Apache 2.0"></a>
  11. <img src="https://img.shields.io/badge/python-3.11%2B-blue.svg" alt="Python 3.11+">
  12. <img src="https://img.shields.io/badge/status-pre--alpha-orange.svg" alt="Status: pre-alpha">
  13. </p>
  14. Choir aims to spread the cost of a large formalization. A human overseer runs an orchestrator agent on their own machine; Choir turns that agent's plan into tasks on a GitHub repo, where any contributor can claim one and work it with their own agent, billed to their own account. Every submitted pull request is audited by Choir's deterministic trust gate before it is reviewed and merged. Works with Lean 4, Isabelle and Rocq, and with whichever agent each participant already runs. The default planner and orchestrator are easy to swap for your own, or to slot into a workflow you already have.
  15. See a demo repo: [ProbMethodCombinatorics](https://github.com/yidiq7/ProbMethodCombinatorics) is a Choir-powered autoformalization of Yufei Zhao's *Probabilistic Methods in Combinatorics* lecture notes — 285 theorems in Lean 4 with Mathlib.
  16. Read the paper: [*Choir: An Open Protocol for Distributed Multi-Agent Autoformalization*](./paper/choir.pdf).
  17. ## Getting started
  18. ### With Claude Code, GitHub Copilot CLI, or Codex
  19. Choir ships as a plugin, and this repo is the marketplace for all three
  20. harnesses.
  21. In a Claude Code or GitHub Copilot CLI session:
  22. ```text
  23. /plugin marketplace add Weber-GeoML/Choir
  24. /plugin install choir@choir
  25. ```
  26. In your shell, for Codex:
  27. ```text
  28. codex plugin marketplace add Weber-GeoML/Choir
  29. codex plugin add choir@choir
  30. ```
  31. Then say what you want in plain language:
  32. - *"Formalize ‹your theorem, paper, or chapter› with Choir"*: start or resume a project as its **overseer**.
  33. - *"Join ‹owner/repo› as a Choir contributor"*: set this machine up to prove tasks as a **worker**.
  34. Explicit invocation works too: `/choir:formalize` and `/choir:join owner/repo` in Claude Code and GitHub Copilot CLI, `$choir:formalize` and `$choir:join owner/repo` in Codex. You can also add your own instructions on top of them.
  35. ### With any other agent
  36. The plugin defines no behaviour. Its skills only run the setup scripts and defer to the playbooks, so any agent can drive Choir. Both roles work the same way: read a playbook, call the CLI. Paste the relevant prompt:
  37. **To run a project (overseer):**
  38. > Clone `https://github.com/Weber-GeoML/Choir` to `~/.choir/checkout` if it isn't already there, then read `~/.choir/checkout/docs/agents/ORCHESTRATOR.md` and act as the orchestrator for ‹goal, sources, or owner/repo›. Follow that playbook; don't improvise steps its scripts already own.
  39. **To contribute proofs (worker):**
  40. > Clone `https://github.com/Weber-GeoML/Choir` to `./choir`, run `sh ./choir/scripts/join.sh ‹owner/repo›` and fix whatever it flags until it reports READY, then read `./choir/docs/agents/CONTRIBUTOR.md` and work by it. You do the proving yourself: claim a task, close the placeholder, submit.
  41. The playbooks in [`docs/agents/`](./docs/agents/) cover both roles in full.
  42. ## License
  43. Apache-2.0. See [`LICENSE`](./LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.