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.

72

Quality

87%

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

The canonical home for this skill is treatment-plans in K-Dense-AI/scientific-agent-skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exceptionally well-structured body: executable commands at every step, explicit validation and release gates, and clean one-level-deep disclosure into a real, well-organized bundle. Only slight redundancy in the safety-boundary repetition keeps it from full marks on conciseness.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence — it explains no general concepts — but the safety boundary material is repeated across "Hard safety boundary", "Source boundaries", and the workflow's release step, and the citation block is long; minor trimming would reach a 5.

4 / 5

Actionability

Fully executable copy-paste commands throughout: the generator invocation with flags, all six validation scripts with exact paths and arguments, the unittest discovery command, and the AST-parse one-liner — no pseudocode anywhere.

5 / 5

Workflow Clarity

A five-step sequence with explicit validation checkpoints (step 4 runs six deterministic checks), a release gate held "blocked" until every review completes, discrepancy-resolution requirements, and a final human-review checklist with sign-off — a complete feedback loop for a batch/risky operation.

5 / 5

Progressive Disclosure

The body is an overview pointing to one-level-deep references, each clearly signaled by purpose in the reference map, with references/README.md providing reading order; all referenced files (8 references, 6 asset templates, 8 scripts) verified to exist.

5 / 5

Total

19

/

20

Passed

Description

82%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 strong description with an explicit what, a concrete Use-for trigger list, and a clear negative boundary. Its only weakness is that it states just two concrete capabilities, relying on the trigger list rather than a fuller enumeration of actions.

DimensionReasoningScore

Specificity

The description names the domain ("local treatment-plan documentation") and two concrete actions ("Format and structurally validate"), but does not enumerate several distinct actions as the score-4 anchor requires; coverage of what the skill does is otherwise carried by trigger phrases rather than capability statements.

3 / 5

Completeness

It explicitly answers what ("Format and structurally validate local treatment-plan documentation after clinical decisions have already been supplied and verified...") and when ("Use for source traceability... release gates—not for clinical decision-making"), with concrete trigger phrases plus an explicit exclusion.

5 / 5

Trigger Term Quality

"source traceability, clinician-authored intervention records, goals and checkpoints, shared-decision records, reconciliation handoffs, and release gates" provides good, natural keyword coverage a user in this domain would actually say, though it lacks synonyms or file-format variations that would justify a 5.

4 / 5

Distinctiveness Conflict Risk

"treatment-plan documentation" with clinician-authored-record triggers carves out a clear niche, and the "not for clinical decision-making" exclusion further separates it from adjacent skills, minimizing misfire risk.

5 / 5

Total

17

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
K-Dense-AI/claude-scientific-writer
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.