PluginBench
Skill
Review
Audit score 70

ljg-qa

lijigang/ljg-skills

Extract core arguments as incisive Q-A chains that reconstruct an author's reasoning, not summaries or study aids.

What is ljg-qa?

ljg-qa transforms articles, papers, or books into structured question-answer pairs that expose the author's logical skeleton. Each question cuts to a critical junction (why, trade-off, boundary), and each answer delivers a one-line conclusion, a visual formula, the reasoning steps, and failure conditions. Use it when you need intellectual scaffolding that lets readers walk through an argument, not when you need FAQs, glossaries, or comprehension quizzes.

  • Extracts argument structure as a directed Q-chain where each question naturally leads to the next
  • Formats answers in four strict sections: conclusion, visual formula, reasoning steps, and boundary conditions
  • Avoids textbook definitions and instead targets the 'why,' trade-offs, and limits of each idea
  • Outputs in org-mode to a denote-compatible file in ~/Documents/notes/
  • Handles URLs, PDFs, and direct text input

How to install ljg-qa

npx skills add https://github.com/lijigang/ljg-skills --skill ljg-qa
Prerequisites
  • A source: URL, PDF file path, or direct text
  • Optionally, a local HTTP endpoint at localhost:31337 for voice notifications (non-blocking)
Claude Code
Cursor
Windsurf
Cline

How to use ljg-qa

  1. 1.Invoke with /ljg-qa followed by a URL, file path, or paste text directly
  2. 2.Specify the source: the skill fetches URLs, reads PDFs, or processes inline text
  3. 3.The skill extracts the argument's logical skeleton and designs a Q-chain based on dependencies, not document order
  4. 4.Each answer is formatted with conclusion, visual formula, reasoning, and boundary conditions
  5. 5.Output is written to ~/Documents/notes/ as a denote file in org-mode format

Use cases

Good for
  • Extract the core logic from a research paper to understand its method's assumptions and failure modes
  • Convert a long article into a question sequence that reveals the author's decision tree
  • Break down a book chapter into incisive Q-A pairs that expose unstated premises and trade-offs
  • Reconstruct a technical argument's reasoning path for teaching or documentation
  • Identify gaps in an author's logic by mapping the Q-chain and spotting missing links
Who it's for
  • Researchers and academics analyzing papers and arguments
  • Knowledge workers who need to internalize complex reasoning, not just summaries
  • Educators designing materials that teach thinking, not facts
  • Technical writers documenting decision rationale
  • Anyone extracting intellectual scaffolding from dense sources

ljg-qa FAQ

How is this different from FAQ generation or summarization?

FAQs answer 'what is X' questions that readers skip; summaries repackage content. ljg-qa extracts the author's reasoning chain—each Q is a pressure point that forces the A to carry weight, and the Q-chain itself mirrors the logical dependencies, not the document order.

What does 'formalization' mean here?

Formalization is a one-line visual relationship using text and simple symbols (→, =, ≠, +, ×) to compress an idea into a readable structure, like 'generalist = coordinate, specialist = execute.' It's the geometry of thought, not mathematical notation.

Can I use this for study guides or comprehension quizzes?

No. ljg-qa is intellectual scaffolding for reconstructing reasoning, not a study aid. Questions are not designed to test the reader but to expose the author's argument structure.

What if the source is a URL or PDF?

The skill handles both: it fetches URLs via WebFetch and reads PDFs (respecting page parameters). For direct text, paste it inline and skip the fetch step.

Why does the answer need four sections?

Conclusion anchors the idea; formalization makes the relationship visible; reasoning shows how to arrive there; boundary reveals where it fails. Together, they let readers replicate the author's thinking, not just memorize conclusions.

Full instructions (SKILL.md)

Source of truth, from lijigang/ljg-skills.


name: ljg-qa description: 信息提问机。给一篇文章/论文/书,把核心观点抽成 Q-A 对——Question 切要害,不教科书;Answer 简洁清晰,有形式化收口,逻辑链完整。读者顺 Q 链走过,每个 A 砸下一枚钉子,复现作者整套推理。Use when user says '问答', 'Q&A', 'QA', '提问', '抽取问题', '/ljg-qa', or shares an article/paper/book and asks for Q-A extraction. Triggers when the user wants ideas extracted not as a summary but as a sequence of incisive questions with answered. NOT FOR FAQ generation, glossary creation, or comprehension quizzes — this is intellectual scaffolding, not study aids. user_invocable: true

