Follow the shared workflow in ../wps-learning-workflow.md.
Inputs
- A WPS study note, explanatory draft, or review note
- Optional topic tags
- Optional textbook summary, answer key points, or reference materials
Output
A structured WPS-ready misunderstanding diagnosis result, including problem locations, correction suggestions, and small self-test questions.
What this skill should produce
This is a "diagnose + repair" type skill, not a language polisher.
It is recommended to include these parts:
overall understanding diagnosishigh-confidence errorspossible misunderstandingsmissing evidence or examplesbetter phrasing for understanding repairmini self-test
WPS-first rules
- Quote the original sentences from the user's notes as much as possible, and tell the user exactly where the problem is.
- Correction suggestions should be directly fillable back into the notes, rather than only giving abstract evaluations.
- Each key misunderstanding should preferably be accompanied by a self-test question so it can be verified immediately.
Quality rules
- Clearly distinguish clearly wrong, likely confused, and too vague to trust.
- For low-confidence issues, explain why it is only a "possible misunderstanding."
- The goal of "better phrasing" is to correct understanding, not to make sentences more flowery.
Do not use when
- The user only wants to polish the wording
- The original note content is too thin to support an effective diagnosis
- What the user really needs to do is a prerequisite knowledge gap analysis
Recommended next skill
Usually recommend:
notes-to-flashcardsprerequisite-gap-finder