CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

qutip

Quantum physics simulation library for open quantum systems. Use when studying master equations, Lindblad dynamics, decoherence, quantum optics, or cavity QED. Best for physics research, open system dynamics, and educational simulations. NOT for circuit-based quantum computing—use qiskit, cirq, or pennylane for quantum algorithms and hardware execution.

Quality

85%

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 qutip in K-Dense-AI/scientific-agent-skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured library skill: executable, copy-paste-ready examples; a concrete solver-selection decision guide; and clean progressive disclosure with five real, one-level-deep reference files. Weaknesses are minor — some duplicated reference listings, a couple of example-code blemishes (unused function, undefined variables in the HEOM snippet), and validation advice that lives in tips rather than in the workflows themselves.

Suggestions

Remove the closing 'References' section (or the inline 'See references/...' pointers) — the same five files are listed twice, costing tokens without adding navigation value.

Fix the two-qubit workflow: either use the defined compute_concurrence callback or delete it, and use a physically meaningful Hamiltonian (e.g., 0 or the interaction term) instead of qeye([2, 2]).

Make convergence validation an explicit step inside the simulation workflows (vary Hilbert space size / ntraj and compare) rather than only a tip at the end.

DimensionReasoningScore

Conciseness

The body is code-dense and assumes domain competence — no padding explaining what quantum mechanics or libraries are, and the Overview, Tips, and Troubleshooting sections are tight. Anchor 5 is missed mainly due to redundancy: the closing 'References' section re-lists all five reference files already linked inline in each section.

4 / 5

Actionability

Nearly all examples are complete, executable code covering common cases (damped oscillator, Jaynes-Cummings, Bell-state dephasing), and the solver-selection guide gives concrete decision rules. Minor gaps keep it below anchor 5: the HEOM example references undefined variables (ck_real, vk_real), and the two-qubit workflow defines an unused compute_concurrence function while calling mesolve with a qeye Hamiltonian instead of it.

4 / 5

Workflow Clarity

Workflows are clearly sequenced (parameters -> operators -> evolve -> plot) and the solver selection guide plus Tips ('Check convergence: Vary ntraj, Hilbert space size, and tolerances') and Troubleshooting sections provide most checkpoints. Validation is advisory rather than embedded as explicit steps in the workflows, so it sits at anchor 4 rather than 5.

4 / 5

Progressive Disclosure

SKILL.md is a genuine overview: each core section ends with a well-signaled one-level-deep pointer ('**See** references/time_evolution.md'), all five referenced files exist in the bundle, and no reference file points to further files. The closing References section gives an easy navigation index. This matches anchor 5.

5 / 5

Total

17

/

20

Passed

Description

87%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 explicit what/when structure, natural domain trigger terms, and excellent boundary guidance that names alternative skills for the excluded use case. Its only weakness is framing capabilities as research topics rather than concrete actions.

DimensionReasoningScore

Specificity

The description enumerates concrete capability areas — 'studying master equations, Lindblad dynamics, decoherence, quantum optics, or cavity QED' — going beyond anchor 3's 1-2 actions, but it frames capabilities as subject areas rather than explicit actions (simulate, solve, visualize), so it falls short of anchor 5's fully comprehensive action list.

4 / 5

Completeness

Explicitly answers both: what ('Quantum physics simulation library for open quantum systems') and when ('Use when studying master equations, Lindblad dynamics, decoherence, quantum optics, or cavity QED'), plus fit guidance ('Best for...') and an explicit NOT-for clause with alternatives — matching anchor 5.

5 / 5

Trigger Term Quality

Strong natural phrases users would say: 'master equations', 'Lindblad dynamics', 'decoherence', 'quantum optics', 'cavity QED', 'open system dynamics'. A few common domain terms users might naturally say (e.g., 'density matrix', 'Hamiltonian', 'dissipative systems') are missing, so it matches anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche (open quantum systems) with explicit boundary guidance — 'NOT for circuit-based quantum computing—use qiskit, cirq, or pennylane' — which actively prevents mis-triggering against adjacent quantum skills. Minimal conflict risk, matching anchor 5.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

synthetic-sciences/openscience

Path

backend/cli/skills/quantum/qutip/SKILL.md

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.