treatment-plans

Generate concise (3-4 page), focused medical treatment plans in LaTeX/PDF format for all clinical specialties. Supports general medical treatment, rehabilitation therapy, mental health care, chronic disease management, perioperative care, and pain management. Includes SMART goal frameworks, evidence-based interventions with minimal text citations, regulatory compliance (HIPAA), and professional formatting. Prioritizes brevity and clinical actionability.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./bundled/skills/treatment-plans/SKILL.md

Quality

Content

56%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.

Operationally strong with concrete scripts, templates, and a validation workflow, but the body is far too long, inlines content that already exists as dedicated reference files, and repeatedly preaches brevity it does not practice.

Suggestions

Move the inlined specialty/regulatory/SMART-goal and the ~400-line styling material into the existing references/ and assets/ files and link them one level deep (e.g., 'See references/specialty_specific_guidelines.md'), cutting the body substantially.

Remove the redundant brevity sections ('Critical Principles', 'Concise Documentation', 'Quality Over Quantity', 'Brevity and Focus') and consolidate into one concise directive to reduce padding.

Trim the textbook medical content (condition lists, intervention catalogs, drug examples) that Claude already knows, keeping only skill-specific operational guidance.

Dimension	Reasoning	Score
Conciseness	At 1579 lines the body is noticeably verbose: it reproduces textbook medical knowledge Claude already knows (SMART definitions, per-specialty condition lists, drug/intervention catalogs) and preaches brevity repeatedly ('Critical Principles', 'Concise Documentation', 'Quality Over Quantity', 'Brevity and Focus (HIGHEST PRIORITY)') while itself being padded.	2 / 5
Actionability	Provides mostly executable guidance: concrete bash commands (pdflatex/xelatex, python check_completeness.py, validate_treatment_plan.py, generate_template.py, timeline_generator.py), named template files, and copy-paste LaTeX snippets, with only minor gaps.	4 / 5
Workflow Clarity	The 'Validation Workflow' gives a clear 7-step sequence (create -> check_completeness -> validate_treatment_plan -> review checklist -> generate PDF -> review with patient -> implement) with validation checkpoints present, though the explicit fix-and-retry loop on validation failure is not spelled out.	4 / 5
Progressive Disclosure	Bundle files exist (references/*.md guides, assets/STYLING_QUICK_REFERENCE.md) but the body never links them; their content (specialty guidelines, regulatory/HIPAA detail, SMART-goal frameworks, and the ~400-line 'Professional Document Styling' block) is inlined instead of split out, matching the 'content that should be separate is inline' anchor.	3 / 5
	Total	13 / 20 Passed

Description

71%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 specific, well-scoped description with concrete capabilities and good trigger-term coverage, but it omits an explicit 'Use when...' trigger clause, which caps its completeness score.

Suggestions

Append an explicit trigger clause, e.g., 'Use when creating medical treatment plans, care plans, or clinical documentation in LaTeX/PDF for any specialty.'

Add user-natural synonyms such as 'care plans' and 'clinical care plans' to broaden trigger-term coverage toward 5.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions and comprehensive coverage: 'Generate concise (3-4 page)... treatment plans in LaTeX/PDF format', six named specialty areas, and concrete features (SMART goal frameworks, evidence-based interventions, HIPAA compliance, professional formatting).	5 / 5
Completeness	The 'what' is clear and detailed, but there is no 'Use when...' clause or equivalent explicit trigger guidance; per rubric, a missing Use-when clause caps completeness at 3 even though the what is well stated.	3 / 5
Trigger Term Quality	Strong natural-term coverage ('treatment plans', 'rehabilitation', 'mental health care', 'chronic disease management', 'pain management', 'HIPAA', 'LaTeX/PDF'), but missing common synonyms a user might say (e.g., 'care plans', 'clinical plans').	4 / 5
Distinctiveness Conflict Risk	Clear niche (LaTeX/PDF medical treatment plans with HIPAA compliance and named specialties) is mostly distinct with only minor overlap risk against a generic clinical-reports skill.	4 / 5
	Total	16 / 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 (1580 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/treatment-plans/SKILL.md
Commit: ddcaa2a

Reviewed: 6 days 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.