agentsclimarketplace

Math strategy studio

Skill r-irbe/proof-skills/skills/math-strategy-studio

USE FOR: Strategic mathematical thinking — brainstorming, problem decomposition, proof strategy design, creative hypothesis generation, and mathematical intuition development. Use when facing novel formalization challenges, when standard approaches fail, when exploring connections between domains, or when the theorem specification needs creative mathematical insight. The creative counterpart to the systematic research-council and review-council skills. DO NOT USE FOR: strategy analysis methodology generally (use @applied-strategy-analysis); research synthesis (use @research-synthesis-engine); Lean specification (use @lean-specification). TRIGGERS: strategy studio, brainstorming, problem decomposition, proof strategy, creative hypothesis, mathematical intuition.From its SKILL.md

Install
npx -y skills add r-irbe/proof-skills --skill math-strategy-studio

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.0 KB, 646 tokens by cl100k_base, as published. Nobody here has run it

Mathematical Strategy Studio

Creative mathematical thinking and proof strategy design for Lean 4 formalization.


Routing

  • USE FOR: Strategic mathematical thinking — brainstorming, problem decomposition, proof strategy design, creative hypothesis generation, and mathematical intuition development. Use when facing novel formalization challenges, when standard approaches fail, when exploring connections between domains, or when the theorem specification needs creative mathematical insight. The creative counterpart to the systematic research-council and review-council skills.
  • DO NOT USE FOR: strategy analysis methodology generally (use @applied-strategy-analysis); research synthesis (use @research-synthesis-engine); Lean specification (use @lean-specification).
  • TRIGGERS: strategy studio, brainstorming, problem decomposition, proof strategy, creative hypothesis, mathematical intuition.

Workflow

  1. Frame the strategy question: brainstorming, problem decomposition, proof-strategy design, hypothesis generation, or intuition-building.
  2. Pick the matching method from the body; surface 3-5 candidate strategies for evaluation.
  3. Score the candidates; recommend the top strategy with explicit assumptions and fallbacks.
  4. Hand off: to @lean-specification for proof-strategy execution, to @research-council for hypothesis vetting, to @lean-zettelkasten.

Recovery & STOP

  • STOP if the question is applied-strategy (not mathematical) — delegate to @applied-strategy-analysis.
  • STOP if no candidate scores above the belief floor — escalate to @research-council.
  • STOP if the question is about synthesising prior work — delegate to @research-synthesis-engine.

Handoffs

  • Predecessors: agent:gateway, skill:lean-research.
  • Successors: skill:lean-specification, skill:research-council, skill:lean-zettelkasten.

Detailed reference

Full content for math-strategy-studio lives in references/math-strategy-studio-handbook.md. Load that file when the skill is convened; the SKILL.md only carries the dispatch contract and the parts index.

SectionTopic
Part 1Strategy Design Framework
Part 2Proof Strategy Patterns
Part 3Creative Techniques
Part 4Brainstorming Protocols
Part 5Problem Decomposition for Complex Theorems
Part 6Mathematical Intuition Development
Part 7Research Council Integration

See also

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.