CtrlK
BlogDocsLog inGet started
Tessl Logo

treatment-plans

Format and structurally validate local treatment-plan documentation after clinical decisions have already been supplied and verified by authorized licensed professionals. Use for source traceability, clinician-authored intervention records, goals and checkpoints, shared-decision records, reconciliation handoffs, and release gates—not for clinical decision-making.

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A well-structured, actionable safety-critical skill body with a clear sequenced workflow, executable commands, and properly layered references. The only weakness is redundancy in the safety-boundary framing, which inflates token cost without adding clarity.

Suggestions

Consolidate the repeated safety framing: the 'Hard safety boundary', 'Required visible notice', 'Data gate', and 'Source boundaries' sections restate the same prohibition; merge into a single boundary block and reference it.

Trim the nine-item 'Never use it to' list to the most representative exclusions and point to references/safety_scope.md for the exhaustive set.

Move the full source-ledger citation list (FDA, WHO, NICE, AHRQ, CMS) entirely into references/source_ledger.md and keep only the routing rule inline.

DimensionReasoningScore

Conciseness

Mostly efficient and free of generic concept explanation, but the safety message is restated across four sections and the nine-item 'Never use it to' list is verbose even for a safety-critical skill.

2 / 3

Actionability

Provides copy-paste-ready, executable commands for generation, validation, and verification (e.g. 'python3 scripts/validate_treatment_plan.py ./local-plan-package') with concrete flags and paths.

3 / 3

Workflow Clarity

A clearly sequenced five-step workflow with an explicit deterministic-checks validation step and a release-gate checkpoint that stays blocked until human review completes.

3 / 3

Progressive Disclosure

SKILL.md is a concise overview with a one-level-deep Reference map; every referenced file under references/ and assets/ exists and is clearly signaled.

3 / 3

Total

11

/

12

Passed

Description

100%

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, third-person description that clearly states capabilities, natural trigger terms, and an explicit use-when clause while carving out a distinct, low-conflict niche. It is concise without sacrificing the what/when distinction.

DimensionReasoningScore

Specificity

Names multiple concrete actions ('Format and structurally validate local treatment-plan documentation') rather than vague language.

3 / 3

Completeness

Explicitly answers what ('Format and structurally validate…') and when ('Use for source traceability…') with an explicit trigger clause.

3 / 3

Trigger Term Quality

Covers natural domain terms a user would say: 'source traceability, clinician-authored intervention records, goals and checkpoints, shared-decision records, reconciliation handoffs, and release gates'.

3 / 3

Distinctiveness Conflict Risk

Highly specific clinical-documentation niche with an explicit 'not for clinical decision-making' guardrail, making conflict with other skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
K-Dense-AI/scientific-agent-skills
Reviewed

Table of Contents

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.