CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ljg-paper

Explain research papers to readers without a specialist background: what the paper studies, what the authors contribute, how the findings follow, and what the evidence does not establish. USE WHEN the user shares an arXiv link, paper URL, PDF, local paper, or paper title, or asks to read, explain, analyze, or understand a paper. Defaults to a saved Markdown note. NOT FOR reproduction, formal peer review, benchmark tables, or literature surveys.

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-paper/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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-structured with a genuinely strong validation loop and concrete file conventions, but it is undermined by broken bundle references: the required-reading ReadingGuide.md does not exist and the template path is inconsistent. Combined with notable restatement across the intro, goals, and pitfalls sections, the skill cannot be followed end-to-end as shipped.

Suggestions

Add the missing ReadingGuide.md to the bundle (or repoint every reference to an existing file) — it is listed as 必读材料 for all three workflow routes, so its absence blocks the core workflow.

Fix the path inconsistency on line 58: the body cites references/template.md but the bundle contains references/template.org (the routing table already uses the correct .org path).

Merge the five opening philosophy paragraphs with the 三个目标 and 容易出错的地方 sections — several statements about judgment revision, avoiding forced reversals, and distinguishing verified claims from mechanism-based predictions appear two or three times.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows, but the five opening philosophy paragraphs substantially restate material that reappears later: "让读者理解证据怎样调整或巩固判断" and "区分论文验证过的结论与依据机制作出的预测" repeat goals-section lines, "无须制造戏剧性的反转" appears in both the intro and goal two, and "区分假想示例和真实实验" is echoed by the template's "自拟示例自然说明其性质". Matches anchor 3 ("mostly efficient... could be tightened") — not 2 because there is no filler or generic explanation, not 4 because the overlap between intro, goals, and pitfalls is more than minor trimming.

3 / 5

Actionability

Concrete items exist (routing table per input type, Denote filename with `date +%Y%m%dT%H%M%S`, save dir `~/Context/`, the executable `bun {skill_dir}/scripts/validate_note.ts ... --map ...` command whose flags match the script's CLI), but the primary writing instructions defer to `ReadingGuide.md`, which does not exist in the bundle, and line 58 cites `references/template.md` while the actual file is `template.org`. Fits anchor 3 ("some concrete guidance but incomplete... missing key details") — not 4 because the missing core guide makes the main workflow non-executable as written.

3 / 5

Workflow Clarity

The routing table maps each input to required materials and outputs, and 保存与检查 gives a sequenced loop with real checkpoints: write → run validator → Emacs read-back of identifier/filename/index → 4-item independent reading check → re-run script → confirm consistency, plus error handling ("验证脚本接受尚未填写阅读检查结果的记录...但会返回失败" and the fallback when the validator is unavailable). Matches anchor 4 — not 5 because the reading/writing steps themselves live in the absent ReadingGuide.md, leaving a gap in the middle of the sequence, and the template.md/template.org path inconsistency can misroute the writer.

4 / 5

Progressive Disclosure

The intended structure is good — SKILL.md stays an overview and pushes detail one level deep to ReadingGuide.md, references/paper-map.md, references/template.org, and scripts/ — but scored against the actual bundle, the most-referenced file (ReadingGuide.md, cited in the routing table, the pitfalls section, and 保存与检查) is missing entirely, and one cited path (references/template.md) does not match the real file. This is more than the "minor organization gaps" of anchor 4; broken navigation paths match anchor 3 ("references present but not clearly signaled" in the sense of not reliably resolvable).

3 / 5

Total

13

/

20

Passed

Description

92%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: concrete capability list, an explicit USE WHEN clause with natural trigger terms across formats, sensible defaults, and clear NOT FOR boundaries. The only weakness is modest synonym coverage (no "preprint"/"research paper"/".pdf").

DimensionReasoningScore

Specificity

"Explain research papers to readers without a specialist background: what the paper studies, what the authors contribute, how the findings follow, and what the evidence does not establish" lists four concrete facets of the output, plus defaults ("Defaults to a saved Markdown note") and explicit exclusions — comprehensive coverage of the capability, matching the anchor 5 example's breadth. It is not 4 because the facet list leaves no minor gaps: scope, contribution, reasoning chain, and evidence limits are all named.

5 / 5

Completeness

Explicitly answers both: "what" in the first sentence (explain studies, contributions, how findings follow, evidence limits) and "when" via a concrete "USE WHEN the user shares an arXiv link, paper URL, PDF, local paper, or paper title..." clause, further sharpened by a "NOT FOR" boundary list. This matches anchor 5 exactly; it exceeds anchor 4 because the when-clause enumerates concrete trigger phrases rather than a generic condition.

5 / 5

Trigger Term Quality

Triggers cover "arXiv link, paper URL, PDF, local paper, or paper title" plus the verbs "read, explain, analyze, or understand" — good natural coverage of what users would say. Not 5 because a few natural synonyms are missing ("research paper", "preprint", "journal article", ".pdf" as a file extension); not 3 because the listed terms are natural user phrasings, not jargon, and cover multiple input formats.

4 / 5

Distinctiveness Conflict Risk

The niche (layperson explanation of research papers) is distinct, and the explicit "NOT FOR reproduction, formal peer review, benchmark tables, or literature surveys" clause removes the most likely collision targets. "PDF" as a trigger slightly overlaps PDF-manipulation skills, but the paper context ("local paper, or paper title") and exclusion list keep conflict risk minimal — fits anchor 5; it is not 4 because the disambiguating exclusions are already explicit.

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

lijigang/ljg-skills

Path

skills/ljg-paper/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.