CtrlK
BlogDocsLog inGet started
Tessl Logo

paper-analysis-assistant

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

60

Quality

70%

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

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-organized skill with executable examples and clean progressive disclosure, weakened mainly by script-list redundancy across three sections and absent validation checkpoints in the batch workflow. Trimming the duplicated resource index and adding verification steps would raise the lower dimensions.

Suggestions

Remove or collapse the 资源索引 section since it duplicates the script names and purposes already given in 操作步骤, keeping the body leaner.

Add validation/verification checkpoints between batch steps (e.g. confirm the PDF downloaded and text extracted non-empty before downstream generation).

Merge 使用示例 into the step list or keep only one canonical command reference to reduce triple repetition of the same scripts.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence (no concept padding) and is well structured, but 操作步骤, 资源索引, and 使用示例 each re-list the same scripts and parameters, creating redundancy that could be tightened.

2 / 3

Actionability

The 使用示例 section provides fully executable, copy-paste-ready bash commands with concrete arguments and example paths, and each step lists exact script parameters.

3 / 3

Workflow Clarity

Steps are clearly numbered (1–8) with optional branches, but this batch operation has no validation or verification checkpoints between steps, so workflow_clarity is capped at 2 per the batch-operations guideline.

2 / 3

Progressive Disclosure

Clear overview sections with one-level-deep, well-signaled markdown links to real bundle files (all 8 scripts and references/stopwords.txt verified present), and content is appropriately split into separate script files.

3 / 3

Total

10

/

12

Passed

Description

67%

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 specific, niche-scoped description that clearly conveys capabilities, but it omits explicit 'when to use' trigger guidance and has limited trigger-term coverage. Adding a 'Use when...' clause would lift completeness and trigger_term_quality.

Suggestions

Append a 'Use when...' clause naming natural triggers, e.g. '当用户提供 arXiv 论文网址或论文 PDF、需要下载或多维度分析论文时使用'.

Broaden trigger terms to include common variations like '论文分析', 'paper analysis', '学术文献', '.pdf'.

Keep the existing action list but pair it with the explicit usage trigger so both 'what' and 'when' are answered.

DimensionReasoningScore

Specificity

The description lists many concrete actions — '自动下载PDF', '文本提取', '词频分析', '语音播报', '播客对话生成', '交互式网页', 'PPT', '总结图', '引用分析' — matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

It thoroughly answers 'what' through the enumerated analysis actions, but lacks any 'Use when...' clause or explicit trigger guidance, so 'when' is only implied and completeness is capped at 2 per the guidelines.

2 / 3

Trigger Term Quality

It contains relevant natural terms like 'arXiv论文网址' and 'PDF', but coverage is thin and missing common variations (e.g. '论文分析', 'paper', '学术') a user might say.

2 / 3

Distinctiveness Conflict Risk

The arXiv-paper-to-multi-format-analysis niche is distinct and unlikely to conflict with other skills, with the 'arXiv论文网址' trigger clearly scoping it.

3 / 3

Total

10

/

12

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.