CtrlK
BlogDocsLog inGet started
Tessl Logo

paper-analysis-assistant

根据arXiv论文网址自动下载PDF并进行多维度分析,包括文本提取、词频分析、语音播报、播客对话生成、交互式网页、PPT、总结图和引用分析

60

Quality

71%

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

68%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 content is well-structured and highly actionable with executable commands and real referenced bundle files, but the multi-step batch workflow lacks validation checkpoints and repeats script listings across sections. Tightening redundancy and adding verification steps would lift the weakest dimensions.

Suggestions

Add validation/verification checkpoints (e.g. confirm each output file exists and is non-empty before proceeding, or verify PDF extraction succeeded) to lift workflow_clarity above the batch-operation cap of 3.

Consolidate the script listing — keep full parameter details in '操作步骤' and have '资源索引' and '使用示例' reference rather than re-list them — to reduce redundancy and improve conciseness.

Specify concrete output formats for the agent-driven steps (step 5 dialogue script schema, step 8 summary image layout) so all steps carry equally actionable guidance.

DimensionReasoningScore

Conciseness

The body is efficient and avoids explaining concepts Claude already knows, but script invocations are repeated across '操作步骤', '资源索引', and '使用示例', which could be trimmed.

4 / 5

Actionability

Concrete executable bash commands with explicit parameters are given for every script, but agent-driven steps 5 (dialogue script) and 8 (summary image) lack concrete format/spec guidance.

4 / 5

Workflow Clarity

A clear 9-step sequence with parameters and optional branches is present, but there are no validation/verification checkpoints; since this is a batch operation generating many outputs, workflow clarity is capped at 3.

3 / 5

Progressive Disclosure

Well-organized sections with one-level-deep, clearly signaled references to real bundle files (scripts/*.py, references/stopwords.txt); minor redundancy from listing scripts in three places keeps it just below 5.

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

The description conveys a rich, concrete capability set and a distinct arXiv-paper niche, but lacks any explicit 'when to use' trigger clause, which limits its completeness. Trigger term coverage is good but could be broader.

Suggestions

Add an explicit trigger clause such as '当用户提供 arXiv 论文网址或论文 PDF 文件并希望进行多维度分析时使用' to answer 'when' and lift completeness above 3.

Include natural synonyms and file extensions (e.g. '.pdf', '论文 PDF', 'arXiv 链接') to broaden trigger term coverage toward 5.

Keep third-person voice consistent; the current phrasing is already third person — maintain this when adding the trigger clause.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — '自动下载PDF', '文本提取', '词频分析', '语音播报', '播客对话生成', '交互式网页', 'PPT', '总结图', '引用分析' — giving comprehensive coverage of capabilities.

5 / 5

Completeness

Clearly states 'what' (download PDF and multi-dimension analysis) but provides no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

Natural terms like 'arXiv论文网址', 'PDF', '论文' are present and would be said by users, but common synonyms and file extensions (.pdf) are missing.

4 / 5

Distinctiveness Conflict Risk

Scoped specifically to arXiv papers with PDF download and multi-format analysis, giving a clear niche with minimal overlap risk against other skills.

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

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