verify-math
Skill39 starsChanged 8 months agoMITView on GitHub
Verify algebra, calculus, identities, equation solving, and nontrivial derivation steps with SymPy. Use when a mathematical result needs programmatic checking.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- flonat/flonat-researchtheir own version, first seen Nov 3, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- flonat/flonat-research★ 150same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- accessible-pdfSkill
- anonymize-repoSkill
- arxiv-metadataSkill
- arxiv-prepSkill
- bib-doi-toggleSkill
- check-refsSkill
- critique-figuresSkill
- critique-manuscriptSkill
- doi-bibtexSkill
- latex-cleanupSkill
- openalexSkill
- presubmit-checksSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 8
Use the bundled script to check nontrivial symbolic transformations.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Verify mathematics with SymPy
Use the bundled script to check nontrivial symbolic transformations. When the user requests a fully audited derivation, verify each substantive step. Do not add tool calls after routine arithmetic or notation changes.
State relevant domains and assumptions before interpreting a result. SymPy may return expressions that are equal only under conditions involving signs, branches, singularities, or parameter values. Report those conditions instead of treating every simplified equality as a universal proof.
Commands
# Check two expressions are equal
./verify.py eq "EXPR1" "EXPR2"
# Compute derivative
./verify.py diff "EXPR" [VAR]
# Compute integral
./verify.py int "EXPR" [VAR]
# Simplify/expand expression
./verify.py simp "EXPR"
# Solve equation (EXPR = 0)
./verify.py solve "EXPR" [VAR]Paths are relative to this skill's directory.
Expression Syntax
- Powers:
x**2orx^2 - Functions:
sin(x),cos(x),exp(x),log(x),sqrt(x) - Pre-defined symbols:
x y z t s n k a b c C - Reserved symbols handled:
E I S N O(treated as variables, not SymPy constants)
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.

