treatment-plans

Generate concise (typically 1–4 pages) patient-centered medical treatment plans in LaTeX/PDF when a clinician needs an actionable plan with SMART goals, evidence-based interventions, monitoring, and HIPAA-aware documentation.

Quality

79%

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

Quality

Content

71%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 highly actionable with executable commands and a concrete LaTeX skeleton, and the workflow is well sequenced with a validation step. Its main weaknesses are redundant restatement of the length and front-page-summary patterns across sections and several orphaned bundle files (the references/ directory and two asset guides) that are never surfaced from the body.

Suggestions

Add a short 'References' section that links to the references/ files (goal_setting_frameworks.md, intervention_guidelines.md, regulatory_compliance.md, specialty_specific_guidelines.md, treatment_plan_standards.md) and the asset guides (STYLING_QUICK_REFERENCE.md, quality_checklist.md) so the existing bundle is navigable one level deep.

De-duplicate the document-length strategy and front-page executive-summary pattern, which currently appear in both 'Key Features' and 'Implementation Details'; keep the detailed version in one place and cross-reference it.

Make the validation feedback loop explicit in the Example Usage workflow (e.g., 'If check_completeness or validate_treatment_plan reports errors, fix the .tex and re-run before distributing') and either add scripts/generate_schematic.py or remove the reference to it.

Reference the style package by path (assets/medical_treatment_plan.sty) in the Dependencies or Implementation Details so the LaTeX styling dependency is concretely located.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and free of basic-concept padding, but the document-length strategy and front-page executive-summary pattern are each restated across 'Key Features' and 'Implementation Details', and the 'Validation logic' section restates what the scripts already check — more than minor trimming is needed.	3 / 5
Actionability	Provides copy-paste-ready bash commands with concrete flags (generate_template.py --type, xelatex, check_completeness.py, validate_treatment_plan.py, timeline_generator.py), an executable LaTeX skeleton using the custom environments, and a template-selection map from condition to file, covering the common cases.	5 / 5
Workflow Clarity	A clear numbered 1–5 sequence (generate → diagram → compile → validate → timeline) with the validation checkpoint at step 4, but the validate→fix→retry feedback loop is only implicit rather than explicitly stated, leaving a minor validation gap below the 5 anchor.	4 / 5
Progressive Disclosure	The body signals scripts and template files that exist in the bundle, but the entire references/ directory (6 files) and the asset guides STYLING_QUICK_REFERENCE.md and quality_checklist.md are never pointed to, and generate_schematic.py is referenced yet absent from scripts/ — references present in the bundle but not clearly signaled.	3 / 5
	Total	15 / 20 Passed

Description

87%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, third-person, and explicitly covers both what the skill does and when to use it with concrete clinical trigger terms. Its only gap is that the capability is framed around a single generation action with rich output attributes rather than multiple distinct actions.

Dimension	Reasoning	Score
Specificity	Names the domain (medical treatment plans in LaTeX/PDF) and several concrete deliverable attributes (SMART goals, evidence-based interventions, monitoring, HIPAA-aware documentation), but centers on a single action verb ('Generate') rather than multiple distinct actions, so it sits above the 3 anchor but short of 5.	4 / 5
Completeness	Explicitly answers both 'what' ('Generate concise... treatment plans in LaTeX/PDF') and 'when' ('when a clinician needs an actionable plan with SMART goals, evidence-based interventions, monitoring, and HIPAA-aware documentation') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms a clinician-oriented user would say ('medical treatment plans', 'LaTeX/PDF', 'clinician', 'SMART goals', 'HIPAA'), with good keyword coverage; a few natural synonyms (e.g., 'care plan', 'clinical plan') and file extensions (.tex/.pdf) are missing, keeping it at 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — patient-centered medical treatment plans with HIPAA-aware documentation in LaTeX/PDF — with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	14 / 16 Passed

Repository: aipoch/medical-research-skills
Path: scientific-skills/Other/treatment-plans/SKILL.md
Commit: 63c61d3

Reviewed: 4 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.