agentleFS
wpsnotewpsnote/wpsnote-skills/skills/misconception-finder/SKILL.md

misconception-finder

Skill184 starsChanged 7 months agoMITView on GitHub

当用户希望检查一篇 WPS 学习笔记里是否存在理解错误、概念混淆、逻辑跳步或表述过虚时使用此 Skill。适合课后自查、复习前校正、讲给别人之前自检,以及“我是不是以为自己懂了其实没懂”的场景。

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow the shared workflow in ../wps-learning-workflow.md.

    line 9

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

WPS Misconception Finder 2.0

Follow the shared workflow in ../wps-learning-workflow.md.

Inputs

  • 一篇 WPS 学习笔记、解释稿或复习笔记
  • 可选的主题标签
  • 可选的教材摘要、答案要点或参考资料

Output

A structured WPS-ready 误解诊断结果,包含问题定位、修正建议和小型自测问题。

What this skill should produce

这是一个“诊断 + 修复”型 skill,不是语言润色器。

建议包含这些部分:

  1. overall understanding diagnosis
  2. high-confidence errors
  3. possible misunderstandings
  4. missing evidence or examples
  5. better phrasing for understanding repair
  6. mini self-test

WPS-first rules

  • 尽量引用用户笔记里的原句,告诉用户具体哪里出了问题。
  • 修正建议要能直接回填到笔记里,而不是只给抽象评价。
  • 每个关键误解最好都附一条自测题,方便立刻验证。

Quality rules

  • 明确区分 clearly wrong、likely confused、too vague to trust。
  • 低置信度的问题要说明为什么只是“可能误解”。
  • “better phrasing” 的目标是修正理解,不是把句子写得更华丽。

Do not use when

  • 用户只是想润色文字表达
  • 原始笔记内容太薄,无法支撑有效诊断
  • 用户真正要做的是前置知识缺口分析

Recommended next skill

Usually recommend:

  • notes-to-flashcards
  • prerequisite-gap-finder

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.