SKILLEMALL.ai

AD qutip

Simulate and audit closed and open quantum-system models with QuTiP 5, including deterministic, trajectory, steady-state, spectral, and phase-space workflows. Use for local quantum-dynamics work where physical assumptions, dimensions, and numerical convergence must be explicit.

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

Simulate and audit closed and open quantum-system models with QuTiP 5, including deterministic, trajectory, steady-state, spectral, and phase-space workflows.

As a process D 45/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

AnalyzerGitHubAI and agentstype 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
D
45/100
Unfinished process
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: 13. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note edit-residue the text marks something as outdated (lines 181, 212, 244): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 45/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
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 3 mutating operations with no state check
    • 60Tools and files. Uses tools (web, python) that frontmatter does not declare
    • 100Steps. 36 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3523 tokens
    • 100Progress reporting. Reports progress
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low 15 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)
    • -31 of 7 scripts are never mentioned in SKILL.md
    • +2Single-language instructions
    • +3Description length 278: enough signal without eating the budget
    • +4Structure: 16 headings
    • +3Step-by-step instructions: 36 items
    • +3Output format is stated explicitly
    • +4Has examples (9 code blocks)
    • +4Reference files are cited in the instructions (5 of 5)
    • +1License stated

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