Agent skill

mathematical-proof-logic

The logical structure of mathematical proof -- how first-order logic, natural deduction, and semantic reasoning combine to produce rigorous mathematical arguments. Covers the logical skeleton of direct proof, contraposition, contradiction, cases, and induction; the role of definitions, lemmas, and theorems; how informal mathematical prose maps to formal deductive structure; and the difference between proof-as-object and proof-as-activity. Use when the question is "why is this a valid proof?" rather than "what proof technique applies?

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill mathematical-proof-logic --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 13 KB
Bundled scripts: none
Path: skills/analysis/mathematical-proof-logic/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Mathematical Proof Logic Mathematical proof is the oldest and most rigorous form of argumentation humans have developed. Its rigor comes from logic: every legitimate step in a proof must correspond to a rule of inference in some underlying logical system -- usually first-order logic with a background theory like ZFC set theory or Peano arithmetic. This skill is about the logical structure of proof, not the pragmatic heuristics for finding one. It answers the question "what makes this sequence of sentences a valid proof?" rather than "what trick should I try?" The complementary `proof-techniques` skill in the math department covers the latter. **Agent affinity:** godel (metamathematics), tarski (semantic grounding), russell (Principia heritage) **Concept IDs:** log-predicate-logic, log-proof-techniques, log-deductive-reasoning, log-mathematical-proof ## Proof as Logical Object A mathematical proof is, formally, a finite sequence of sentences in a formal language such that every sentence is either: 1. An axiom of the background theory, 2. A previously established theorem (lemma), or 3. Inferred from earlier sentences by an inference rule of the logic. The final sentence is the theo

What's inside
Steps it walks through
  1. Proof as Logical Object
  2. The Underlying Logic
  3. Proof Structures as Logical Patterns
  4. Direct proof
  5. Proof by contrapositive
  6. Proof by contradiction (reductio ad absurdum)
  7. Proof by cases
  8. Proof by induction
  9. Existence proofs
  10. Uniqueness proofs
  11. Definitions, Axioms, Lemmas, Theorems
  12. Informal Prose and Its Formal Shadow
  13. Worked Example: A Classical Proof
  14. Common Errors in Proofs
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the mathematical-proof-logic skill do?

The logical structure of mathematical proof -- how first-order logic, natural deduction, and semantic reasoning combine to produce rigorous mathematical arguments. Covers the logical skeleton of direct proof, contraposition, contradiction, cases, and induction; the role of definitions, lemmas, and theorems; how informal mathematical prose maps to formal deductive structure; and the difference between proof-as-object and proof-as-activity. Use when the question is "why is this a valid proof?" rather than "what proof technique applies?

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill mathematical-proof-logic --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going