CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

medical-english-precision-editor

Improves medical English precision without changing the underlying facts, evidence boundaries, or intended scientific meaning.

Quality

61%

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/medical-english-precision-editor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%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 genuinely clear process architecture — sequenced steps, input validation, and a mandatory structured output — and a healthy reference bundle that is real and well-signaled. Its weaknesses are heavy redundancy (the same rules restated in six-plus sections and duplicated with references/hard-rules.md) and the absence of any worked before/after editing examples that would make the guidance concrete for an editing task.

Suggestions

Consolidate the overlapping constraint sections (Task, Important Distinctions, Core Function, What This Skill Should Not Do, Quality Standard) into one Hard Rules section and defer rule detail to references/hard-rules.md instead of duplicating it inline.

Add a short worked example — an original sentence, its precision-edited version, and the boundary check showing the claim strength was unchanged — since concrete before/after pairs are the core executable artifact for an editing skill.

Trim the prose around the reference list (each file needs only a one-line purpose) and around the Execution steps, which currently re-explain constraints already stated elsewhere.

DimensionReasoningScore

Conciseness

The same constraints (preserve meaning, do not overstate claims, ask for context when unclear) are restated across at least six sections — Task, Scope Boundary, Important Distinctions, Core Function, Hard Rules, What This Skill Should Not Do, and Quality Standard — and the body's Hard Rules duplicate references/hard-rules.md. This is noticeably verbose with several padded sections rather than only minor tightening, matching anchor 2 rather than anchor 3.

2 / 5

Actionability

The 8-step execution sequence and the mandatory A–G output structure with exact headers are concrete and executable, but the skill provides no worked examples — no before/after sentence pairs demonstrating a precision edit or an overstrengthening correction — leaving key details missing for an editing skill, which matches anchor 3. It is above anchor 2 because the process and output format are fully specified, not merely hinted.

3 / 5

Workflow Clarity

Steps 1–8 are clearly sequenced with explicit checkpoints: Step 1 validates input sufficiency before editing, Step 6 checks for unintended overstrengthening, and output sections A and F force an input-match and boundary check. It falls short of anchor 5 only because there is no feedback loop describing what to do when a checkpoint fails mid-edit (e.g., revise and re-verify the boundary check).

4 / 5

Progressive Disclosure

Seven one-level-deep references exist as real files, each introduced with its purpose and when to use it, and the body works as an overview pointing to them. Scored against the actual bundle structure, the main gap is that the body inlines a Hard Rules section that substantially duplicates references/hard-rules.md, matching anchor 4's 'minor organization gaps' rather than anchor 5's clean split.

4 / 5

Total

13

/

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 is accurate and appropriately narrow, clearly communicating a preserve-the-science editing role, but it is a single-clause statement of what rather than a full discovery description. It lacks any 'Use when...' trigger guidance and the natural vocabulary (edit, polish, manuscript, journal) users would actually type.

Suggestions

Append an explicit trigger clause, e.g., 'Use when the user asks to polish, edit, or proofread biomedical manuscript text, reviewer responses, figure legends, or slide prose without changing the science.'

Name the concrete edit types performed (terminology, grammar and tense, tone, flow/cohesion) so users and the router can match on them.

Include user-facing synonyms such as 'medical English', 'academic writing', and 'journal-style' to broaden natural trigger coverage without losing the niche.

DimensionReasoningScore

Specificity

"Improves medical English precision" names the domain and one core action, but the description never lists the concrete edit types it performs (grammar, tense, terminology, tone, flow), matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It falls short of anchor 4, which requires several specific actions listed.

3 / 5

Completeness

The 'what' is clear (improve medical English precision while preserving facts, evidence boundaries, and meaning), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It cannot score 4, which requires both what and an explicit (even if imperfect) when.

3 / 5

Trigger Term Quality

"medical English" is a phrase users would naturally say, but common natural terms such as edit, polish, proofread, manuscript, or journal are missing, matching 'Some relevant keywords but missing common variations or synonyms'. Not score 4 because good keyword coverage would include several of those everyday phrasings.

3 / 5

Distinctiveness Conflict Risk

"medical English precision" combined with "evidence boundaries" carves out a distinct biomedical-editing niche with characteristic triggers, but it could still trigger for general academic-writing or grammar-polishing requests, matching 'Mostly distinct; minor overlap risk with closely related skills'. Not 5 because a broader writing-assistant family would still compete for the same phrasings.

4 / 5

Total

13

/

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/medical-english-precision-editor/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.