SKILLEMALL.ai

AC model-validation

Design or audit the clinical-validation study for an engineer-built medical-imaging model (segmentation, classification, or detection) before the validation report or manuscript is written. Covers patient-level split disjointness and the data-leakage taxonomy, tuning-on-test, internal versus genuine external validation, comparator design, single-run versus multi-seed variance, task-correct metric selection, test-set sizing, and CLAIM 2024 / TRIPOD+AI / STARD-AI reporting fit. Ships a deterministic split-leakage gate that proves patient disjointness by set arithmetic on the emitted split-assignment table. Does not build or train models — it integrates with MONAI / nnU-Net, it does not replace them.

Aperivue/medsci-skills Agent Skills author: Aperivue MIT 15 files · 3 scripts body ≈ 2 542 tokens Open the sourcegithub.com analyzed 27 h ago

Design or audit the clinical-validation study for an engineer-built medical-imaging model (segmentation, classification, or detection) before the validation…

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

AnalyzerData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
89
Run on models
none yet
Process rating
C
54/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: 11. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "triggers"
    • note frontmatter-key unknown frontmatter key "tools"

    Process rating: all ten parameters 54/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
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 7 mutating operations with no state check
    • 50When it triggers. No condition that starts the skill
    • 100Tools and files. Tools declared in frontmatter
    • 100Steps. 13 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2542 tokens
    • 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
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +3Description length 706: enough signal without eating the budget
    • +4Structure: 17 headings
    • +3Step-by-step instructions: 13 items
    • +4Has examples (2 code blocks)
    • +4Reference files are cited in the instructions (1 of 1)
    • +3All 1 scripts are documented

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