CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

paper-analysis-assistant

其他高等院校教师与数据科学家在追踪前沿学术时,当需要深度解析arXiv论文,用此技能可一键下载PDF并自动生成词频分析、双人播客、交互式网页、PPT演示与总结图,将数小时的文献阅读转化为多媒体内容,效率提升十倍!

Quality

75%

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

Quality

Content

65%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 well-structured, largely executable pipeline skill: real scripts with accurately documented CLI parameters, clear step ordering with conditional branches, and exemplary one-level-deep reference coverage of the bundle. Its weaknesses are the complete absence of validation checkpoints in a batch-generation workflow, an unspecified dialogue-script input format, and significant duplication of the same commands across three sections.

Suggestions

Specify the dialogue script format in step 5 (the '角色: 台词' / 'Role: line' format that dialogue_to_podcast.py parses) so the agent can generate a valid input without opening the script.

Add validation checkpoints between steps, e.g. verify the PDF downloaded and is non-empty before extraction, check the extracted txt is non-empty before analysis, and confirm each output file exists after generation.

Eliminate the triple repetition: keep the parameterized step list as the canonical reference and reduce 资源索引/使用示例 to only non-duplicated information (e.g. the quick-analysis variant).

DimensionReasoningScore

Conciseness

Per-step content is tight (script + parameters, no concept explanations), but the same script inventory appears three times: the 操作步骤 section, the 资源索引 section ('下载脚本:见 [scripts/download_pdf.py]...用途:下载 arXiv PDF'), and the 示例 1 bash block repeating the full command sequence verbatim. This ~30-line redundancy could be tightened into one canonical form.

3 / 5

Actionability

Every step names a concrete script with its parameters and 示例 1 provides copy-paste-ready bash commands; I verified the documented flags match the actual argparse interfaces (e.g. download_pdf.py --url/--output, dialogue_to_podcast.py --dialogue/--output). Gaps: step 5 says '根据论文内容生成双人对话脚本' and the notes only say '需确保对话格式正确' without ever specifying the '角色: 台词' (Role: line) format the script parses, and step 8's agent-generated summary image has no format/tool guidance.

4 / 5

Workflow Clarity

The 9 steps are clearly numbered and sequenced with explicit branches ('当 用户直接提供 PDF 文件:跳过步骤 1'), but there are zero validation checkpoints — no verification that the PDF downloaded correctly, that extracted text is non-empty before analysis, or that each output file was produced. Per the rubric's cap, a batch multi-output pipeline without validation cannot score above 3.

3 / 5

Progressive Disclosure

The body is an ~88-line overview delegating implementation to the bundle: the 资源索引 section links all 9 bundle files (8 scripts + references/stopwords.txt) with a stated purpose each, and I confirmed every referenced path exists. References are exactly one level deep with no nesting, matching the clear-overview anchor.

5 / 5

Total

15

/

20

Passed

Description

75%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 solidly specific description with an explicit capability list and a present (if persona-wrapped) trigger clause, clearly distinguishing the arXiv-analysis niche. Its deductions come from marketing over-claims ('一键', '效率提升十倍'), an audience-framed rather than input-framed trigger, and missing common synonyms like '研报' and '文献'.

Suggestions

Remove the over-claims and buzzwords ('一键', '自动', '效率提升十倍!') and state the capabilities plainly in third person.

Replace the persona framing with an explicit input-based trigger clause, e.g. '当用户提供 arXiv 网址或论文 PDF,或要求解析论文/研报/文献时使用', to sharpen the 'when' and lift completeness.

Add natural synonym triggers ('论文', '研报', '文献', 'paper') to broaden keyword coverage toward users who don't say 'arXiv'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — '一键下载PDF并自动生成词频分析、双人播客、交互式网页、PPT演示与总结图' covers six distinct outputs with comprehensive coverage. Held at 4 rather than 5 because of over-claims the guidelines penalize: '一键' (one-click), '自动' (automatically), and '效率提升十倍' (tenfold efficiency) are marketing assertions, not capabilities.

4 / 5

Completeness

The 'what' is explicit (download PDF; generate six output types) and a 'when' clause is present ('当需要深度解析arXiv论文' — equivalent to 'Use when'), so it clears the 3-cap for missing trigger guidance. Not 5 because the when is buried in persona framing ('其他高等院校教师与数据科学家在追踪前沿学术时') that narrows and muddles the trigger, instead of a crisp clause like the body's own '用户提供 arXiv 论文网址或论文 PDF 文件'.

4 / 5

Trigger Term Quality

Contains the natural terms a user would say: 'arXiv论文', '深度解析', 'PDF', '词频', '播客', 'PPT', '文献阅读'. Not 5 because common variations are missing — '研报' (used in the skill's own examples), '文献', 'paper', or file extensions — so keyword coverage is good but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

The arXiv-paper-analysis-to-multimedia niche is clear with distinct triggers (arXiv, 论文解析, 词频, 播客), making wrong-skill triggering unlikely. Minor overlap remains with dedicated PPT-generation, audio/TTS, and webpage skills for requests like '把这篇论文做成PPT', fitting the 'mostly distinct, minor overlap' anchor.

4 / 5

Total

16

/

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

anbeime/skill

Path

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