본문으로 건너뛰기
cccskills
무료GitHub에 공개

math-progress-monitor

Review progress while solving a math problem by organizing previous attempts, checking intermediate results, and assessing growing complexity. The skill recommends whether to continue, adjust the approach, switch strategies, or tackle a smaller problem first.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Metacognitive check-ins during problem solving - detects when to pivot or persist

설치 방법 보기

이럴 때 유용합니다

  • Review an approach when stuck on a math problem
  • Assess calculations that keep getting more complicated
  • Check intermediate results
  • Decide whether to switch strategies

포함된 파일(1)

  • SKILL.md3.7 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Coordinate background agents through saved files, keeping lengthy work transcripts out of the main conversation. It defines how to pass results between agents, monitor progress, and verify completed work with tests.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Keeping long agent transcripts out of the main conversation
  • Passing research and plans between agents through files
  • Checking for stalled background agents
parcadei/Continuous-Claude-v33.9천2026년 1월 27일 업데이트

Delegate implementation, file reading, and testing to separate agents, then bring concise summaries back to the main conversation. The rules explain when delegation helps and when a small edit is better handled directly.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Implementing a feature across multiple files
  • Completing a specific phase of an implementation plan
  • Delegating feature development and testing
parcadei/Continuous-Claude-v33.9천2026년 1월 27일 업데이트

Organize implementation work across research, planning, validation, implementation, and review agents. Each stage passes files to the next, while implementation starts with failing tests and the main conversation coordinates the workflow.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Dividing implementation work among specialized agents
  • Checking a plan against research before implementation
  • Writing failing tests before implementing changes
parcadei/Continuous-Claude-v33.9천2026년 1월 27일 업데이트

Connect Agentica SDK agents to Claude Code CLI through a proxy, an intermediary server. Use setup and debugging guidance to address file permissions, streamed responses, result formatting, and agents reporting success without performing the requested operations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Connecting Agentica agents to Claude Code tools
  • Investigating file write and edit permission errors
  • Debugging streaming and REPL response formats
parcadei/Continuous-Claude-v33.9천2026년 1월 27일 업데이트

Consult Agentica APIs when building workflows where multiple AI agents cooperate. This reference covers eleven coordination patterns, agent tracking, shared state, handoffs, and ways to combine results, with pointers to detailed API specifications.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Choose a coordination pattern for multiple agents
  • Check pattern constructors and methods
  • Implement custom coordination patterns
parcadei/Continuous-Claude-v33.9천2026년 1월 27일 업데이트

Write clearer instructions for Agentica and REPL agents by specifying roles, file operations, and output formats. Includes templates for dividing research, coordinating specialists, reviewing solutions, and passing results between agents through files.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Clarifying instructions for reading and editing files
  • Dividing research among multiple agents
  • Passing findings and plans between agents
parcadei/Continuous-Claude-v33.9천2026년 1월 27일 업데이트

parcadei의 스킬 모두 보기

이 스킬의 문제 신고