mathematical-enhancer
Skill4 starsChanged 7 months agoMITView on GitHub
Strengthen the mathematical substance of research papers by proposing or implementing better proofs, sharper results, cleaner derivations, and stronger formulations. Use when Codex needs to improve the mathematics itself rather than only the writing, especially by replacing brute-force arguments with better structure or identifying tractable generalizations.
In this repository8 other files it gives its agents.
- inline-paper-criticSkill
- literature-searchSkill
- manuscript-reviewSkill
- math-ocrSkill
- scientific-presenterSkill
- scientific-simplifierSkill
- tikz-figure-builderSkill
- writing-commenterSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use this skill when a manuscript's main opportunity lies in stronger mathematics: a cleaner proof strategy, a tighter bound, a more general …
- Distinctive: line 14
Read the whole paper first and identify where the mathematical content is routine, where it is fragile, and where genuine improvement seems …
- Distinctive: line 15
Look for brute-force arguments that can be replaced with more natural structure, known results, or more revealing tools.
- Distinctive: line 18
When claiming an improvement, actually work it out.
- Distinctive: line 20
If a better proof or stronger statement depends on standard results, connect the manuscript clearly to those results instead of rederiving …
- Distinctive: line 21
Keep any inline annotations compile-safe if you are working directly in LaTeX.
- Distinctive: line 28
Do not trade away clarity for abstract cleverness if the new argument becomes harder to trust.
- Distinctive: line 29
If the stronger route fails, fall back cleanly instead of leaving half-implemented sophistication behind.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Mathematical Enhancer
When to use this skill
Use this skill when a manuscript's main opportunity lies in stronger mathematics: a cleaner proof strategy, a tighter bound, a more general theorem, a resolved loose end, or a more illuminating derivation.
Workflow
- Read the whole paper first and identify where the mathematical content is routine, where it is fragile, and where genuine improvement seems possible.
- Look for brute-force arguments that can be replaced with more natural structure, known results, or more revealing tools.
- Rate candidate improvements by two axes: impact on the paper and confidence that the route is sound.
- Separate tractable improvements from speculative ones. Implement the former fully; annotate the latter as explicit suggestions.
- When claiming an improvement, actually work it out. Do not gesture at a stronger result unless you can justify the claim.
- Distinguish between improvements to mathematical substance and mere exposition. Stay focused on the mathematics.
- If a better proof or stronger statement depends on standard results, connect the manuscript clearly to those results instead of rederiving everything from scratch.
- Keep any inline annotations compile-safe if you are working directly in LaTeX.
Quality Bar
- A proposed enhancement should either improve correctness, generality, elegance, or explanatory power.
- Implement only the improvements you can justify rigorously.
- Mark speculative or difficult ideas as suggestions, not as accomplished facts.
- Do not trade away clarity for abstract cleverness if the new argument becomes harder to trust.
- If the stronger route fails, fall back cleanly instead of leaving half-implemented sophistication behind.
- High-impact, high-confidence improvements should be implemented, not merely admired.
For a more systematic pass over impact, tractability, and the boundary between implemented improvements and annotated suggestions, use references/enhancement-checklist.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

