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

72%

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 ./.claude/skills/treatment-plans/SKILL.md

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with concrete scripts, templates, and validation workflows, but it is verbose and monolithic, inlining large reference-worthy sections rather than offloading them to the existing bundle files.

Suggestions

Move the 'Professional Document Styling' section and specialty/regulatory detail into the existing references/ and assets/ files, replacing the inline content with one-line signaled pointers (e.g., 'See references/specialty_specific_guidelines.md').

Consolidate the repeated brevity/first-page-summary guidance, which is restated in 'Document Length Options', 'Concise Documentation', 'Best Practices', and 'First Page Summary', into a single authoritative section.

Remove generic LaTeX troubleshooting, tlmgr, and CTAN installation guidance that Claude already knows, keeping only skill-specific styling instructions.

Dimension	Reasoning	Score
Conciseness	The ~1580-line body repeats the brevity/first-page-summary guidance across multiple sections and inlines a large LaTeX styling/troubleshooting/CTAN-install section that explains concepts Claude already knows, so while mostly accurate it is padded and could be tightened considerably.	2 / 3
Actionability	Provides fully executable commands (check_completeness.py, validate_treatment_plan.py, timeline_generator.py, generate_template.py with flags), concrete LaTeX box environments with copy-paste code, named template files, and specific worked examples with dosing/goals, matching the 'fully executable, copy-paste ready' anchor.	3 / 3
Workflow Clarity	A clear 7-step validation workflow sequences create → check completeness → validate quality → review checklist → generate PDF, supported by validation scripts and a quality checklist with explicit checkpoints, matching the 'clear sequence with explicit validation steps' anchor.	3 / 3
Progressive Disclosure	A rich bundle exists (references/, scripts/, assets/) and referenced files are real, but the monolithic body inlines content that belongs in the provided reference files (specialty guidelines, regulatory compliance, the ~400-line styling section) instead of clearly signaling one-level-deep pointers to them.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 distinctive, clearly conveying what the skill produces, but it omits an explicit 'Use when...' trigger clause, which caps its completeness and weakens trigger-term naturalness.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger situations (e.g., 'Use when creating care plans, clinical treatment documentation, or specialty-specific plans for diabetes, rehab, mental health, perioperative, or pain management').

Include common user-facing phrasings like 'care plan' and 'clinical documentation' alongside the specialty list to improve trigger-term naturalness.

Tighten the long specialty enumeration into a trigger-focused sentence so the description leads with when-to-use context rather than only capabilities.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Generate concise (3-4 page), focused medical treatment plans in LaTeX/PDF format', 'Includes SMART goal frameworks, evidence-based interventions with minimal text citations, regulatory compliance (HIPAA), and professional formatting'), matching the 'lists multiple specific concrete actions' anchor rather than the partial-action anchor at 2.	3 / 3
Completeness	Clearly answers 'what' the skill does, but lacks any explicit 'Use when...' clause or equivalent trigger guidance in the description; per the rubric a missing 'when' trigger caps completeness at 2 even though the body has a separate 'When to Use' section.	2 / 3
Trigger Term Quality	Contains relevant specialty terms (treatment plans, LaTeX/PDF, rehabilitation therapy, mental health care, chronic disease management, perioperative care, pain management, HIPAA) but presents them as capability enumeration rather than natural user trigger phrasing, and omits common variations like 'care plan' or 'clinical documentation'; no explicit 'Use when...' trigger phrasing is present.	2 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (medical treatment plans in LaTeX/PDF with SMART goals and HIPAA compliance) with distinct triggers unlikely to conflict with adjacent clinical skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	10 / 12 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 (1581 lines); consider splitting into references/ and linking	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: K-Dense-AI/claude-scientific-writer
Path: .claude/skills/treatment-plans/SKILL.md
Commit: 4717803

Reviewed: about 10 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.