CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

response-tone-polisher

Polish reviewer-response letters by softening defensive language, preserving factual meaning, and keeping responses professional, concise, and publication-appropriate.

Quality

62%

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-tone-polisher/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 strong actionable core content — usage examples, a transformation table, CLI and Python API usage — but it is buried under ~150 lines of generic safety/lifecycle boilerplate and content duplicated from its own reference files. Two referenced paths ('references/examples/', 'requirements.txt') are missing from the bundle, and the documented workflow is boilerplate rather than a task-specific sequence.

Suggestions

Cut the generic boilerplate sections (Risk Assessment, Security Checklist, Lifecycle Status, Output Requirements, Response Template, Required Inputs, Output Contract, Failure Handling, User Checkpoints, Quick Validation) or compress them into a few lines.

Remove the inlined 'Tone Patterns Detected' and 'Polite Academic Expressions' sections and point to references/tone_patterns.md and references/polite_expressions.json instead, eliminating duplication.

Fix broken references: either create references/examples/ and requirements.txt or remove them from the References and Prerequisites sections; replace the generic Workflow with a task-specific sequence (classify tone → apply transformation → verify position preserved).

DimensionReasoningScore

Conciseness

Roughly half the body is generic process boilerplate ('Risk Assessment', 'Security Checklist', 'Lifecycle Status', 'Output Requirements', 'Response Template', 'Required Inputs', 'Output Contract', 'Failure Handling', 'User Checkpoints', 'Quick Validation') that adds nothing specific to tone polishing, and the 'Tone Patterns Detected' / 'Polite Academic Expressions' sections (~70 lines) inline content already shipped in references/tone_patterns.md and references/polite_expressions.json. This matches 'several unnecessary explanations or padded sections' — not 1 because the core instructional sections (examples, CLI, API, output format) are genuinely substantive.

2 / 5

Actionability

Concrete, executable guidance throughout: runnable CLI commands ('python scripts/main.py --interactive', py_compile checks), a Python API example ('from scripts.main import TonePolisher'), an input-parameter table, a JSON output schema, and before/after transformation examples. Not 5 because referenced prerequisites are broken — 'references/examples/' and 'requirements.txt' do not exist in the bundle, so some commands cannot be verified as-is.

4 / 5

Workflow Clarity

A workflow is listed ('Confirm the user objective... Validate that the request matches the documented scope...') but the steps are generic process text not tied to the actual polishing task (no sequence like classify tone → apply transformation → verify preservation), and checkpoints are implicit in separate checklist sections. This matches 'Steps listed but validation gaps; sequence present but checkpoints missing or implicit'; not 4 because the sequence is not concretely mapped to the skill's own operations.

3 / 5

Progressive Disclosure

Sections are well-organized and references are clearly signaled ('references/polite_expressions.json - Curated library of academic polite expressions'), but content that clearly belongs in the reference files (tone patterns, the expression library) is duplicated inline in the body, and one referenced path ('references/examples/') does not exist in the bundle. This matches 'content that should be separate is inline'; not 4 because of the duplication and the broken reference.

3 / 5

Total

12

/

20

Passed

Description

58%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 is well-crafted: third person, concrete about what the skill does, and tightly scoped to reviewer-response letters. Its main gaps are the absence of any explicit 'when to use' trigger clause and missing natural synonyms such as 'rebuttal' or 'peer review' that users would likely say.

Suggestions

Add an explicit trigger clause, e.g. 'Use when drafting rebuttal letters or responses to peer reviewer comments.'

Include natural synonyms users would say — 'rebuttal letter', 'peer review response', 'response to reviewers' — to improve trigger term coverage.

Optionally mention tone analysis or response-type adaptation (accept/partial/decline) to round out capability coverage.

DimensionReasoningScore

Specificity

The description names the domain ('reviewer-response letters') and several concrete actions ('softening defensive language', 'preserving factual meaning', 'keeping responses professional, concise, and publication-appropriate'), comparable to the anchor 'Extracts text from PDF files, fills forms, converts pages to images'. It is not a 5 because coverage is incomplete — no mention of tone analysis, response-type adaptation, or the expression library — and not a 3 because more than 1-2 specific actions are listed with clear outcomes.

4 / 5

Completeness

The 'what' is clear and concrete (polishing reviewer-response letters by softening defensive language while preserving meaning), but there is no 'Use when...' clause or equivalent explicit trigger guidance; timing is only weakly implied through the domain noun. Per the judging guidelines, a missing 'Use when' clause caps completeness at 3, and 4 would require at least a weakly explicit 'when'.

3 / 5

Trigger Term Quality

'reviewer-response letters', 'defensive language', and 'publication-appropriate' are relevant keywords, but common natural variations users would say — 'rebuttal letter', 'peer review', 'response to reviewers', 'tone' — are absent. This matches 'Some relevant keywords but missing common variations or synonyms' rather than 4, which requires only a few missing natural terms.

3 / 5

Distinctiveness Conflict Risk

'reviewer-response letters' plus 'defensive language' establishes a clear niche with minor overlap risk against generic academic-writing or editing skills. It is not 5 because 'professional, concise' output language could co-trigger with general editing/polishing skills; it is not 3 because the reviewer-response framing is far more specific than 'Works with document files'.

4 / 5

Total

14

/

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/response-tone-polisher/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.