ljg-qa: 问答提取

读一份东西,把它的思想拆成「为什么—怎么—边界」的问答链。

读者顺着 Q 走过去,每个 A 砸下来一枚钉子。

你不是

  • 不是 FAQ 生成器("什么是 X"——读者一看就跳过)
  • 不是摘要换皮(把段落拆成"问/答"两半还是摘要)
  • 不是知识点列表(孤立的事实碰撞不出洞察)
  • 不是阅读理解题(提问不是为了考读者,是为了切中作者)

你是

把作者的论证骨架翻出来,每根骨头长成一个尖锐的问题。读者沿着 Q 链读,能复现作者的整套思路——而不是被告知结论。

三条铁律

  1. Q 切要害 —— 问的是「为什么这个解法成立」「它跟另一种做法差在哪」「它的代价是什么」「它在哪里失效」,不是「它定义是什么」。一个 Q 必须能让答案承重,不能被一句话敷衍过去。

  2. A 有形式化收口 —— 每个 A 严格四段:结论(一句话)+ 形式化(用文字 + 简单符号把思想压成一行可视关系,如 A = B + C、旧: X → 新: Y)+ 论证步(怎么想到的)+ 边界(不成立的条件)。形式化是"思想的几何",让读者一眼看出关系。

  3. Q 链有方向 —— Q 之间不是并列罗列,是「Q1 答完→Q2 自然冒出来」。读者读完整串 Q,相当于走了一遍作者的推理路径。

工作流

按 Workflows/Extract.md 的步骤执行。

设计参考

Q 怎么提、A 怎么收口的具体模式见 References/QuestionDesign.md。

Voice Notification

执行 workflow 时:

curl -s -X POST http://localhost:31337/notify \
  -H "Content-Type: application/json" \
  -d '{"message": "Running Extract in ljg-qa"}' \
  > /dev/null 2>&1 &

输出文本:

Running **Extract** in **ljg-qa**...

输出

  • 格式:org-mode(*bold*,禁 markdown 语法)
  • 路径:~/Documents/notes/
  • denote 文件名:{YYYYMMDDTHHMMSS}--qa-{核心主题 5-10 字}__qa.org

Examples

Example 1: URL

User: /ljg-qa https://example.com/article
→ WebFetch 获取
→ 找观点骨架 → 设计 Q 链 → 写 A 三段
→ org-mode 输出到 ~/Documents/notes/

Example 2: 论文 PDF

User: /ljg-qa ~/Downloads/paper.pdf
→ Read PDF(注意 pages 参数)
→ Q 抽出方法的「为什么」「代价」「边界」
→ 输出 org-mode

Example 3: 直接文本

User: 把这段抽成 Q-A: [text]
→ 跳过获取,直接抽
→ 输出

Gotchas

  • AI 默认会写「什么是 X」型问题 —— 教科书腔。生成后扫一遍,凡是 Q 能用一句定义打发的,重写
  • AI 默认会让 A 散掉 —— 没有结论句、没有边界、写成一段散文。每个 A 必须严格四段(结论 / 形式化 / 步骤 / 边界)
  • AI 默认会把「形式化」写成数学公式 —— 不是。形式化是用文字 + → = ≠ + × 这类符号压一行可视的关系,比如 通才 = 协调,专才 = 干活。是"思想的几何",不是"数学的形式"
  • AI 默认按章节顺序提问 —— 这是抄目录,不是抽思想。Q 链应该按论证依赖关系排,不按出现顺序
  • AI 默认会把 Q-A 理解成「问答游戏」 —— 不是。这里 Q 是凿子,A 是钉子。装饰性的轻问题禁止
  • AI 默认会在 A 里堆术语保平安 —— 用术语不算回答。把术语翻译成具体动作和具体物件,否则 A 没承重