CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

author-response-builder

Turns reviewer comments into structured, professional point-by-point responses linked to manuscript revisions, clarifications, rebuttals, and additional analyses.

Quality

71%

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 ./awesome-med-research-skills/Academic Writing/author-response-builder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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-structured, genuinely actionable instruction skill with a clear validated workflow and a properly organized one-level-deep reference bundle. Its main defect is verbosity through self-duplication: roughly a third of the body restates other sections or the hard-rules reference file, inflating token cost without adding guidance.

Suggestions

Delete 'Core Function' (duplicates 'Task') and the inline 'Hard Rules' section (verbatim copy of references/hard-rules.md, already loaded via the Reference Module Integration list).

Merge 'Scope Boundary', 'What This Skill Should Not Do', and 'Quality Standard' into one compact section; they restate the same accept/rebut/clarify boundaries three times.

Replace one of the repeated response-mode enumerations with a short worked example of a completed point-by-point response (one acceptance, one bounded rebuttal) to raise actionability.

DimensionReasoningScore

Conciseness

The body is noticeably padded through outright duplication: 'Core Function' restates 'Task' almost verbatim, the inline 'Hard Rules' section copies references/hard-rules.md word-for-word, 'Scope Boundary' / 'What This Skill Should Not Do' / 'Quality Standard' overlap heavily, and the response-mode list (acceptance/explanation/rebuttal/additional analysis) appears at least four times. This matches the several-padded-sections anchor rather than the mostly-efficient anchor 3, though it avoids explaining background concepts Claude already knows, so it is not a 1.

2 / 5

Actionability

For an instruction-only writing skill the guidance is concrete and executable: an 8-step workflow, a mandatory A–H output structure with exact section headers, quantified tiering rules ('2 or fewer comments... Combine Sections F, G, and H'; '5 or more comments... mode-distribution count'), and a quoted constructive-pivot phrasing to reuse. It falls short of anchor 5 only because there is no worked example of a completed point-by-point response covering the common cases.

4 / 5

Workflow Clarity

The multi-step process is clearly sequenced (Steps 1–8) with an explicit input-validation checkpoint up front (Step 1 'Clarify before drafting' plus output Section A 'Input Match Check') and a recovery path that asks for missing material instead of drafting blindly. It is not a 5 because later steps lack explicit checkpoints — e.g. Step 4's revision linkage is a list of things to check rather than a verify-and-fix loop confirming each reply maps to a real change.

4 / 5

Progressive Disclosure

All seven reference files referenced in the body exist in references/, are one level deep with no nested pointers, and each is signaled with a clear statement of when to use it. The gap keeping it at 4 rather than 5 is that content belonging in the reference files is duplicated inline — the full 'Hard Rules' list restates references/hard-rules.md — rather than the body being a lean overview pointing to the bundle.

4 / 5

Total

14

/

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 specific, third-person, well-niched description that clearly conveys what the skill does, but it lacks any explicit 'when to use' trigger clause, which both caps completeness and slightly weakens trigger-term coverage. Adding a 'Use when drafting responses to peer reviewer or editor comments...' sentence would resolve both weaknesses at once.

Suggestions

Append an explicit trigger clause, e.g. 'Use when drafting responses to peer reviewer or editor comments, rebuttal letters, or point-by-point revision responses.'

Add natural user phrasings such as 'response letter', 'peer review comments', and 'revision letter' to the trigger vocabulary.

Optionally mention editor response letters in the capability list to round out coverage.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'Turns reviewer comments into structured, professional point-by-point responses' plus the linked modes 'manuscript revisions, clarifications, rebuttals, and additional analyses' — but omits adjacent capabilities like editor response letters and response-mode selection, leaving minor coverage gaps that keep it below the comprehensive anchor 5.

4 / 5

Completeness

The 'what' is clearly stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance; per the judging guidelines a missing explicit 'when' caps completeness at 3. It is not a 4 because the when-condition is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Natural phrases users would say are present ('reviewer comments', 'point-by-point responses', 'manuscript revisions', 'rebuttals'), but common variations such as 'response letter', 'peer review', or 'revision letter' are missing, matching the good-coverage-with-a-few-gaps anchor rather than the comprehensive one.

4 / 5

Distinctiveness Conflict Risk

The peer-review response domain is a clear niche with distinct triggers ('reviewer comments', 'manuscript revisions', 'rebuttals') and minimal realistic overlap with other skills, matching the clear-niche anchor; it is not a 4 because no closely related competing skill surface is suggested by this wording.

5 / 5

Total

16

/

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

awesome-med-research-skills/Academic Writing/author-response-builder/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.