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

misconception-detector

Use when diagnosing a repeated conceptual mistake and designing a targeted correction loop to replace the faulty mental model.

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

설치 방법 보기

포함된 파일(3)

  • SKILL.md3.9 KB
  • examples.md2.3 KB
  • README.md782 B

SKILL.md(원문)

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

Purpose

Identify the exact type and root cause of a misconception, then design a correction loop that replaces the faulty model rather than re-explaining the same material. Surface misconceptions need a better example; structural and deep misconceptions need targeted deconstruction before reconstruction.

Activation

  • Learner makes the same conceptual error repeatedly. check-understanding or challenge-generator flagged a pattern. Learner's explanation reveals a plausible but incorrect mental model. Learner believes they understand but consistently applies it wrong.
  • Skip if: one-time execution mistake with no conceptual root. Concept hasn't been taught yet → teach-concept. Issue is environmental → debug-teacher.
  • Routing: run before check-understanding recheck when persistent error detected. Pair with socratic-mode for deep misconceptions. Log to weak-area-tracker.

Inputs

  • Learner's incorrect statement/reasoning, concept being misunderstood, prior error history, correct mental model.

Misconception Types

  • Surface: wrong terminology/label, underlying model partially correct → fix with clear definition + contrast example.
  • Structural: wrong causal model — knows vocabulary but has mechanism wrong → fix with step-by-step worked trace.
  • Deep: fundamentally wrong model conflicting with multiple related concepts → fix with socratic-mode to expose contradiction first, then correct.

Workflow

  1. Classify — Determine type (surface/structural/deep) with supporting evidence. State classification before proceeding.
  2. Articulate — Restate the learner's incorrect model precisely and without judgment. Confirm with learner that this represents their belief.
  3. Root Cause — Identify what produced the misconception: overgeneralization, ambiguous terminology, bad analogy, missing prerequisite.
  4. Deconstruct — Surface: correct definition + contrast. Structural: step-by-step mechanism trace. Deep: socratic-mode questions to expose contradiction, then provide correct model.
  5. Install Correct Model — State the replacement model explicitly. Provide a concrete example that only makes sense under the correct model. Contrast with what the incorrect model would have predicted.
  6. Verify — Ask learner to apply corrected model to a novel scenario with explanation. If error persists: escalate to socratic-mode.
  7. Reinforce — Log to weak-area-tracker. Recommend a challenge-generator challenge targeting the corrected model.

Rules

  • DO: classify before correcting — type determines strategy.
  • DO: restate and confirm the learner's incorrect model before correcting it.
  • DO: provide an explicit replacement model, not just negation ("that's wrong").
  • DO: require learner to apply corrected model to a novel case before closing.
  • DON'T: correct by repeating the original explanation louder or longer.
  • DON'T: assume the misconception — confirm with learner first.
  • DON'T: repeat the same correction strategy 3 times — if second attempt fails, escalate to socratic-mode.
  • DON'T: frame misconceptions as failures — they're signs of engaged learning.

Output

Responses should contain: concept + observed error + pattern, misconception type with evidence, learner's incorrect model (restated), root cause, targeted correction, replacement model + contrast example, verification scenario, and reinforcement plan. Format naturally.

Checklist

  • Misconception type classified with evidence.
  • Learner's incorrect model restated and confirmed.
  • Replacement model explicitly provided with contrast example.
  • Verification requires novel application.

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

Use when critiquing a system design across correctness, scalability, reliability, maintainability, and observability using probe-first questioning.

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

yugash007/edu-agent-skills102026년 5월 19일 업데이트

Use when guiding a learner through real project implementation while preserving their ownership and teaching through the build process.

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

yugash007/edu-agent-skills102026년 5월 19일 업데이트

Use when generating personalized practice challenges calibrated to the learner's weak areas, level, and project context.

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

yugash007/edu-agent-skills102026년 5월 19일 업데이트

Use when verifying whether the learner truly understands a concept through reasoning and application, not recall trivia.

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

yugash007/edu-agent-skills102026년 5월 19일 업데이트

Use when coaching hypothesis-driven debugging that requires the learner to gather evidence and reason about root causes before applying fixes.

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

yugash007/edu-agent-skills102026년 5월 19일 업데이트

deep-dive

무료

Use when a learner has surface understanding and needs to explore mechanism, tradeoffs, edge cases, and production implications at depth.

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

yugash007/edu-agent-skills102026년 5월 19일 업데이트

yugash007의 스킬 모두 보기

이 스킬의 문제 신고