CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

peer-review-response-drafter

Assist in drafting professional peer review response letters. Trigger.

Quality

56%

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-response-drafter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%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 body has a solid core — a realistic usage example, a useful quality checklist, explicit error handling and fallback paths — but it is buried in generic template boilerplate and, critically, its documentation of the packaged script is wrong: the parameter table lists flags the script does not accept and omits the two required ones, and the 'Audit-Ready' command would fail as written. The dangling references/examples/ path further undermines reliability. It needs a pruning pass and a doc-accuracy pass against main.py.

Suggestions

Correct the Parameters table to match scripts/main.py: document '--input/-i' (not '--input-file'), add the required '--title' and '--journal' arguments, and remove the nonexistent '--format' and '--include-diff' flags (or implement them); fix the Audit-Ready commands so they include the required arguments and use a peer-review sample input instead of the medical-sounding 'symptoms, history, assessment' string.

Delete the template filler that adds no skill-specific value: 'Key Features', the stdlib 'Dependencies' list, 'Evaluation Criteria', 'Lifecycle Status', 'Risk Assessment', and the generic 'Security Checklist' — or compress them to the few lines that carry real information.

Resolve the dangling reference: create references/examples/ with sample response letters or remove the 'references/examples/' line from the References section.

DimensionReasoningScore

Conciseness

The ~250-line body carries many padded template sections that add nothing Claude doesn't know: 'Dependencies' lists stdlib modules ('dataclasses', 'enum'), plus generic filler like 'Key Features', 'Evaluation Criteria' ('Performance is acceptable'), 'Lifecycle Status', 'Risk Assessment', and a boilerplate 'Security Checklist'. This matches 'noticeably verbose; several unnecessary explanations or padded sections'. Not a 1 because the core sections (Parameters, Usage Example, Quality Checklist, Error Handling) contain genuine non-obvious content; not a 3 because at least half the body is dispensable boilerplate, including broken self-references ('See `## Prerequisites` above' pointing to a later section).

2 / 5

Actionability

Concrete material exists (py_compile quick check, a parameters table, a realistic usage example, a quality checklist), but the core executable guidance does not match the packaged script: the table documents '--input-file', '--format', and '--include-diff' which main.py does not define, while the script's required '--title' and '--journal' arguments are undocumented — so both the table and the 'Audit-Ready' command ('python scripts/main.py --input "..."') would fail as written. This fits 'some concrete guidance but incomplete; missing key details'. Not a 4 because the guidance is not mostly-executable against the actual implementation; not a 2 because there is substantial specific, structured guidance beyond high-level hints.

3 / 5

Workflow Clarity

A 5-step Workflow with an explicit fallback path ('If execution fails or inputs are incomplete, switch to the fallback path and state exactly what blocked full completion') and a parse-level Quick Check exist, but checkpoints are generic process directives ('Confirm the user objective', 'Validate that the request matches the documented scope') rather than domain-validated steps, and the audit command meant to verify execution cannot run (missing required --title/--journal). This matches 'steps listed but validation gaps; sequence present but checkpoints missing or implicit'. Not a 4 because the documented verification commands fail against the real CLI; not a 2 because a coherent sequence with error handling and input-validation rules is present.

3 / 5

Progressive Disclosure

References are one level deep and clearly signaled with one-line descriptions ('references/response_templates.md - Common response patterns', 'references/tone_guide.md - Academic tone guidelines'), and scripts/main.py is real — but 'references/examples/' is cited in the References section and does not exist in the bundle, and large amounts of template boilerplate are inlined in SKILL.md that belong in references or nowhere. This fits 'some structure but could be better organized'. Not a 4 because of the dangling reference path and the inlined generic checklist/lifecycle content; not a 2 because the structure is sectioned and the two existing reference files are well-signaled and genuinely offloaded.

3 / 5

Total

11

/

20

Passed

Description

53%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 communicates a clear, specific purpose but is crippled by the literal 'Trigger.' placeholder where a 'Use when...' clause should be — it reads as an unfinished template. It names the domain well yet provides no trigger guidance and no synonym coverage. The fix is small: append a real trigger clause such as 'Use when responding to peer reviewer comments, rebuttal letters, or revision requests.'

Suggestions

Replace the dangling 'Trigger.' fragment with an explicit trigger clause, e.g. 'Use when the user needs to respond to peer reviewer comments, write a rebuttal letter, or address revision requests for a journal submission.'

Add natural trigger synonyms and related phrasings ('reviewer comments', 'rebuttal letter', 'respond to reviewers', 'revision response') so users' natural language matches the description.

Broaden the 'what' slightly to cover the skill's documented capabilities (parse reviewer comments, draft point-by-point responses, adjust tone), which currently only says 'drafting'.

DimensionReasoningScore

Specificity

The description names its domain ('peer review response letters') and one concrete action ('drafting professional... letters'), matching the anchor for naming a domain with 1-2 concrete actions but not comprehensive coverage. It is not a 4 because it omits other capabilities the body documents (parsing reviewer comments, tone adjustment, output formats); not a 2 because the domain and action are specific rather than generic.

3 / 5

Completeness

The 'what' is clearly stated ('drafting professional peer review response letters'), but the 'when' is effectively absent: 'Trigger.' is a corrupted placeholder, not an explicit 'Use when...' clause or equivalent trigger guidance, so completeness is capped at 3 per the judging guidelines. It is not a 2 because the 'what' is concrete rather than vague; it cannot be a 4 without any usable trigger guidance.

3 / 5

Trigger Term Quality

'peer review' and 'response letters' are relevant, fairly natural keywords, but common variations users would say are missing ('reviewer comments', 'rebuttal', 'respond to reviewers'). The trailing 'Trigger.' is a broken placeholder adding no keyword value; it falls between anchor 3 (some relevant keywords, missing synonyms) and anchor 2, but the domain-specific terms keep it at 3 rather than dropping to the generic-keyword level of 2.

3 / 5

Distinctiveness Conflict Risk

'Peer review response letters' carves out a specific academic niche with minimal overlap risk against unrelated skills, fitting 'mostly distinct; minor overlap risk with closely related skills' — the body shows this skill sits in a family of packaged academic-writing skills where partial overlap is plausible. Not a 5 because distinct trigger phrases are absent (the 'Trigger.' fragment), leaving it reliant on domain phrasing alone.

4 / 5

Total

13

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

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