CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ljg-qa

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

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/ljg-qa/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The SKILL.md body is punchy and dense, with a well-specified answer format and unusually good failure-mode documentation, but it is undermined by its bundle: both files it delegates its core workflow and design patterns to are missing, leaving the actual procedure only sketched in examples. Add an internal inconsistency (three-part vs. four-part answer) and the skill as shipped is more manifesto than executable instruction.

Suggestions

Ship Workflows/Extract.md and References/QuestionDesign.md in the bundle (or inline their essential steps and question-design patterns into SKILL.md) — the workflow section currently points at a file that does not exist.

Fix the internal inconsistency: Example 1 says "写 A 三段" while 铁律 2 mandates a strict four-part structure (结论/形式化/论证步/边界) — align the examples with the rule.

Promote the rewrite-after-scan loop from Gotchas into an explicit numbered workflow step with a validation checkpoint (generate → scan Q list → rewrite definition-answerable Qs → verify each A has all four parts).

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no basic-concept explanations, and every Gotcha is a genuine failure mode ("AI 默认会写「什么是 X」型问题"). Minor trimming is possible: the nail/chisel metaphor repeats three times ("每个 A 砸下来一枚钉子", "Q 是凿子,A 是钉子", rule 3), and "你不是"/"你是" restate one framing from two sides — that places it just below anchor 5.

4 / 5

Actionability

There is concrete guidance (the strict four-part A structure "*结论* + *形式化* + *论证步* + *边界*" with worked formalization examples like `通才 = 协调,专才 = 干活`, a copy-paste curl notification command, and a concrete denote filename pattern), but the core extraction procedure is delegated to "`Workflows/Extract.md`", which does not exist in the bundle — a key missing detail. This sits between anchor 3 (incomplete, missing key details) and anchor 4 (minor gaps only); the absent workflow file is a major gap, so 3.

3 / 5

Workflow Clarity

A rough sequence appears only in the Examples ("WebFetch 获取 → 找观点骨架 → 设计 Q 链 → 写 A 三段 → markdown 输出") and a revision loop exists in Gotchas ("生成后扫一遍,凡是 Q 能用一句定义打发的,重写"), but the promised step list ("按 `Workflows/Extract.md` 的步骤执行") points to a file that is not in the bundle, and Example 1's "写 A 三段" contradicts rule 2's four-part mandate. Sequence present with real gaps and an internal inconsistency = anchor 3, not the mostly-checkpointed flow of anchor 4.

3 / 5

Progressive Disclosure

The bundle contains only SKILL.md — neither "`Workflows/Extract.md`" nor "`References/QuestionDesign.md`" exists, so the two clearly-signaled one-level references are dangling and the content they promise (the actual workflow steps and the question-design patterns) is unreachable. Not anchor 1 (the SKILL.md itself is well-sectioned, not a wall of text) and not anchor 3 (references are well-signaled; the problem is they are broken, which defeats navigation entirely) — minimal functioning structure, so 2.

2 / 5

Total

12

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it states what the skill does in concrete terms, gives explicit bilingual trigger phrases plus a slash command, and fences off adjacent use cases (FAQ, glossary, quizzes). Only minor blemishes keep it from perfection — the single grammatical slip "a sequence of incisive questions with answered" and a what-side that is one deeply-characterized action rather than a breadth of actions.

DimensionReasoningScore

Specificity

Concrete actions and output characteristics are named: "把核心观点抽成 Q-A 对", "Question 切要害,不教科书", "Answer 简洁清晰,有形式化收口,逻辑链完整". This is richer than anchor 3 (which expects only 1-2 concrete actions), but it is one core action characterized in depth rather than the multiple distinct actions of anchor 5, so 4 fits best.

4 / 5

Completeness

Both halves are explicit: what ("把核心观点抽成 Q-A 对" with sharp questions and formalized answers whose chain reproduces the author's reasoning) and when ("Use when user says…", "Triggers when the user wants ideas extracted not as a summary but as a sequence of incisive questions"). This clearly matches the anchor-5 example's pattern of what + explicit trigger phrases, not the weaker 'when' of anchor 4.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage with synonyms in both languages and the slash command: "'问答', 'Q&A', 'QA', '提问', '抽取问题', '/ljg-qa'", plus the behavioral trigger "shares an article/paper/book and asks for Q-A extraction". Matches anchor 5's comprehensiveness (synonyms + invocation forms); no natural phrasing a user would say for this task is obviously missing.

5 / 5

Distinctiveness Conflict Risk

A clear niche (Q-A extraction as "intellectual scaffolding") with explicit negative boundaries: "NOT FOR FAQ generation, glossary creation, or comprehension quizzes". These carve-outs plus the dedicated slash-command trigger make conflict with adjacent summarization/study skills minimal, matching anchor 5.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

lijigang/ljg-skills

Path

skills/ljg-qa/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.