CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

62

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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 body is well-organized and dense with original, skill-specific guidance (the three 铁律, four-part answer contract, output spec, and failure-mode Gotchas are all strong), and it avoids teaching Claude things it already knows. Its main defect is that the two files it delegates the core workflow and design patterns to are absent from the bundle, leaving the actual extraction procedure underspecified and the reference chain broken.

Suggestions

Create the referenced `Workflows/Extract.md` and `References/QuestionDesign.md` (or move their essential content into SKILL.md) — the body delegates its core procedure to files that do not exist in the bundle.

Add an explicit numbered workflow sequence in the body (fetch → identify argument skeleton → design Q chain → write four-part A → output org-mode) with a built-in review pass, so the skill is self-sufficient even if the external files are unavailable.

Trim the duplicated guidance between the 你不是 section and the Gotchas (e.g., the 'textbook question' failure mode is stated twice) and cut one repetition of the 凿子/钉子 metaphor.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no explanations of concepts Claude already knows, and every section (铁律, 输出, Examples, Gotchas) carries skill-specific instructions. It earns a 4 rather than 5 because of minor redundancy: the 'textbook question' failure mode is stated in both 铁律 1 ("不教科书") and Gotcha 1 ("教科书腔…重写"), and the 凿子/钉子 metaphor is repeated across the intro, 你是, and Gotchas.

4 / 5

Actionability

There is real concrete guidance — the four-part answer structure (结论/形式化/论证步/边界), formalization patterns like `A = B + C` and `通才 = 协调,专才 = 干活`, a copy-paste curl command, an exact denote filename pattern, and three input-specific examples. But the core extraction steps are delegated to `Workflows/Extract.md` ("按 Workflows/Extract.md 的步骤执行"), which does not exist in the bundle, so key execution details are missing — this fits the 'some concrete guidance but incomplete… missing key details' anchor better than the 4-anchor's 'minor gaps'.

3 / 5

Workflow Clarity

A rough sequence exists only implicitly through the Examples ("WebFetch 获取 → 找观点骨架 → 设计 Q 链 → 写 A 三段 → org-mode 输出"), and the Gotchas provide an implicit review checkpoint ("生成后扫一遍,凡是 Q 能用一句定义打发的,重写"). However, the authoritative step list lives in the missing `Workflows/Extract.md`, so the sequence has gaps and checkpoints remain implicit rather than explicit — matching the 'sequence present but checkpoints missing or implicit' anchor.

3 / 5

Progressive Disclosure

The body is well-sectioned, but both referenced files — `Workflows/Extract.md` and `References/QuestionDesign.md` — do not exist anywhere in the bundle (no references/, scripts/, assets/, or Workflows/ directories are present), so the disclosure chain is broken: an agent following the skill hits dead pointers for the workflow and for the question-design patterns. This is worse than the 3-anchor ('references present but not clearly signaled') since the references are clearly signaled but missing, and lands on the 2-anchor's broken/minimal disclosure structure.

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 and varied 'Use when'/'Triggers when' guidance covering natural synonyms in both Chinese and English, and delimits its niche with an explicit NOT-FOR clause. The only weakness is minor — the poetic framing ('每个 A 砸下一枚钉子') stands in for a plain statement of the deliverable, and the output format is not mentioned.

DimensionReasoningScore

Specificity

Lists several specific concrete actions — "把核心观点抽成 Q-A 对", "Question 切要害,不教科书", "Answer 简洁清晰,有形式化收口,逻辑链完整", "读者顺 Q 链走过…复现作者整套推理" — matching the 'several specific actions; minor gaps' anchor. Not a 5 because the deliverable/output format is not stated and the metaphor "每个 A 砸下一枚钉子" replaces a concrete statement of what is produced; not a 3 because multiple distinct concrete actions are named, not just 1-2.

4 / 5

Completeness

Explicitly answers what ("信息提问机。给一篇文章/论文/书,把核心观点抽成 Q-A 对…") and when ("Use when user says '问答', 'Q&A', 'QA', '提问', '抽取问题', '/ljg-qa', or shares an article/paper/book…Triggers when…") with concrete trigger phrases, matching the top anchor exactly. The 4-anchor ('when could be more explicit') does not apply since both 'Use when' and 'Triggers when' clauses are present and specific.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage including synonyms in two languages and the command itself: '问答', 'Q&A', 'QA', '提问', '抽取问题', '/ljg-qa', plus the behavioral trigger "shares an article/paper/book and asks for Q-A extraction". This matches the 'comprehensive coverage of natural terms including synonyms' anchor; the 4-anchor ('a few natural terms missing') fits less well since both the colloquial Chinese phrases and their English equivalents are present.

5 / 5

Distinctiveness Conflict Risk

Clear niche (extracting an author's argument into a question chain, not summarizing) with explicit negative boundaries — "NOT FOR FAQ generation, glossary creation, or comprehension quizzes — this is intellectual scaffolding, not study aids" — which sharply reduces overlap with study-aid/summary skills. Matches the 'clear niche with distinct triggers; minimal conflict risk' anchor.

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