CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

daily-papers-notes

Generate full notes for must-read recommendations, maintain concepts, and backfill links. English triggers: "generate paper notes", "batch paper notes". This is pipeline stage 3. 论文笔记生成(3 步流水线的第 3 步)。补充概念库,为推荐论文生成完整笔记, 链接回填到推荐文件;目录页默认自动刷新,git 自动化默认关闭。 触发词:"批量笔记"、"跑一下论文笔记"

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

A workflow-first skill with an exemplary validation backbone: sequenced steps, precondition stops, per-note quality checklists with fix-and-revalidate loops, and gated git/index operations. The main costs are token redundancy — the critical anti-skip guardrail is repeated three times — and a couple of unresolved script/reference paths (backfill_links.py, the duplicated concept-categories.md citation).

Suggestions

Consolidate the anti-skip/context-overflow guardrail, currently stated near-verbatim in the 铁律 block, the 笔记质量硬性要求 section, and 注意事项, into a single 禁止事项 section and reference it from Step 2 instead of repeating it.

Give backfill_links.py an explicit path the way the other scripts have one (e.g. scripts/backfill_links.py or ../_shared/backfill_links.py), since it is currently invoked bare and does not ship in the skill's bundle.

Fix the duplicated citation where both 分类规则 and 概念笔记模板 point to ../paper-reader/references/concept-categories.md — point the concept-note template at its actual file so the two references are unambiguous.

DimensionReasoningScore

Conciseness

The style is lean and imperative with no explanations of concepts Claude already knows, but the anti-skip/context-overflow guardrail is restated nearly verbatim in three places — the 铁律 block ("必读的论文全部生成笔记,一篇不能少…绝对不能默默跳过"), the 硬性要求 section ("不要因为'怕 context overflow'…就自己写个 70 行的骨架糊弄过去"), and 注意事项 ("仅为'必读'论文生成笔记…不是跳过的理由" and the repeated context-overflow procedure). Not 4 because 15+ lines of duplicated policy is more than minor trimming; not 2 because there is no concept padding and the workflow itself is efficient.

3 / 5

Actionability

Gives concrete executable commands ("python3 ../_shared/user_config.py", "python3 backfill_links.py --recommendation \"{RECOMMENDATION_PATH}\" --notes-dir \"{NOTES_PATH}\"", "cd {VAULT_PATH} && git add -A && git commit -m \"daily papers: notes YYYY-MM-DD\""), explicit variable derivations, quantitative quality gates (行数 >= 120、至少 2 处 LaTeX、至少 1 张图), and a copy-paste insertion template ("- 📒 **笔记**: [[笔记名]]"). Not 5 because backfill_links.py is invoked without a path and does not ship in the skill's bundle, and the core note generation is delegated to the external paper-reader skill.

4 / 5

Workflow Clarity

Steps 0–5 are clearly sequenced with a precondition stop (前置检查: 若任一不存在…然后停止), a per-note validation checklist with an explicit feedback loop ("若检查未通过,对照原论文修复并复核"), gated post-steps (AUTO_REFRESH_INDEXES / GIT_COMMIT_ENABLED), git pre-commit checks ("VAULT_PATH/.git 存在", "git add -A 后确实有 staged changes"), and a context-overflow recovery procedure. This batch operation has thorough validation with fix-and-revalidate loops, matching the top anchor; not 4 because checkpoints are explicit rather than merely present.

5 / 5

Progressive Disclosure

A single well-sectioned file (numbered steps, sub-steps 1a–3d) whose external references are one level deep and clearly signaled via markdown links ([language selection](../_shared/language.md), [paper-reader](../paper-reader/SKILL.md), [the English workflow](SKILL.en.md)). Not 5 because 分类规则 and 概念笔记模板 both cite the same file (../paper-reader/references/concept-categories.md) with one citation likely wrong, backfill_links.py has no resolvable location, and none of the referenced files exist in this skill's bundle; not 3 because structure and signaling are otherwise good with no inlined content that belongs in separate files.

4 / 5

Total

16

/

20

Passed

Description

83%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 bilingual description: it states concrete pipeline-stage actions and gives explicit, natural trigger phrases in both English and Chinese. The main residual weaknesses are the slightly generic "maintain concepts" phrasing and minor overlap risk with the sibling paper-reader skill that also produces paper notes.

DimensionReasoningScore

Specificity

Lists several concrete actions — "Generate full notes for must-read recommendations", "补充概念库", "链接回填到推荐文件", "目录页默认自动刷新,git 自动化默认关闭" — covering the whole pipeline stage. Not 5 because "maintain concepts" is generic and the content/format of a full note is never described; not 3 since coverage goes well beyond 1-2 actions.

4 / 5

Completeness

Clearly answers both questions: the "what" is three concrete actions (generate full notes, supplement concepts, backfill links) and the "when" is explicit trigger phrases quoted verbatim in English and Chinese. Not 4 because the "when" is not merely present — it is explicit with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Explicitly quotes natural phrases a user would say in both languages: English triggers "generate paper notes", "batch paper notes" and 触发词 "批量笔记"、"跑一下论文笔记". Not 5 because common variations/synonyms (e.g. "论文笔记" alone, "take notes on papers") are missing; not 3 since the given terms are natural and directly relevant rather than jargon.

4 / 5

Distinctiveness Conflict Risk

"This is pipeline stage 3" / "3 步流水线的第 3 步" plus the recommendation/backfill specifics carve a clear niche with paper-notes-specific triggers. Not 5 because "generate paper notes" could plausibly match the closely related paper-reader skill and there is no explicit differentiation from it; not 3 since the stage framing and backfill/index-refresh specifics make overlap unlikely beyond that one sibling.

4 / 5

Total

17

/

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

relative_links

Relative link issues: 1 missing, 3 suspicious

Warning

Total

15

/

16

Passed

Repository

huangkiki/dailypaper-skills

Path

skills/daily-papers-notes/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.