mathematics-problem-solver
Skill6 starsChanged 40 days agoMITView on GitHub
Use when solving a mathematics problem and the user wants a rigorous, readable derivation with assumptions and verification.
In this repository36 other files it gives its agents.
- bioinformatics-planningSkill
- biology-literature-analysisSkill
- biology-paper-analysisSkill
- chemistry-research-analysisSkill
- skill-authorSkill
- codebase-explorerSkill
- codebase-understandingSkill
- code-reviewSkill
- debug-systematicallySkill
- implementation-plannerSkill
- implementation-reviewSkill
- ledger-tasks-yyloSkill
- test-and-verifySkill
- algorithm-learningSkill
- system-design-basicsSkill
- defensive-security-reviewSkill
- threat-modelingSkill
- data-analysisSkill
- tutorSkill
- experiment-analysisSkill
- model-evaluationSkill
- numerical-methodsSkill
- proof-solvingSkill
- physics-research-analysisSkill
- data-cleaningSkill
- data-visualizationSkill
- evidence-checkerSkill
- evidence-comparisonSkill
- experimental-planningSkill
- literature-synthesizerSkill
- reproducibility-auditSkill
- research-questionSkill
- source-verificationSkill
- api-designSkill
- frontend-planningSkill
- technical-editorSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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 14
Keep algebra and notation explicit.
- Distinctive: line 15
Check the result using substitution, limiting behavior, an alternative derivation, or another appropriate verification.
- Distinctive: line 17
If there are multiple valid methods, mention them without unnecessarily expanding the solution.
- Distinctive: line 19
Avoid decorative intuition.
- Distinctive: line 21
Do not silently change assumptions or domains.
≈ “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
Mathematics Problem Solver
Workflow
- Restate the problem precisely.
- List the known quantities, assumptions, and target.
- Select an appropriate method and briefly justify the choice.
- Solve step by step.
- Keep algebra and notation explicit.
- Check the result using substitution, limiting behavior, an alternative derivation, or another appropriate verification.
- State the final answer clearly.
- If there are multiple valid methods, mention them without unnecessarily expanding the solution.
Avoid decorative intuition. Use intuition only when it materially clarifies a difficult step.
Do not silently change assumptions or domains.
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.