SKILLEMALL.ai
GitHub ↗ RU Sign in

CD 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.

FreedomIntelligence/OpenClaw-Medical-Skills Agent Skills author: FreedomIntelligence 13 files · 4 scripts body ≈ 13 002 tokens Open the sourcegithub.com↗ analyzed 12 h ago

Generate concise (3-4 page), focused medical treatment plans in LaTeX/PDF format for all clinical specialties.

As a process D 37/100 · Unfinished process — References files that are not bundled: assets/medical_treatment_plan.sty

GeneratorLaTeXPDFWriting and documentsSecurityLegaltype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
81/100
safety, quality, tests
Safety 60%
90
Quality 40%
67
Run on models
none yet
Process rating
D
37/100
Unfinished process
References files that are not bundled: assets/medical_treatment_plan.sty
Tools and files w 18
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: RA-Skills

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

Dangerous commands medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 2

✓ No critical or high findings

Medium and low: 2
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Read Write Edit Bash
  • medium Dangerous commands cmd-privilege SKILL.md:1387
    Privilege escalation / world-writable permissions
    sudo cp assets/medical_treatment_plan.sty /usr/local/texlive/texmf-local/tex/latex/

Files scanned: 13. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 13002 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: assets/medical_treatment_plan.sty

Process rating: all ten parameters 37/100

Will not run. References files that are not bundled: assets/medical_treatment_plan.sty
  • 0Tools and files. 1 referenced file(s) missing: assets/medical_treatment_plan.sty
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 8 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 40Execution cost. Instruction body is 13002 tokens: crowds the task out of the window
  • 50Failures and branches. 0 branches, has a failure section
  • 85Steps. 599 steps, 2 vague phrases
  • 100Consistency. Name and required fields are in place
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 16 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • -45 reference files, but SKILL.md never points to them: the model will not open them
  • +1No license
  • +2Single-language instructions
  • +3Description length 457: enough signal without eating the budget
  • +4Structure: 105 headings
  • +3Step-by-step instructions: 599 items
  • +4Has examples (30 code blocks)
  • +3All 4 scripts are documented

Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.