CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

medical-email-polisher

Transforms rough email drafts into polished, professional medical correspondence.

Quality

56%

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

Quality

Content

42%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 contains genuinely useful concrete material (parameter table, output schema, runnable commands) buried in heavy generic boilerplate: circular self-references, a grammatically broken When-to-Use line, four overlapping policy sections, and a wrong example path. Trimming the template filler, fixing the example, adding one worked polish example, and linking references/guidelines.md by name would move most dimensions up a full point.

Suggestions

Delete or merge the boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Output Requirements, Response Template, Input Validation) into a short Workflow plus Error Handling section — they are the main source of padding.

Fix the example usage path ('20260318/scientific-skills/...' does not exist) and add one complete worked example: a rough draft input, the command, and the polished JSON output.

Replace 'Reference material available in `references/`' with a named link to `references/guidelines.md` and briefly describe what it contains (communication standards and correspondence templates).

DimensionReasoningScore

Conciseness

The body has several padded or circular sections — 'See `## Features` above for related details', 'See `## Prerequisites` above for related details', the broken 'Use this skill when the task needs Transforms rough email drafts...' line, plus redundant boilerplate (Risk Assessment table, Security Checklist, Evaluation Criteria, Lifecycle Status with a review date, and four overlapping output/error/validation sections). This is noticeably verbose with several padded sections rather than only occasional tightening opportunities, but it never explains basic concepts Claude already knows, so it does not fall to 1.

2 / 5

Actionability

Concrete commands exist (`python -m py_compile scripts/main.py`, `python scripts/main.py --help`, `python scripts/main.py demo`) along with a specific parameter table and output JSON schema, but the usage example cds into a nonexistent hardcoded path ('20260318/scientific-skills/...') and no worked example with a real input draft and its polished output is provided. These are missing key details, not the minor gaps of a 4.

3 / 5

Workflow Clarity

The 5-step Workflow lists a sequence with a py_compile pre-check and an error-handling fallback, but the steps are abstract ('Use the packaged script path or the documented reasoning path'), output-quality validation is absent, and the sequence is duplicated across three overlapping sections (Workflow, Implementation Details, Example run plan). This fits 'steps listed but validation gaps' rather than the mostly-checkpointed 4; no destructive/batch cap applies since this is a low-risk text task.

3 / 5

Progressive Disclosure

Referenced bundle files are real and one level deep (`scripts/main.py` verified, `references/guidelines.md` verified), but the body never names or links guidelines.md — only the vague 'Reference material available in `references/`' — and substantial boilerplate (risk tables, checklists, lifecycle metadata) that should be trimmed or split is inlined in SKILL.md. This matches 'references present but not clearly signaled; content that should be separate is inline' rather than the well-signaled 4.

3 / 5

Total

11

/

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 grammatical, correctly third-person, and names a concrete domain, but it is a single terse sentence: one broad action, no trigger guidance, and no synonyms. Adding an explicit 'Use when...' clause covering the recipient types and polish/edit/proofread phrasing would lift it from the 3s into 4-5 territory.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to polish, edit, or proofread an email to a mentor, journal editor, colleague, or patient.'

Enumerate the concrete capabilities already documented in the body (tone adjustment, recipient-specific templates, HIPAA-aware patient communication) instead of the single 'transforms' action.

Include natural user phrasings and synonyms such as 'polish', 'proofread', 'rewrite', and 'patient/colleague email' so the skill triggers on how users actually ask.

DimensionReasoningScore

Specificity

The description names the domain ('medical correspondence') and one concrete action ('Transforms rough email drafts into polished, professional medical correspondence'), matching the anchor for 1-2 concrete actions. It is not a 4 because it lists only a single generic action, omitting capabilities documented in the body such as tone adjustment, recipient templates, and HIPAA-aware communication.

3 / 5

Completeness

It has a clear 'what' (transforms rough drafts into polished medical correspondence) but no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3. A score of 4 would require an explicit, if imperfect, 'when' statement, which is absent.

3 / 5

Trigger Term Quality

Relevant keywords are present ('email drafts', 'medical correspondence', 'professional') but common natural phrases users would say — 'polish', 'proofread', 'edit', 'rewrite', 'colleague email', 'patient email' — are missing. This matches 'some relevant keywords but missing common variations or synonyms' rather than the good coverage of a 4.

3 / 5

Distinctiveness Conflict Risk

'Medical correspondence' carves a mostly distinct niche with only minor overlap risk against general email-polishing or academic-writing skills, fitting 'mostly distinct; minor overlap risk'. It is not a 5 because without explicit trigger phrases it could still fire for generic 'polish my email' requests.

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

scientific-skills/Academic Writing/medical-email-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.