scientific-simplifier
Skill4 starsChanged 7 months agoMITView on GitHub
Simplify scientific code, LaTeX, and technical prose while preserving exact behavior, results, and meaning. Use when Codex needs to remove duplication, reduce unnecessary abstraction, clean up AI-generated bloat, or make a research codebase or manuscript clearer without changing its substance.
In this repository8 other files it gives its agents.
- inline-paper-criticSkill
- literature-searchSkill
- manuscript-reviewSkill
- mathematical-enhancerSkill
- math-ocrSkill
- scientific-presenterSkill
- tikz-figure-builderSkill
- writing-commenterSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
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 scientific project feels bloated, repetitive, over-abstracted, or harder to read than it should be, but the …
- Distinctive: line 16
Remove duplication only after verifying the repeated pieces serve the same purpose, not merely a similar shape.
- Distinctive: line 17
Prefer direct, idiomatic language and native constructs over custom wrappers or ornamental abstractions.
- Distinctive: line 20
Stop when the code or prose reads like a deliberate design, not a pile of edits.
- Distinctive: line 24
Do not collapse distinct scientific regimes or assumptions into one helper just to save lines.
- Distinctive: line 25
Do not replace clear control flow with clever one-liners.
- Distinctive: line 26
Do not remove notation, equations, or comments that carry real meaning.
- Distinctive: line 27
Prefer smaller, safer edits over sweeping rewrites when the verification surface is large.
- Distinctive: line 28
If a simplification changes results, semantics, or narrative emphasis, revert it.
≈ “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
Scientific Simplifier
When to use this skill
Use this skill when a scientific project feels bloated, repetitive, over-abstracted, or harder to read than it should be, but the underlying behavior and mathematics must remain unchanged.
Workflow
- Inspect the target area before editing. Identify what is duplicated, indirect, dead, formulaic, or misleadingly complex.
- Preserve outputs and meaning. Treat simplification as an expression change, not a behavior change.
- Remove duplication only after verifying the repeated pieces serve the same purpose, not merely a similar shape.
- Prefer direct, idiomatic language and native constructs over custom wrappers or ornamental abstractions.
- Tighten scientific prose aggressively: delete filler openings, redundant transitions, vague significance claims, and conversation leakage.
- Simplify one logical piece at a time and verify after each change with tests, compilation, or equivalent checks.
- Stop when the code or prose reads like a deliberate design, not a pile of edits.
Quality Bar
- Do not collapse distinct scientific regimes or assumptions into one helper just to save lines.
- Do not replace clear control flow with clever one-liners.
- Do not remove notation, equations, or comments that carry real meaning.
- Prefer smaller, safer edits over sweeping rewrites when the verification surface is large.
- If a simplification changes results, semantics, or narrative emphasis, revert it.
For a broader cleanup pass, use references/simplification-checklist.md when the codebase is large, the prose shows obvious AI artifacts, or you need a more systematic review of duplication and abstraction.
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.

