math-progress-monitor — Claude Code skill: assess solution strategy
math-progress-monitor — a skill that evaluates whether you're on the right track while solving a math problem and helps decide whether to keep going or switch strategies. Activates on phrases like "I'm stuck" or "is this approach working".
MIT ★ 3,951 updated 2026-01-26
npx skills add parcadei/Continuous-Claude-v3 --skill math-progress-monitor -a claude-codeWhat math-progress-monitor does
Math-progress-monitor runs a six-step structured check: reviewing attempted approaches, extracting lessons from each one, checking whether complexity is growing unexpectedly, verifying intermediate results, identifying simpler sub-problems, and assessing sunk costs. At each stage it gathers data and produces a verdict—continue, refine, pivot, or decompose the problem.
The output is an organized assessment: a summary of attempts with takeaways, a complexity check (what you expected vs what's happening), verification checkpoints, and a clear recommendation. When pivoting is needed, the skill proposes a concrete alternative method with reasoning for why it could work. The logic draws on Schoenfeld's metacognitive problem-solving framework.
What it helps with
- Recognize when an approach has stopped producing progress
- Detect whether complexity is ballooning instead of simplifying
- Decide between continuing and switching strategy
- Review attempt history and extract transferable insights
- Break a hard problem into simpler stepping stones
Example prompts for the agent
- I've been stuck on this integral for an hour—am I going the right direction?
- Check my progress: I've tried u-substitution and integration by parts
- The complexity keeps growing—should it? Help me figure this out
How to install math-progress-monitor
1Skills CLI (Vercel)
npx skills add parcadei/Continuous-Claude-v3 --skill math-progress-monitor -a claude-code2Manually: put the files in place
~/.claude/skills/math-progress-monitor/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/math-progress-monitor/
1Skills CLI (Vercel)
npx skills add parcadei/Continuous-Claude-v3 --skill math-progress-monitor -a codex2Manually: put the files in place
.agents/skills/math-progress-monitor/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add parcadei/Continuous-Claude-v3 --skill math-progress-monitor -a cursor2Manually: put the files in place
.cursor/skills/math-progress-monitor/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install parcadei/Continuous-Claude-v3 .claude/skills/math/math-progress-monitor2Manually: put the files in place
.github/skills/math-progress-monitor/SKILL.md1Skills CLI (Vercel)
npx skills add parcadei/Continuous-Claude-v3 --skill math-progress-monitor -a gemini-cli2Platform CLI
gemini skills install https://github.com/parcadei/Continuous-Claude-v3 --path .claude/skills/math/math-progress-monitorManually: put the files in place
.devin/skills/math-progress-monitor/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about math-progress-monitor
How do I install math-progress-monitor in Claude Code?
Run npx skills add parcadei/Continuous-Claude-v3 --skill math-progress-monitor -a claude-code in your terminal, then open ~/.claude/skills/math-progress-monitor/SKILL.md.
What does math-progress-monitor do?
It evaluates your problem-solving progress through six check-ins: attempt history, lessons learned, whether complexity is rising as expected, how to verify intermediate steps, and whether breaking the problem down would help. It recommends whether to persist or change course.
When does this skill activate?
Automatically triggered by phrases like "I'm stuck", "is this working", "should I try something else", "verify my progress", or "is this getting too complicated".
Source text
SKILL.md · MIT
--- name: math-progress-monitor description: Metacognitive check-ins during problem solving - detects when to pivot or persist --- # Math Progress Monitor ## When to Use Trigger on phrases like: - "am I on the right track" - "is this approach working" - "I'm stuck" - "should I try something else" - "verify my progress" - "check my reasoning" - "is this getting too complicated" Use mid-work to assess whether to continue, pivot, or decompose (Schoenfeld's metacognitive control). ## Process Run a structured progress assessment: ### 1. Inventory attempts **Ask:** "What have you tried so far?" - List each approach - Order by when attempted - Note time spent ### 2. Extract learnings **Ask:** "What did each attempt tell you?" - Even failures provide information - What was ruled out? - What patterns emerged? ### 3. Complexity check **Ask:** "Is complexity growing faster than expected?" - Warning signs: - More terms than you started with - New variables appearing - Calculation getting messier - Normal: complexity stays flat or decreases ### 4. Spot-check verification **Ask:** "Can you verify any intermediate results?" - Run numerical examples - Check limiting cases - Dimensional analysis ### 5. Decomposition check **Ask:** "Is there a simpler sub-problem to solve first?" - Identify dependencies - Find stepping stones - Reduce scope ### 6. Sunk cost assessment **Ask:** "What would abandoning this approach cost?" - Time already spent (irrelevant) - Insights that transfer (relevant) - Probability of success if continue ## Key Questions to Ask 1. What have you tried? (inventory) 2. What did you learn? (extract) 3. Is it getting simpler or harder? (complexity) 4. Can you check a piece? (verify) 5. What's the smallest step? (decompose) 6. Should you pivot? (decide) ## Output Format ``` Progress Assessment: Status: [On track / Hitting resistance / Should pivot] Attempts Summary: 1. [Approach] -> [Outcome/Learning] 2. [Approach] -> [Outcome/Learning] Complexity Check: - Expected: [what should this look like] - Actual: [what it actually looks like] - Verdict: [Normal / Warning / Abandon] Verification Points: - [Intermediate result to check] - [Numerical test case] Recommendation: [Continue / Modify approach / Switch strategy / Decompose / Get more info] If Pivoting: - Alternative: [specific new approach] - Why it might work: [reasoning] ``` ## Example Interaction ``` User: I've been trying to evaluate this integral for an hour Claude: Let's do a progress check. Q1: What have you tried? > u-substitution with u = sin(x), then integration by parts twice. Q2: What did each tell you? > Substitution made it longer. Parts created a cycle. Q3: Complexity now vs start? > Much worse. Started with 3 terms, now have 8. Complexity Check: - Expected: Should simplify or stay similar - Actual: 3 terms -> 8 terms after 2 techniques - Verdict: WARNING - likely wrong approach Let me verify an intermediate step... [Runs sympy on original integral] This integral has closed form using: - Beta function (special function) - Or contour integration Recommendation: PIVOT Your algebraic approaches won't simplify this pattern. Alternative Approach: 1. Recognize: integral of sin^m(x) * cos^n(x) 2. Use Beta function identity 3. Or convert to complex exponentials Related Skills: - complex-analysis/contour-integrals - numerical-methods/numerical-integration Would you like the Beta function approach, or get a numerical answer first to verify? ``` ## Co-activates When user is stuck, suggest: - **math-intuition-builder** - reset understanding - **math-model-selector** - if framework was wrong - **math-mode** - for verification computations - **Relevant domain skill** - for alternative approach
© parcadei · MIT · parcadei/Continuous-Claude-v3