agentleFS
odinfreeodinfree/storm-ecdsa-harness/skills/computer-algebra-oracles/SKILL.md

computer-algebra-oracles

Skill4 starsChanged 20 days agoMITView on GitHub

Route exact algebra, finite-field, coding-theory, polynomial-system, group-theory and number-theory questions through SageMath, Magma, OSCAR, Singular, GAP/GUAVA, PARI/GP or Hecke, with replayable evidence and an independent check.

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. About 0 are common, 14 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈14

    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
  1. Distinctive:

    Use an exact computer-algebra system to expose structure, compute a witness, or falsify a claim.

    line 8
  2. Distinctive:

    Read references/routing.md when more than one system is plausible or a specialist feature is required.

    line 12
  3. Distinctive:

    Start with SageMath for broad interactive exploration and cross-domain glue.

    line 14
  4. Distinctive:

    Prefer OSCAR for integrated exact algebra and geometry, and Singular for ideals, Groebner bases, elimination, and polynomial systems.

    line 15
  5. Distinctive:

    Prefer GAP/GUAVA for finite groups, automorphisms, equivalence, and coding-theory constructions.

    line 16
  6. Distinctive:

    Prefer PARI/GP or Hecke for algebraic-number-theory computations.

    line 17
  7. Distinctive:

    Use Magma when a named Magma algorithm, database, or independent implementation supplies a concrete advantage and a licensed route is …

    line 18
  8. Distinctive:

    Do not infer mathematical independence merely because two front ends have different names.

    line 20
  9. Distinctive:

    Use exact literals and exact types.

    line 26
  10. Distinctive:

    Check load-bearing results through a semantically equivalent route with a genuinely distinct implementation or translate them into the …

    line 28
  11. Distinctive:

    Read references/receipts.md before handing a result to another lane or treating a computation as exhaustive.

    line 31
  12. Distinctive:

    Stop and repair the model if the mathematical object in the program is not demonstrably equivalent to the stated object.

    line 35
  13. Distinctive:

    Stop calling a route independent when its decisive computation shares the same backend or generated artifact.

    line 36
  14. Distinctive:

    Stop before using an online calculator, licensed installation, paid service, or external upload unless that action is authorized.

    line 37

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Computer algebra oracles

Use an exact computer-algebra system to expose structure, compute a witness, or falsify a claim. Produce a replayable mathematical receipt; do not silently promote oracle output into a proof.

Route by structure

Read references/routing.md when more than one system is plausible or a specialist feature is required.

  • Start with SageMath for broad interactive exploration and cross-domain glue.
  • Prefer OSCAR for integrated exact algebra and geometry, and Singular for ideals, Groebner bases, elimination, and polynomial systems.
  • Prefer GAP/GUAVA for finite groups, automorphisms, equivalence, and coding-theory constructions.
  • Prefer PARI/GP or Hecke for algebraic-number-theory computations.
  • Use Magma when a named Magma algorithm, database, or independent implementation supplies a concrete advantage and a licensed route is available.

Do not infer mathematical independence merely because two front ends have different names. Record shared backends such as FLINT, Singular, GAP, or PARI.

Execution contract

  1. State the ring, field, characteristic, coefficient domain, variable order, quotient, and normalization conventions before computing.
  2. Probe capability with a small representative calculation. Binary presence or a successful import is not a workload check.
  3. Use exact literals and exact types. Any floating-point approximation must be explicitly bounded and cannot certify an exact claim by itself.
  4. Save minimal executable input, tool and package versions, seed when used, and output sufficient to replay the claim.
  5. Check load-bearing results through a semantically equivalent route with a genuinely distinct implementation or translate them into the target proof system.
  6. Report the narrowest status supported: explored, witnessed, falsified on the declared domain, independently reproduced, or formally proved.

Read references/receipts.md before handing a result to another lane or treating a computation as exhaustive.

Stop conditions

  • Stop and repair the model if the mathematical object in the program is not demonstrably equivalent to the stated object.
  • Stop calling a route independent when its decisive computation shares the same backend or generated artifact.
  • Stop before using an online calculator, licensed installation, paid service, or external upload unless that action is authorized.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.