Resume Tailor
reactive-resume/reactive-resume
Tailors one resume to one specific job posting. An agent skill from reactive-resume/reactive-resume.
Start or resume a Choir formalization project as its overseer — formalize a theorem, paper, textbook chapter, or folder of sources in Lean 4, Isabelle, or Rocq by orchestrating AI contributor agents…
Apache-2.0Auto-check passed
Install Formalize
$ npx skills add Weber-GeoML/Choir --skill formalize -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Weber-GeoML/Choir formalize --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/Weber-GeoML/Choir.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugin/skills/formalize .claude/skills/formalize && 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 "formalize" agent skill from https://github.com/Weber-GeoML/Choir/tree/main/plugin/skills/formalize into .claude/skills/formalize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "formalize", 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/Weber-GeoML/Choir/tree/main/plugin/skills/formalizeType 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 Weber-GeoML/Choir --skill formalize -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Weber-GeoML/Choir formalize --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Weber-GeoML/Choir.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugin/skills/formalize .agents/skills/formalize && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "formalize" agent skill from https://github.com/Weber-GeoML/Choir/tree/main/plugin/skills/formalize into .agents/skills/formalize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "formalize", 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 Weber-GeoML/Choir --skill formalize -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Weber-GeoML/Choir formalize --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Weber-GeoML/Choir.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugin/skills/formalize .cursor/skills/formalize && 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 "formalize" agent skill from https://github.com/Weber-GeoML/Choir/tree/main/plugin/skills/formalize into .cursor/skills/formalize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "formalize", 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/Weber-GeoML/Choir.git --path plugin/skills/formalize--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 Weber-GeoML/Choir --skill formalize -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Weber-GeoML/Choir formalize --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Weber-GeoML/Choir.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugin/skills/formalize .gemini/skills/formalize && 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 "formalize" agent skill from https://github.com/Weber-GeoML/Choir/tree/main/plugin/skills/formalize into .gemini/skills/formalize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "formalize", 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 Weber-GeoML/Choir formalizeInstalls 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 Weber-GeoML/Choir --skill formalize -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Weber-GeoML/Choir.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugin/skills/formalize .github/skills/formalize && 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 "formalize" agent skill from https://github.com/Weber-GeoML/Choir/tree/main/plugin/skills/formalize into .github/skills/formalize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "formalize", 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 Weber-GeoML/Choir --skill formalize -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Weber-GeoML/Choir formalize --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Weber-GeoML/Choir.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugin/skills/formalize .opencode/skills/formalize && 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 "formalize" agent skill from https://github.com/Weber-GeoML/Choir/tree/main/plugin/skills/formalize into .opencode/skills/formalize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "formalize", 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
formalize- GitHub stars
- 114
- Token cost
- ~626 tokens
- SKILL.md length
- 269 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Start or resume a Choir formalization project as its overseer — formalize a theorem, paper, textbook chapter, or folder of sources in Lean 4, Isabelle, or Rocq by orchestrating AI contributor agents…
- Works in 4 steps: Understand the goal. Take it from the… → Ensure a Choir checkout at… → Machine setup. When resuming a project… → …
- The user wants to formalize something with Choir
- Calls gh
- Run/resume a Choir project they oversee
What it does
Formalize is an agent skill from Weber-GeoML/Choir. Start or resume a Choir formalization project as its overseer — formalize a theorem, paper, textbook chapter, or folder of sources in Lean 4, Isabelle, or Rocq by orchestrating AI contributor agents behind a deterministic verification gate. Use when the user wants to formalize something with Choir or run/resume a Choir project they oversee.
Its SKILL.md is about 630 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: An open protocol for distributed multi-agent autoformalization. The licence is Apache-2.0.
When your agent uses it
- The user wants to formalize something with Choir
- Run/resume a Choir project they oversee
Example prompts
- “/formalize”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Understand the goal. Take it from the arguments and the
- Ensure a Choir checkout at ~/.choir/checkout. If missing
- Machine setup. When resuming a project whose repo you already know
- **Read ~/.choir/checkout/docs/agents/orchestrator-setup.md and
What it can do on your machine
Read from SKILL.md and the folder at commit 762d1ce. 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
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
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
Formalize loads about 626 tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 269 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); files beside SKILL.md are not scanned.
SKILL.md
The full file from Weber-GeoML/Choir at commit 762d1ce, republished under its Apache-2.0 licence (© Weber-GeoML). 269 words, ~626 tokens.
Download SKILL.mdSave it as
.claude/skills/formalize/SKILL.md (or your agent's skills folder).- name
- formalize
- description
- Start or resume a Choir formalization project as its overseer — formalize a theorem, paper, textbook chapter, or folder of sources in Lean 4, Isabelle, or Rocq by orchestrating AI contributor agents behind a deterministic verification gate. Use when the user wants to formalize something with Choir or run/resume a Choir project they oversee.
- argument-hint
- [goal, sources, or owner/repo]
Formalize with Choir (overseer)
Choir is an open protocol for community-led formalization in kernel-checked proof assistants: contributor agents prove tasks on their own machines and LLM accounts, and a deterministic gate verifies every submission before merge. You are about to act as the project's orchestrator on the overseer's behalf: plan, publish tasks, review contributions, merge per the automation level.
This skill is a pointer. The behavioral contract lives in Choir's playbook — never improvise a step the playbook or its scripts already own.
Understand the goal. Take it from the arguments and the conversation: a theorem, a paper or textbook chapter, a folder of sources, or an existing Choir project repo to resume. Treat the current folder as the project's sources unless told otherwise.
Ensure a Choir checkout at
~/.choir/checkout. If missing:gh repo clone Weber-GeoML/Choir ~/.choir/checkoutIf
ghis missing or unauthenticated, have the user install it and rungh auth loginfirst.Machine setup. When resuming a project whose repo you already know:
sh ~/.choir/checkout/scripts/orchestrator-init.sh <owner/repo>For a fresh project, the playbook establishes the repo: follow
~/.choir/checkout/docs/agents/orchestrator-setup.md's bootstrapping procedure (it drivesscripts/new-project.shand the configuration interview), then runorchestrator-init.shwith the newowner/repo.Read
~/.choir/checkout/docs/agents/orchestrator-setup.mdandORCHESTRATOR.mdand drive the project by them, starting with the configuration interview. Bootstrap or resume as the playbook determines, then run the plan/publish/review/merge loop in this session at the project's configured automation level.If the user names another tool to plan or orchestrate with ("use AutoformBot for orchestrating"), also read
~/.choir/checkout/docs/agents/integrations/README.mdand that tool's note, and run the loop with the tool in the slots the note names.
© Weber-GeoML, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugin/skills/formalize of Weber-GeoML/Choir.
Open the folder on GitHubat commit 762d1ce
Compare with similar skills
Formalize 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 |
|---|---|---|---|---|---|---|
| Formalize this skillWeber-GeoML/Choir | 114 | — | ~626 | Automated safety check: Pass | Apache-2.0 | |
| Resume Tailorreactive-resume/reactive-resume | 44k | — | ~8.3k | Automated safety check: Pass | MIT | |
| Resume Bullet Writerreactive-resume/reactive-resume | 44k | — | ~8k | Automated safety check: Pass | MIT | |
| Reactive Resume Builderreactive-resume/reactive-resume | 44k | — | ~2k | Automated safety check: Pass | MIT | |
| Resume Content Guidereactive-resume/reactive-resume | 44k | — | ~11k | Automated safety check: Warn | MIT | |
| Resume Version Managerdavila7/claude-code-templates | 33k | 2 repos | ~2.1k | Automated safety check: Pass | MIT |
Similar skills
Resume Bullet Writer
reactive-resume/reactive-resume
Turns resume duties into truthful impact bullets. An agent skill from reactive-resume/reactive-resume.
Reactive Resume Builder
reactive-resume/reactive-resume
Builds resumes as valid JSON for the open-source Reactive Resume app by interviewing you, and can track job applications through its MCP tools.
Resume Content Guide
reactive-resume/reactive-resume
Decides what information belongs on a resume or CV, what to leave off and in what order, and audits an existing resume against those norms.
Resume Version Manager
davila7/claude-code-templates
Track different resume versions, maintain a master resume, and manage tailored variants.
Resume Modern
nexu-io/open-design
Modern minimal resume, single A4 page, ready for print or PDF export.
More from Weber-GeoML/Choir
Join
Weber-GeoML/Choir
Join a Choir formalization project as a contributor — set up this machine and start proving tasks (Lean 4, Isabelle, or Rocq) with your own agent on your own LLM account.
Questions about Formalize
What does Formalize do?
Start or resume a Choir formalization project as its overseer — formalize a theorem, paper, textbook chapter, or folder of sources in Lean 4, Isabelle, or Rocq by orchestrating AI contributor agents…. Formalize is an agent skill from Weber-GeoML/Choir. Start or resume a Choir formalization project as its overseer — formalize a theorem, paper, textbook chapter, or folder of sources in Lean 4, Isabelle, or Rocq by orchestrating AI contributor agents behind a deterministic verification gate.
When should I use Formalize?
Formalize fits situations like: the user wants to formalize something with Choir; run/resume a Choir project they oversee.
How do I install Formalize in Claude Code?
Run `npx skills add Weber-GeoML/Choir --skill formalize -a claude-code`. Or copy the skill folder (plugin/skills/formalize in Weber-GeoML/Choir) into .claude/skills/formalize in your project. Claude Code loads it when a task matches its description.
How do I install Formalize in Codex?
Run `npx skills add Weber-GeoML/Choir --skill formalize -a codex`. Or copy the skill folder (plugin/skills/formalize in Weber-GeoML/Choir) into .agents/skills/formalize in your project. Codex loads it when a task matches its description.
Can I use Formalize 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 Weber-GeoML/Choir --skill formalize -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/formalize, .gemini/skills/formalize, .github/skills/formalize and .opencode/skills/formalize in your project.
What does Formalize need to run?
Going by SKILL.md and its folder, Formalize needs the command-line tools its instructions call (gh).
Does Formalize access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Formalize 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. Review the folder before installing.
What licence does Formalize use?
Formalize is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Formalize use?
About 626 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Formalize?
Skills that share tags, products or a category with Formalize: Resume Tailor (reactive-resume/reactive-resume, 44k stars), Resume Bullet Writer (reactive-resume/reactive-resume, 44k stars), Reactive Resume Builder (reactive-resume/reactive-resume, 44k stars) and Resume Content Guide (reactive-resume/reactive-resume, 44k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Formalize?
Weber-GeoML (a GitHub organization) maintains it in Weber-GeoML/Choir, which has 114 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 1, 2026.
Source: Weber-GeoML/Choir on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.