CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

referral-letter-generator

Generate medical referral letters with patient summary, reason for referral, key findings, and requested next steps; use when transferring care or communicating with another clinician or department.

Quality

74%

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/referral-letter-generator/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 delivers genuinely actionable core documentation (usage, parameters, example) but is buried under generic template boilerplate that roughly doubles its length. The references section is both vague and partially inaccurate, and the abstract workflow is disconnected from the concrete validation commands.

Suggestions

Remove or externalize the generic boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Output Contract, User Checkpoints, Response Template) that are not specific to referral letter generation, and delete the 'Quick Check' section that duplicates the Audit-Ready Commands.

Rewrite the References section to link the actual bundled files by name (e.g., 'See [templates.md](references/templates.md) and [referral_standards.md](references/referral_standards.md)') and remove the nonexistent 'Medical terminology guidelines' and 'Privacy compliance checklist' entries or add those files.

Integrate the concrete validation commands (py_compile, --help) into the Workflow steps with an explicit validate-then-fix-then-retry loop, and fix the copy-pasted 'When to Use' bullet about 'academic writing tasks' that does not match this skill's purpose.

DimensionReasoningScore

Conciseness

The ~260-line body is padded with generic boilerplate sections (Risk Assessment, Security Checklist, Lifecycle Status, Evaluation Criteria, Output Contract, User Checkpoints, Response Template) that add nothing referral-specific, and 'Quick Check' duplicates the same 'python -m py_compile scripts/main.py' command already in 'Audit-Ready Commands'. Not 1 because the Usage, Input Parameters, and Example sections do carry real content.

2 / 5

Actionability

Provides concrete executable guidance: 'python scripts/main.py --input patient_data.json --output referral_letter.pdf', a full parameter table, and a worked example JSON; scripts/main.py exists in the bundle. Not 5 because the Python API example uses '{...}' placeholders and the References section names files ('Medical terminology guidelines', 'Privacy compliance checklist') that do not exist in references/.

4 / 5

Workflow Clarity

The 5-step Workflow is present but abstract ('Use the packaged script path or the documented reasoning path with only the inputs that are actually available') with no commands embedded or validate-fix-retry loop; validation exists only as a separate unconnected command block. Not 4 because the sequence lacks concrete checkpoints tied to the actual commands.

3 / 5

Progressive Disclosure

Substantial content that belongs in separate files (security checklist, risk assessment, evaluation criteria, lifecycle) is inlined in SKILL.md, and the References section is vague ('See references/ folder for:...') without naming the actual bundled files, two of which it misdescribes. Not 2 because real one-level-deep bundle files (templates.md, referral_standards.md, referral_template.md) do exist.

3 / 5

Total

12

/

20

Passed

Description

87%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 strong description that clearly and explicitly states both the capability and its use conditions with concrete trigger phrases. Minor improvements possible by broadening synonyms (e.g., 'refer a patient to a specialist') and hinting at output formats.

DimensionReasoningScore

Specificity

The description names the domain ('medical referral letters') and enumerates concrete output components ('patient summary, reason for referral, key findings, and requested next steps'). Not 5 because it uses a single action verb ('Generate') and omits capabilities like output formats or the bundled script; not 3 because it lists several specific deliverable elements rather than just 1-2.

4 / 5

Completeness

Explicitly answers both what ('Generate medical referral letters with patient summary, reason for referral, key findings, and requested next steps') and when ('use when transferring care or communicating with another clinician or department') with concrete trigger phrases, matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

Includes natural phrases users would say: 'referral letters', 'transferring care', 'communicating with another clinician or department'. Not 5 because common variations like 'refer a patient to a specialist', 'handoff', or 'consult' are missing; not 3 because coverage goes beyond a single generic keyword.

4 / 5

Distinctiveness Conflict Risk

The medical referral letter niche is clear and distinct; triggers ('transferring care', 'communicating with another clinician') are unlikely to fire for unrelated skills, so conflict risk is minimal.

5 / 5

Total

18

/

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/referral-letter-generator/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.