clinical-reports

Write comprehensive clinical reports including case reports (CARE guidelines), diagnostic reports (radiology/pathology/lab), clinical trial reports (ICH-E3, SAE, CSR), and patient documentation (SOAP, H&P, discharge summaries). Full support with templates, regulatory compliance (HIPAA, FDA, ICH-GCP), and validation tools.

Quality

67%

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 ./bundled/skills/clinical-reports/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 skill is well-structured with real bundle files and clear workflows, but it is substantially verbose — inlining detailed report-specification content that belongs in the reference files it already provides. Trimming SKILL.md to an overview would improve token efficiency.

Suggestions

Move the field-by-field report specifications (CARE checklist, ICH-E3 section list, SOAP/H&P/discharge component breakdowns) into the corresponding references/ files, leaving SKILL.md as a concise overview with pointers.

Add explicit validate->fix->retry feedback loops for batch/destructive operations (e.g. 'run check_deidentification.py, fix flagged identifiers, re-run until clean') to strengthen workflow checkpoints.

Reduce restatement of well-known domain concepts (what HIPAA/SNOMED/ICD-10 are) to brief mentions with links to references, cutting token cost.

Dimension	Reasoning	Score
Conciseness	The 1131-line body is noticeably verbose, inlining extensive field-by-field report structures (full CARE checklist, ICH-E3 section enumeration, SOAP/H&P component breakdowns) and explaining domain concepts Claude already knows, which belongs in reference files.	2 / 5
Actionability	The skill provides concrete report structures, named templates, and references to executable validation scripts (e.g. scripts/validate_case_report.py, scripts/check_deidentification.py) with a runnable schematic command; minor gaps in inline executable code keep it just below fully copy-paste ready.	4 / 5
Workflow Clarity	Workflows are clearly sequenced (case report phases, SAE 24h-15d timeline, CSR 6-12 month path) with timing benchmarks and validation scripts referenced; validation checkpoints are implied via the final checklist and scripts rather than explicitly woven as validate->fix->retry loops, so just below a 5.	4 / 5
Progressive Disclosure	Good one-level-deep structure: the body points to real references/ and assets/ files (verified to exist) and lists them in a Resources section; however a large amount of reference-grade content is inlined in SKILL.md rather than split out, keeping it just below a 5.	4 / 5
	Total	14 / 20 Passed

Description

75%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 specific and distinct with strong natural trigger terms, but it omits an explicit 'Use when...' clause, which caps its completeness. Adding a concrete trigger clause would raise the completeness score.

Suggestions

Add an explicit 'Use when...' clause naming the triggering scenarios, e.g. 'Use when writing or reviewing clinical reports, case reports, SAE/CSR submissions, or patient documentation like SOAP notes and discharge summaries.'

Include a few synonyms and file extensions users might naturally say (e.g. 'radiology report', 'pathology report', '.md templates') to round out trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions across four report categories — "case reports (CARE guidelines), diagnostic reports (radiology/pathology/lab), clinical trial reports (ICH-E3, SAE, CSR), and patient documentation (SOAP, H&P, discharge summaries)" — with comprehensive coverage matching the 5-anchor.	5 / 5
Completeness	The "what" is clear and concrete, but there is no explicit "Use when..." trigger clause; per the rubric a missing explicit trigger guidance caps completeness at 3.	3 / 5
Trigger Term Quality	Strong natural terms users would say (case reports, SOAP, discharge summaries, HIPAA, SAE, clinical trial) are present, but synonyms and file extensions are missing, so it is above the midpoint but not fully comprehensive.	4 / 5
Distinctiveness Conflict Risk	The clinical-reporting niche with domain-specific triggers (CARE, ICH-E3, SAE, HIPAA, SOAP) is clearly distinct and unlikely to conflict with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (1131 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	13 / 16 Passed

Repository: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/clinical-reports/SKILL.md
Commit: d5ae560

Reviewed: 1 day 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.