SKILLEMALL.ai
GitHub ↗ RU Sign in

AC treatment-plans

Formats and structurally validates 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.

K-Dense-AI/claude-scientific-skills Agent Skills author: K-Dense-AI MIT 23 files · 8 scripts body ≈ 2 962 tokens Open the sourcegithub.com↗ analyzed 13 h ago

Formats and structurally validates local treatment-plan documentation after clinical decisions have already been supplied and verified by authorized licensed…

As a process C 52/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches

AnalyzerWriting and documentsAI and agentsFinancetype 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
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
90
Run on models
none yet
Process rating
C
52/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

    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 · 0

    ✓ No critical or high findings

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

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 52/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 50When it triggers. No condition that starts the skill
    • 60Tools and files. Uses tools (web) that frontmatter does not declare
    • 100Steps. 59 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2962 tokens
    • 100Running it twice. Mutating operations check current state
    • 100Progress reporting. Reports progress
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

    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
    • +3Output format is not stated: the model decides each time
    • -31 of 8 scripts are never mentioned in SKILL.md
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 367: enough signal without eating the budget
    • +4Structure: 15 headings
    • +3Step-by-step instructions: 59 items
    • +4Has examples (4 code blocks)
    • +4Reference files are cited in the instructions (8 of 8)
    • +1License stated

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

    In the sandbox The scripts kept to themselves

    The skill's scripts were run in a throwaway machine: no network, fake keys in the home directory, a tracer watching. We wrote down what they did. Reaching for the network or for secrets caps the technical grade at C; a quiet run adds no points.

    Запущено 8 скриптов; каждому дали двадцать секунд, поддельный домашний каталог с ключами и сеть, в которой ничего нет.

    Из них 7 не дошли до работы, и об их поведении мы ничего не узнали.

    scripts/_common.pyничего за пределами своей папки
    scripts/check_completeness.pyне запустился: check_completeness.py: error: the following arguments are required: package
    scripts/check_consistency.pyне запустился: check_consistency.py: error: the following arguments are required: package
    scripts/generate_template.pyне запустился: generate_template.py: error: the following arguments are required: --output-dir
    scripts/privacy_process_check.pyне запустился: privacy_process_check.py: error: the following arguments are required: package
    scripts/timeline_generator.pyне запустился: timeline_generator.py: error: the following arguments are required: package, --output
    scripts/validate_traceability.pyне запустился: validate_traceability.py: error: the following arguments are required: package
    scripts/validate_treatment_plan.pyне запустился: validate_treatment_plan.py: error: the following arguments are required: path

    5 Oct 2026