mistake-analyzer
Analyze incorrect answers from text, documents, or images; identify root causes of mistakes; classify error types; explain correct reasoning; and generate targeted improvement suggestions, wrong-question notebook entries, or similar practice questions. Use when the user provides a wrong answer, asks why they were wrong, uploads a marked question, or wants help reviewing mistakes.
Profile →npx skills add mingchen666/Reviva --skill mistake-analyzer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Mistake Analyzer ## Purpose This skill helps the agent analyze mistakes in learning and assessment contexts. It identifies: - what went wrong; - where the reasoning failed; - why the mistake happened; - what the correct reasoning should be; - how the user can avoid similar mistakes; - what practice should come next. The goal is to turn mistakes into targeted learning opportunities. --- ## When t
What does the mistake-analyzer skill do?
Analyze incorrect answers from text, documents, or images; identify root causes of mistakes; classify error types; explain correct reasoning; and generate targeted improvement suggestions, wrong-question notebook entries, or similar practice questions. Use when the user provides a wrong answer, asks why they were wrong, uploads a marked question, or wants help reviewing mistakes.
How do I install it?
Run `npx skills add mingchen666/Reviva --skill mistake-analyzer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mingchen666/Reviva, a repository with 181 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.