# proof-readability

proof-readability edits a math proof that already passed verification so a reader can follow it in one go: reordered steps, added lead-ins, fixed references. The claims stay as they are.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf (Devin Desktop), Claude.ai · ★ 240 repo stars
- Author: franklee16
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/franklee16/academic-research-skills/tree/HEAD/theory-skills/theorist-toolbox-master/skills/proof-readability/SKILL.md
- Updated: 2026-09-18
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/proof-readability

## What it does

It runs late in the chain. The proof exists and has already been accepted, and this skill goes over the write-up: move steps around, add a lead-in, repair references and typos. Nothing in the argument changes. Claims are not strengthened, weakened or quietly simplified.

The work is split into six layers, and the first two take the whole proof at once. One covers layout: the statement and a sketch sit in the main text, the formal argument moves to an appendix, each lemma gets a sentence about what it says and why it is there, and an assembled proof ends with an explicit wrap-up. The other covers navigation: the opening line names the method, a long proof is broken into named steps, and an announced count of cases has to match what follows. Layers three through six are local edits.

A real gap does not get patched. When a step cannot be derived from the stated assumptions, editing stops and that step goes back to the prover, because a silent fix would undermine the verification that already happened. Inside a co-math project the skill is wired into the pipeline: `project-coordinator` opens a `W{NNN}-readability-{slug}` workstream after approval, `prover` carries it out in readability mode, and `paper-reviewer` checks only that the content survived. Scope is the approved proofs named in `instructions.md`.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add franklee16/academic-research-skills --skill proof-readability -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/proof-readability/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/proof-readability/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add franklee16/academic-research-skills --skill proof-readability -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/proof-readability/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add franklee16/academic-research-skills --skill proof-readability -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/proof-readability/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install franklee16/academic-research-skills theory-skills/theorist-toolbox-master/skills/proof-readability
```

2. **Manually: put the files in place**
- File: `.github/skills/proof-readability/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add franklee16/academic-research-skills --skill proof-readability -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/franklee16/academic-research-skills --path theory-skills/theorist-toolbox-master/skills/proof-readability
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/proof-readability/SKILL.md` — The legacy .windsurf/skills/ path still works

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/franklee16/academic-research-skills/tree/HEAD/theory-skills/theorist-toolbox-master/skills/proof-readability/SKILL.md

## When to use it
- turn a verified proof into something a reader can follow in one sitting
- merge two near-identical derivations into one lemma used twice
- give a long proof named steps and a closing recap
- check that the case count announced at the start matches the body
- restate a lemma so it reads on its own outside the surrounding prose

## Example prompts
- Polish the proof of Theorem 2 — presentation only, don't touch the math.
- Run a readability pass over the proofs in Appendix C.
- Rewrite Lemma 4 so it can be read on its own.

## Similar
- [proof-orchestrator](https://affpapa.org/en/nevibecode/skills/proof-orchestrator.md) — skill · 260 installs
- [readability](https://affpapa.org/en/nevibecode/skills/readability.md) — skill · 595 installs
- [readability-check](https://affpapa.org/en/nevibecode/skills/readability-check.md) — skill · 127 installs
- [lean-formalize](https://affpapa.org/en/nevibecode/skills/lean-formalize.md) — skill · 103 installs
- [Text Classifier — Topic Categories & Readability](https://affpapa.org/en/nevibecode/mcp/text-classifier-topic-categories-readability.md) — MCP server · 4595 installs
- [math-proof-judge](https://affpapa.org/en/nevibecode/agents/math-proof-judge.md) — subagent · ★ 47914 repo stars

From the same set: [franklee16/academic-research-skills](https://affpapa.org/en/nevibecode/by/franklee16/academic-research-skills.md) — 98 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
