verify-and-repair-algebra
From the author
Check and repair rational polynomial identities with ResiMind when an expansion looks wrong, two algebraic answers disagree, or an agent needs exact coefficient evidence before using a result. Applies to bounded polynomial algebra, not calculus, arbitrary theorem proving or engineering certification.
Install
npx skills add 1105216375-alt/resimind --skill verify-and-repair-algebra -a claude-code
Installs to .claude/skills/verify-and-repair-algebra/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 85
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- proof-checkerwanshuiyin/Auto-claude-code-research-in-sleepRigorous mathematical proof verification and fixing workflow. Reads a LaTeX proof, identifies gaps via cross-model review (external reviewer backend, ultra reasoning), fixes each gap with full derivations, re-reviews, and generates an audit report. Use when user says "检查证明", "verify proof", "proof check", "审证明", "check this proof", or wants rigorous mathematical verification of a theory paper.Science★ 18K
- proof-refactoring-assistantArabelaTso/Skills-4-SERestructure and improve Isabelle or Coq proofs to enhance readability, modularity, and maintainability without changing semantics. Use when proofs are long and monolithic, have repeated patterns, use unclear naming, lack documentation, or when the user asks to refactor, clean up, improve, or reorganize their formal proofs.Engineering★ 259
- reality-verificationtzachbon/smart-ralphThis skill should be used when the user asks to "verify a fix", "reproduce failure", "diagnose issue", "check BEFORE/AFTER state", "VF task", "reality check", "check test quality", "mock-only tests", or needs guidance on verifying fixes by reproducing failures before and after implementation, or detecting mock-heavy test anti-patterns.Testing★ 562
- rethinkOvid/paadUse when options, a recommendation, or an already-chosen approach are on the table and the reasoning under them has not been independently checked — especially when the case rests on cited documentation, remembered behavior, or premises nobody verified. Not for generating alternatives, and not for critiquing a spec, which is /pushback.Planning★ 143
- verifyoliver-kriska/claude-elixir-phoenixVerify a rewrite slice against its obligations: preflight, capture fresh test evidence, audit translationese and parity, update the ledger. Use after /phx:work finishes a rewrite slice, or before claiming parity.Testing★ 571
- blender-iterative-refinementifBars/blender-agent-studioRun an opt-in evidence-backed second pass on a complete Blender deliverable. Use when the user explicitly asks to critique, improve, repair, iterate, or apply a practice-makes-perfect loop; when a benchmark fixture explicitly requires retained before-and-after evidence; or when a completed candidate must be improved without regressing its existing technical or visible qualities.Other★ 94
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in