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

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

60%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 content is actionable and reasonably well-structured with real bundle files, but it carries substantial generic boilerplate and redundant commands that hurt token efficiency. Tightening the scaffolding and signaling references inline would materially improve it.

Suggestions

Remove duplicate commands (py_compile and --help are repeated) and consolidate the overlapping process sections (Output Requirements, Response Template, When Not to Use, Required Inputs, Output Contract, Failure Handling, User Checkpoints, Quick Validation) into a single concise section.

Delete generic non-skill-specific scaffolding (Risk Assessment table, Security Checklist, Lifecycle Status, Evaluation Criteria) unless it adds discharge-summary-specific value.

Signal references inline where relevant (e.g., 'See references/discharge_template.md for the template') and add the existing example_patient.json to the References list so all bundle files are discoverable.

Dimension	Reasoning	Score
Conciseness	The body is noticeably padded — duplicate validation commands, and large generic scaffolding sections (Risk Assessment, Security Checklist, Lifecycle Status, Output Requirements, Response Template, User Checkpoints, Quick Validation) that add little skill-specific value.	2 / 5
Actionability	Provides concrete executable commands, a full parameters table, and a complete JSON input schema, with only minor gaps (no inline sample of a generated summary).	4 / 5
Workflow Clarity	A sequenced 5-step Workflow with a fallback path and validation entry points (Quick Check, Error Handling); checkpoints are present but not tied into a tight validate-fix-retry loop.	4 / 5
Progressive Disclosure	Three reference files and the script are present and exist on disk, and the body stays an overview; but references are listed flatly rather than contextually signaled inline, and example_patient.json is unreferenced.	4 / 5
	Total	14 / 20 Passed

Description

92%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 strong: it concisely states concrete capabilities, an explicit use-when trigger, and occupies a clear clinical niche with low conflict risk. The only gap is trigger-term breadth — adding synonyms or file-type cues would make it fully comprehensive.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (generate discharge summaries) integrating comprehensive input types — admission data, hospital course, diagnoses, procedures, and follow-up plans — matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly answers both 'what' (generate discharge summaries from the listed inputs) and 'when' (use when a structured discharge document is required) with a concrete trigger clause.	5 / 5
Trigger Term Quality	Includes natural trigger phrasing ('use when a structured discharge document is required from clinical notes') and domain terms, but lacks common synonyms (e.g., 'discharge paperwork/letter') and file extensions that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	A narrow clinical-document niche with distinct triggers ('discharge summaries', 'structured discharge document') that is unlikely to fire for unrelated skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 63c61d3

Reviewed: 6 hours ago

Table of Contents

Discovery Implementation Validation

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.