CtrlK
BlogDocsLog inGet started
Tessl Logo

academic-paper-reviewer

Simulates academic peer review, evaluating papers across Originality, Methodology, Results, and Writing to provide Major/Minor Revision recommendations with actionable feedback. Triggers when a user asks to "review my paper," "simulate peer review," or "give my paper a peer review.

64

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/academic-paper-reviewer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

The body is a well-structured, thorough review framework with a concrete output template, but it is verbose (redundantly restating knowledge Claude already has), lacks a worked example, and keeps all content inline in one monolithic file with no progressive disclosure. These keep every dimension at the middle anchor.

Suggestions

Tighten conciseness by removing the 'Common issue examples' blocks (which restate the criteria above them) and trimming criteria that restate general peer-review knowledge Claude already has, keeping only skill-specific calibration guidance.

Add at least one short worked example — a sample paper snippet mapped to the exact output template — so the actionability of the output format is concrete rather than only implied by a blank template.

Move the per-dimension review criteria and issue examples into a single one-level-deep reference file (e.g., criteria.md) linked from a concise overview, so the main SKILL.md acts as a lean entry point with well-signaled progressive disclosure.

DimensionReasoningScore

Conciseness

The ~233-line body restates general peer-review knowledge Claude already has ('Are there confounding variables or biases?', 'Is the sample size adequate?') and the 'Common issue examples' sections redundantly restate the preceding criteria, so it is mostly efficient but could be tightened considerably.

2 / 3

Actionability

The output-format template is concrete and copy-paste ready (exact headers, 🔴/🟡 markers, table columns, score ranges), but the dimension criteria are descriptive rather than prescriptive and there is no worked input-to-output example showing the format in action.

2 / 3

Workflow Clarity

A logical flow exists (Input Requirements → Four Dimensions → Severity → Output Format) and the Revision Priority Checklist provides a checklist, but the dimensions are presented as parallel categories rather than an explicitly sequenced review process, so the sequence is implicit.

2 / 3

Progressive Disclosure

The skill is a single monolithic ~233-line file with no bundle files and no external references; it is well-organized with clear headers, but per-dimension criteria and examples that could live in separate reference files are all inline, so the over-50-lines small-skill exemption does not apply.

2 / 3

Total

8

/

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 strong across all dimensions: it states concrete capabilities in third person, provides natural trigger phrases, and clearly answers both what the skill does and when to use it. It occupies a distinct niche with low conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in third person — 'Simulates academic peer review, evaluating papers across Originality, Methodology, Results, and Writing to provide Major/Minor Revision recommendations with actionable feedback' — naming the four dimensions and the output type rather than vague language.

3 / 3

Completeness

Explicitly answers both what it does (peer-review simulation across four dimensions yielding Major/Minor recommendations) and when to use it via an explicit 'Triggers when a user asks to...' clause, which is equivalent to a 'Use when...' trigger.

3 / 3

Trigger Term Quality

Includes natural phrases a user would actually say — 'review my paper,' 'simulate peer review,' 'give my paper a peer review' — giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Academic peer-review simulation is a clear niche and the triggers are specific to that context, making it unlikely to fire for unrelated 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
zebbern/claude-code-guide
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.