CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

response-letter

Helps organize reviewer comments and generate a standardized Word (.docx) response letter that maps each change to its exact location (page/paragraph/line). Use when revising a manuscript, replying to peer-review feedback, or preparing internal review responses.

Quality

76%

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

Quality

Content

58%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 excellent workflow sequencing with explicit user checkpoints and edge-case handling, and its bundle references are real and well-signaled. But it is noticeably redundant — the same response-layout rules are repeated three times in-body and again in guide.md — padded with generic template boilerplate, and it never explains how the .docx deliverable is actually produced from the bundled template.

Suggestions

Consolidate the response-layout rules (three-block structure, location marking, blockquote excerpting) into a single section — or delegate them to references/guide.md — instead of repeating them across Key Features, Example Usage, and Implementation Details, and drop the generic Output Contract / Required Inputs / Input Validation boilerplate.

Add concrete guidance for the docx generation step: how to use assets/review_response_template.docx (e.g., fill the template via python-docx, unpack/edit the OOXML, or another specified mechanism) so the core deliverable is reproducible.

Trim references/guide.md overlap by keeping SKILL.md as a lean overview and moving detailed output-format and quality-check rules wholly into the reference file with a single clear pointer.

DimensionReasoningScore

Conciseness

The core layout rules (Reviewer's Comment/Response/Changes in Text, page/paragraph/line marking, blockquote excerpting, added/deleted/rewritten labeling) are stated three times across Key Features, Example Usage, and Implementation Details, and again in references/guide.md. On top of that, roughly 50 lines of generic template boilerplate (Output Contract, Required Inputs table, Input Validation, Quick Validation) add no skill-specific value — several padded/redundant sections, fitting anchor 2 rather than 3.

2 / 5

Actionability

Concrete specifics exist (numbering scheme 'R{reviewer}-{index}', fixed three-block layout, location fallback rules, exact checkpoint phrasings), but the core deliverable step — how to actually produce the .docx from assets/review_response_template.docx — is entirely unspecified, with no script, library guidance, or template-usage instructions anywhere in the bundle. Missing key detail fits anchor 3 rather than 4.

3 / 5

Workflow Clarity

Steps 1–5 are clearly sequenced with explicit validation checkpoints (Checkpoint 1 before the Overview, Checkpoint 2 before DOCX generation with user confirmation, Checkpoint 3's three-part protocol for misread comments, Checkpoint 4 for multi-round disambiguation), plus an execution checklist in the output and a Failure Handling section with recovery guidance — matching the top anchor.

5 / 5

Progressive Disclosure

Both bundle references (references/guide.md and assets/review_response_template.docx) are real files, referenced one level deep and clearly signaled from Dependencies and Implementation Details, with well-organized sections. Minor gap: guide.md's content is largely duplicated inline in SKILL.md rather than cleanly split, fitting anchor 4 rather than 5.

4 / 5

Total

14

/

20

Passed

Description

83%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 strong description in third-person voice that clearly states what the skill does and when to use it, with concrete trigger phrases and specific output format detail. Its only weaknesses are minor: a few missing natural synonyms (rebuttal, resubmission, reviewer comments) and slight overlap risk with adjacent manuscript-revision skills.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'organize reviewer comments', 'generate a standardized Word (.docx) response letter', 'maps each change to its exact location (page/paragraph/line)' — with format detail. Minor gaps in coverage (no mention of the modification checklist, major/minor classification, or editor overview), so it fits anchor 4 rather than the comprehensive anchor 5.

4 / 5

Completeness

Explicitly answers both what ('organize reviewer comments and generate a standardized Word (.docx) response letter that maps each change to its exact location') and when ('Use when revising a manuscript, replying to peer-review feedback, or preparing internal review responses') with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Includes natural phrases users would say — 'revising a manuscript', 'replying to peer-review feedback', 'response letter', 'Word (.docx)' — but misses common synonyms like 'reviewer comments', 'rebuttal letter', or 'resubmission', fitting the 'good coverage, a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

Clear niche (peer-review response letters) with mostly distinct triggers, but 'revising a manuscript' and 'preparing internal review responses' create minor overlap risk with sibling manuscript-editing or review-coordination skills, fitting anchor 4 rather than 5.

4 / 5

Total

17

/

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/response-letter/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.