CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

discharge-summary-writer

Generate hospital discharge summaries from admission data, hospital course, diagnoses, procedures, and follow-up plans; use when a structured discharge document is required from clinical notes.

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/discharge-summary-writer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 functional core is solid: real commands, a complete input schema, matching script arguments, and clearly signaled bundle references. However, the body is bloated with template boilerplate (security/risk/lifecycle/output-contract sections) that is unrelated to discharge summaries, including drift into 'academic writing tasks', and the workflow steps are abstract rather than skill-specific.

Suggestions

Delete or collapse the generic boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Output Contract, User Checkpoints, Required Inputs, Quick Validation) and merge the four overlapping error/validation sections (Error Handling, Failure Handling, Input Validation, When Not to Use) into one — this would roughly halve the body and remove the 'academic writing tasks' drift.

Rewrite the Workflow as a skill-specific command sequence with checkpoints: validate input JSON against the documented schema → run `python scripts/main.py --input patient_data.json --output discharge_summary.md --format standard` → verify the output contains the seven standard sections → on failure, report the failing step and use the manual template in references/discharge_template.md as fallback.

Reference the bundled `references/example_patient.json` (e.g., in a Quick Start showing the example invocation against it) and include a short sample of the standard output structure so the expected deliverable is concrete.

DimensionReasoningScore

Conciseness

Roughly half the body is generic governance boilerplate that any skill could carry ("Risk Assessment", "Security Checklist", "Evaluation Criteria", "Lifecycle Status", "Output Contract", "User Checkpoints", "Quick Validation"), with heavy redundancy across "Error Handling", "Failure Handling", "Input Validation", and "When Not to Use". The "Audit-Ready Commands" section repeats `--help` three times, and "When to Use" even drifts into "academic writing tasks" — clearly template residue from another skill. This matches 'noticeably verbose; several unnecessary explanations or padded sections'.

2 / 5

Actionability

Concrete, executable guidance is present: `python -m py_compile scripts/main.py`, the full usage invocation (`python scripts/main.py --input patient_data.json --output discharge_summary.md --format standard`) whose flags match the actual script, a complete input JSON schema, and a parameters table. Minor gaps: the bundled `references/example_patient.json` is never referenced, no sample output is shown, and some Workflow steps are abstract rather than executable.

4 / 5

Workflow Clarity

A 5-step Workflow exists and validation is mentioned (Quick Check py_compile, "Quick Validation" checklist, fallback on failure), but the workflow steps are generic template language ("Use the packaged script path or the documented reasoning path") rather than a skill-specific sequence with commands, and checkpoints are implicit (e.g., validate input against the JSON schema before running, verify output sections after). This fits 'steps listed but validation gaps; checkpoints missing or implicit'.

3 / 5

Progressive Disclosure

The References section clearly signals three real one-level-deep bundle files with one-line descriptions, and scripts/main.py exists with matching CLI args — no nested references. Minor organization gaps: the bundled references/example_patient.json is not surfaced anywhere, and generic inline sections (Risk/Security/Lifecycle tables) dilute the overview, keeping it below the score-5 anchor.

4 / 5

Total

13

/

20

Passed

Description

83%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: it clearly states what the skill produces, enumerates the concrete data inputs, and includes an explicit use-when clause with concrete terms. The main weaknesses are a single action verb (limited to 'Generate') and slightly unusual trigger phrasing that leaves minor overlap risk with other clinical-documentation skills.

DimensionReasoningScore

Specificity

The description names one concrete action ("Generate hospital discharge summaries") and comprehensively enumerates the five input categories ("admission data, hospital course, diagnoses, procedures, and follow-up plans") with only minor gaps (e.g., medication reconciliation implied but not named). It exceeds the score-3 anchor ('1-2 concrete actions, but not comprehensive') but does not list several distinct actions as the score-5 anchor requires.

4 / 5

Completeness

Both what ("Generate hospital discharge summaries from admission data, hospital course, diagnoses, procedures, and follow-up plans") and when ("use when a structured discharge document is required from clinical notes") are explicitly answered with concrete trigger terms ("structured discharge document", "clinical notes"). The when-clause is more specific than the score-4 example ('Use when working with PDF files'), fitting the score-5 anchor.

5 / 5

Trigger Term Quality

Natural phrases users would say are present: "discharge summaries", "clinical notes", "hospital course". A few natural variants are missing (e.g., "discharge paperwork", "hospital summary", "follow-up instructions"), matching the score-4 anchor 'good keyword coverage; a few natural terms missing'.

4 / 5

Distinctiveness Conflict Risk

The hospital-discharge-summary niche is clear and triggers like "discharge summaries" are distinct, but the phrase "a structured discharge document is required" is slightly abstract and the description sits in a crowded clinical-documentation space with minor overlap risk against adjacent medical-writing skills. This fits 'mostly distinct; minor overlap risk' rather than the fully distinct score-5 anchor.

4 / 5

Total

17

/

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/discharge-summary-writer/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.