Index of every page on this site: llms.txt
All skills
lijigang avatar

/ljg-qa

@76b5fb9
by lijiganglijigang/ljg-skills7.8k stars
865
Run it yourself

信息提问机。给一篇文章/论文/书,把核心观点抽成 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.

Use this Skill: https://skilld.dev/gh/lijigang/ljg-skills/ljg-qa

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈162 tokens for metadata: the name and description. ≈873 when used: this file. ≈2.9k more on demand in 2 files.

Description uses 5.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈475 characters, or 5.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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**...

输出

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

Examples

Example 1: URL

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

Example 2: 论文 PDF

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

Example 3: 直接文本

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

Gotchas

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

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 alert26d3 checks · Risk SAFE
  • Gen Agent Trust Hub26d

    The skill is designed to extract structured Q&A chains from articles, papers, and books. The primary security considerations involve its ability to ingest untrusted data from the web or PDF files, which introduces a risk of indirect prompt injection. Additionally, the skill performs local system operations, such as writing files to the user's documents folder and executing a local network command via curl to provide status notifications.

  • Socket26d

    No alerts

  • Snyk26d

    Risk: CRITICAL · 2 issues

Signed by skilld at 76b5fb9. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 weeks ago.

Activeupdated 4 weeks ago
user_invocable
true

README badge

README badge for lijigang/ljg-skills/ljg-qa