CtrlK
BlogDocsLog inGet started
Tessl Logo

daily-papers

每日论文推荐的一句话总入口。用户说“今日论文推荐”“过去3天论文推荐”“过去一周论文推荐” “最近3天论文”“看看这周有啥论文”时使用。 内部会自动串联论文抓取、推荐生成、重点论文笔记三步,无需用户手动拆开。

68

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

72%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 clear, actionable orchestration skill with good structure and appropriate progressive disclosure. Its main weakness is the total lack of validation/verification steps across a multi-file generation pipeline.

Suggestions

Add a lightweight validation checkpoint after each sub-skill call (e.g. confirm the recommendation file exists and notes were generated before reporting success), with a retry-on-failure loop.

De-duplicate the trigger-phrase list and merge the redundant 'don't run sub-steps manually' guidance from 重要约束 and 自动化 into one place to tighten conciseness.

Provide one concrete example of the final one-line user report so the output is unambiguous.

DimensionReasoningScore

Conciseness

Mostly lean and well-structured, but trigger phrases are listed twice and the 'don't make the user run sub-steps manually' point is restated across both 重要约束 and 自动化.

4 / 5

Actionability

Provides a concrete time-range mapping table and explicit slash commands to call in order, plus specific report items; minor gaps are the absence of any error-handling guidance and no example output sentence.

4 / 5

Workflow Clarity

Steps are clearly numbered and sequenced, but there are no validation checkpoints anywhere in a pipeline that batch-generates recommendation and note files, which caps workflow clarity at 3.

3 / 5

Progressive Disclosure

Under 50 lines, single-purpose, no bundle files needed, with well-organized sections and the sub-skills appropriately kept as separate external skills.

5 / 5

Total

16

/

20

Passed

Description

91%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 entry-point description with excellent natural trigger phrases and explicit what/when coverage. It could sharpen the boundary against the sibling sub-skills it chains together.

Suggestions

Add a brief clause distinguishing this umbrella skill from the three sub-skills (e.g. 'use the sub-skills directly only when the user wants a single step'), to reduce overlap-driven mis-routing.

Replace the meta framing "一句话总入口" with one more concrete capability verb to lift specificity.

DimensionReasoningScore

Specificity

Names the domain and several concrete pipeline actions ("串联论文抓取、推荐生成、重点论文笔记三步"), with minor gaps since the actions are stage names rather than fully elaborated operations.

4 / 5

Completeness

Explicitly answers both what (chains fetch→review→notes) and when ("用户说……时使用") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Quotes many natural user phrases including colloquial variants ("今日论文推荐"、"最近3天论文"、"看看这周有啥论文"), giving comprehensive coverage of the terms a user would actually say.

5 / 5

Distinctiveness Conflict Risk

Has distinct colloquial triggers for a clear niche, but minor overlap risk with the sibling daily-papers-* sub-skills it orchestrates, which it only weakly disambiguates in the description itself.

4 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
huangkiki/dailypaper-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.