What problem does it solve? Product teams building algorithm-practice platforms (Baekjoon/LeetCode-style) often equate an Accepted verdict with real learning, leading to shallow progress metrics like solved counts and streaks. This Skill helps teams distinguish AC from understanding, mastery, retention, and transfer, and design review, revisit, and weak-concept loops grounded in learning science. ## Core Features & Use Cases - Learning State Ladder & Signals: Classifies progress from Exposed through Transferable, and ranks evidence signals (hint level used, mistake diagnosed, re-solve after delay, variation solved) by strength. - Mastery Criteria & Review Design: Defines goal-specific mastery rules (interview prep, competitive programming, fundamentals) and lightweight post-AC review prompts with adaptive depth. - Learning Science Reference: Covers SM-2, FSRS, Leitner schedulers, spacing and interleaving effects, Bloom's taxonomy, worked-example fading, and calibration countermeasures like predict-then-check. - Use Case: A team debating whether a hinted solve should count as solved uses this Skill to define assisted-solve handling, revisit policy, and retention metrics for their MVP. ## Quick Start Ask the Skill to define mastery criteria and a spaced-repetition revisit policy for your algorithm practice product's MVP.