CtrlK
BlogDocsLog inGet started
Tessl Logo

academic-paper-review

Use this skill when the user requests to review, analyze, critique, or summarize academic papers, research articles, preprints, or scientific publications. Supports comprehensive structured reviews covering methodology assessment, contribution evaluation, literature positioning, and constructive feedback generation. Trigger on queries involving paper URLs, uploaded PDFs, arXiv links, or requests like "review this paper", "analyze this research", "summarize this study", or "write a peer review".

72

Quality

88%

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

77%

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

The body delivers a well-sequenced, highly actionable review methodology with a complete output template and verification checklist. Its main weaknesses are verbosity from generic review-principle guidance and a monolithic structure with no progressive disclosure to reference files.

Suggestions

Trim or remove the Review Principles, Common Pitfalls, and Quality Checklist sections that restate reviewing practices Claude already knows, keeping only task-specific guidance.

Move the full Review Output Template and the methodology/contribution rating tables into reference files (e.g., references/review-template.md, references/criteria.md) and link to them from the body to improve progressive disclosure.

Add an explicit validation checkpoint between phases (e.g., confirm all key claims are extracted before starting critical analysis) to make the workflow's feedback loops more concrete.

DimensionReasoningScore

Conciseness

The ~285-line body is mostly task-specific, but sections like Review Principles ("Be specific", "Give credit where due"), Common Pitfalls, and the Quality Checklist restate good-reviewing practices Claude already knows and could be tightened. It is not level 3 because of this padding, and not level 1 because it avoids explaining basic concepts Claude knows (e.g., what a PDF is).

2 / 3

Actionability

Provides concrete, copy-paste-ready guidance: a full review output template, a key-claims extraction format, explicit search-query examples, and rating tables with per-criterion questions. Per the code-vs-instruction note, absence of code is not penalized for an instruction-only skill whose guidance is this actionable, so it reaches level 3 rather than 2.

3 / 3

Workflow Clarity

A clearly sequenced Phase 1 → Phase 2 → Phase 3 process with a closing Quality Checklist that acts as an explicit verification checkpoint before finalizing. It is not level 2 because the sequence and checkpoint are explicit; the task is not destructive/batch, so the feedback-loop cap does not apply.

3 / 3

Progressive Disclosure

The skill is a single monolithic ~285-line document with no bundle files and no external references, so the large output template and detailed criteria tables sit inline where they could be split out. It is not level 1 because sectioning is well-organized, and not level 3 because no one-level-deep reference files exist and the >50-line body has not externalized content.

2 / 3

Total

10

/

12

Passed

Description

100%

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 is exemplary: it states concrete capabilities, provides rich natural-language triggers, explicitly answers both what and when, and occupies a clear niche. It matches the rubric's good examples that use the "Use when/Trigger on" form.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "review, analyze, critique, or summarize academic papers" plus "methodology assessment, contribution evaluation, literature positioning, and constructive feedback generation" — rather than vague language. It is not level 2 because the action list is comprehensive and specific, not a single domain action.

3 / 3

Completeness

Explicitly answers what (structured reviews covering methodology, contribution, literature, feedback) and when ("Trigger on queries involving paper URLs, uploaded PDFs, arXiv links, or requests like..."). It is not level 2 because the "when" is an explicit trigger clause, not merely implied.

3 / 3

Trigger Term Quality

Covers natural phrasings a user would actually say: "review this paper", "analyze this research", "summarize this study", "write a peer review", plus paper URLs, uploaded PDFs, and arXiv links. It is not level 2 because it includes common variations rather than only a few relevant keywords.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (academic paper peer review) with distinct triggers unlikely to fire for unrelated skills. It is not level 2 because the academic-review framing and specific trigger phrases distinguish it from generic summarization or analysis skills.

3 / 3

Total

12

/

12

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
bytedance/deer-flow
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.