CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

peer-review

Conduct professional peer reviews for papers or theses, providing structured evaluations and improvement suggestions; use when you need a pre-submission assessment, an internal review, or academic quality control.

Quality

74%

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 ./scientific-skills/Academic Writing/peer-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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-organized, actionable instruction skill with a clear workflow, explicit evaluation criteria, and functioning one-level-deep bundle references. Its main weaknesses are token duplication between the inline example and the template asset, and an unexplained structural mismatch between the two template versions.

Suggestions

Remove the ~50-line inline worked example (or replace it with a 5-10-line excerpt) and rely on assets/peer_review_template.md, eliminating the duplication that hurts conciseness and token efficiency.

Align the inline example's structure with the actual template asset (Summary/Strengths/Weaknesses/Major/Minor vs. Overall Evaluation/Methods and Results) so users get one consistent output shape.

Trim the "Key Features" section, which restates the Implementation Details workflow, and fold any unique signals into "When to Use".

Add an explicit final quality-check step to the workflow (e.g., verify every issue has a rationale and an actionable fix, per the guide's Quality Check) instead of delegating validation to references/guide.md.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but the ~50-line inline worked template duplicates assets/peer_review_template.md, and the "Key Features" section restates the Implementation Details workflow. Not 2: there is no over-explanation of concepts Claude already knows — the padding is confined to duplication.

3 / 5

Actionability

Concrete guidance throughout: a five-step workflow with explicit criteria (novelty, significance, rigor, evidence alignment, reproducibility), major/minor classification rules, and a fillable template. Not 5: the inline example template diverges structurally from the actual asset template (Summary/Strengths/Weaknesses vs. Overall Evaluation/Methods and Results), leaving the reader to reconcile two different output shapes.

4 / 5

Workflow Clarity

The sequence (read for global understanding → overall evaluation → methods and results verification → issue organization → recommendation) is clearly ordered with per-step specifics. Not 5: validation exists only as a delegated checklist in references/guide.md rather than an explicit quality-check step in the workflow itself.

4 / 5

Progressive Disclosure

Both referenced files (assets/peer_review_template.md, references/guide.md) exist, are one level deep, and are clearly signaled in a dedicated "Templates and References" section. Not 3: despite the inline example duplicating template content, the overall structure and navigation are good.

4 / 5

Total

15

/

20

Passed

Description

70%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 solid description with a clear capability statement, third-person voice, and an explicit 'use when' clause covering three use scenarios. It would benefit from broader action coverage and more concrete, user-voiced trigger phrases.

Suggestions

Enumerate the key actions the skill performs (e.g., triage major vs. minor issues, deliver accept/revise/reject recommendations, build revision roadmaps) to raise specificity beyond two generic actions.

Rewrite the trigger clause around concrete user utterances, e.g., "Use when the user asks to review a paper, manuscript, or thesis, requests a pre-submission check, or wants feedback on a draft" to add natural synonyms like manuscript and draft.

DimensionReasoningScore

Specificity

"Conduct professional peer reviews for papers or theses, providing structured evaluations and improvement suggestions" names the domain and two concrete actions, but coverage is not comprehensive — major/minor issue triage, recommendation with rationale, and revision planning are absent. Not 4: anchor 4 expects several specific concrete actions with only minor gaps.

3 / 5

Completeness

The 'what' is clear (conduct peer reviews, structured evaluations, improvement suggestions) and the explicit clause "use when you need a pre-submission assessment, an internal review, or academic quality control" provides the 'when'. Not 5: the 'when' is phrased around user needs rather than concrete trigger phrases (e.g., "when the user asks to review a paper or manuscript").

4 / 5

Trigger Term Quality

Natural terms like "peer reviews", "papers", "theses", "pre-submission assessment", and "internal review" are phrases users would actually say. Not 5: common variations such as "manuscript", "draft", or "review my paper" are missing.

4 / 5

Distinctiveness Conflict Risk

Peer review of papers and theses is a clear niche with distinct triggers. Not 5: "internal review" and "academic quality control" are broad enough to invite minor overlap with generic review or QA skills.

4 / 5

Total

15

/

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

aipoch/medical-research-skills

Path

scientific-skills/Academic Writing/peer-review/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.