CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

revision-strategy-planner

Builds prioritized manuscript revision plans for major or minor revisions by separating comments that require experiments, analyses, clarification, restructuring, or wording changes.

Quality

69%

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/revision-strategy-planner/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.

The skill has a genuinely strong skeleton: a clear 9-step workflow, an upfront validation checkpoint, a mandatory output structure, and a well-designed one-level-deep reference bundle. Its main liability is heavy internal redundancy — the same taxonomies and rules are repeated three to four times across sections and duplicated from reference files — which inflates token cost without adding guidance value.

Suggestions

Deduplicate the body: keep each taxonomy (comment types, routing categories, feasibility tiers) in exactly one place and reference the corresponding references/*.md file instead of restating it — e.g., cut the 'Task'/'Core Function' repetition and the verbatim copy of references/hard-rules.md.

Add one compact worked example (a sample reviewer comment with its triage verdict, routing decision, and priority tier) to make the abstract judgment criteria concrete.

Add a final verification step to the Execution workflow that checks the produced output against the Quality Standard and Hard Rules before finishing.

DimensionReasoningScore

Conciseness

The 315-line body is noticeably padded through repetition: the comment-routing categories (new experiment / analysis / clarification / wording / restructuring / bounded rebuttal) are restated at least four times ('Important Distinctions', 'Reference Module Integration', 'Step 4', 'Mandatory Output Structure E'); 'Hard Rules' duplicates references/hard-rules.md nearly verbatim; and 'Task', 'Core Function', and 'Execution' restate the same list three times. It avoids explaining concepts Claude already knows, so it stays above a 1.

2 / 5

Actionability

For an instruction-only skill the guidance is concrete and executable: a 9-step execution sequence, a mandatory A-J output structure with exact section headers, and explicit decision categories and hard rules. It falls short of a 5 because there is no worked example — e.g., a sample reviewer comment triaged and routed — so the judgment calls the skill hinges on are illustrated only abstractly.

4 / 5

Workflow Clarity

Steps 1-9 are clearly sequenced with an explicit input-validation checkpoint up front (Step 1, 'Input Validation', and section A) and a strong/weak output quality standard functioning as a checklist. Not a 5 because there is no post-output verification loop tying the Quality Standard back into the Execution steps.

4 / 5

Progressive Disclosure

All seven referenced files exist, are one level deep (none reference each other), and each is signaled with its purpose and usage condition. Not a 5 because the body inlines substantial material (Hard Rules, full routing taxonomies) that already lives in the reference files, making the ~315-line 'overview' bulky and blurring the overview/detail split.

4 / 5

Total

14

/

20

Passed

Description

66%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, domain-anchored description with good natural trigger terms and a clearly stated capability. Its main weakness is the missing 'Use when...' trigger clause, which caps completeness and slightly weakens both trigger reliability and distinctiveness from adjacent rebuttal-drafting skills.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user mentions reviewer comments, an editor decision letter, major or minor revision, reject-and-resubmit, or planning a rebuttal.'

Include the natural synonyms users actually say — 'reviewer comments', 'rebuttal', 'response to reviewers' — to improve trigger-term coverage and distinctiveness from rebuttal-drafting skills.

DimensionReasoningScore

Specificity

The description names the domain ('manuscript revision plans for major or minor revisions') and several concrete action categories ('separating comments that require experiments, analyses, clarification, restructuring, or wording changes'). It falls short of a 5 because coverage has minor gaps — rebuttal alignment and feasibility triage, which the body treats as core, are absent — and above a 3 because it enumerates multiple specific actions rather than 1-2.

4 / 5

Completeness

The 'what' is clearly and concretely stated ('Builds prioritized manuscript revision plans... by separating comments...'), but there is no 'Use when...' clause or equivalent explicit trigger guidance; 'for major or minor revisions' only weakly implies when. Per the rubric guideline, a missing 'when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

'manuscript revision plans', 'major or minor revisions', 'experiments', 'analyses', and 'clarification' are phrases users would naturally say. A few natural terms are missing — 'reviewer comments' (only bare 'comments' appears), 'rebuttal', 'response to reviewers' — which matches the anchor for good but not comprehensive keyword coverage.

4 / 5

Distinctiveness Conflict Risk

The peer-review revision-triage niche is clearly distinct from generic writing-assistant skills and unlikely to trigger the wrong skill. Minor overlap risk remains with a rebuttal-drafting skill, since 'rebuttal' is absent from the description, slightly blurring that adjacent boundary.

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

awesome-med-research-skills/Academic Writing/revision-strategy-planner/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.