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.
Install with Tessl CLI
npx tessl i github:K-Dense-AI/claude-scientific-skills --skill qutipOverall
score
93%
Does it follow best practices?
Validation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines its specialized domain (open quantum systems simulation), provides rich trigger terms that physicists would naturally use, and explicitly distinguishes itself from circuit-based quantum computing tools. The 'NOT for' clause is particularly valuable for preventing skill conflicts in a multi-skill environment.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and domains: 'master equations, Lindblad dynamics, decoherence, quantum optics, cavity QED' and clarifies use cases like 'physics research, open system dynamics, educational simulations'. | 3 / 3 |
Completeness | Clearly answers both what ('Quantum physics simulation library for open quantum systems') and when ('Use when studying master equations, Lindblad dynamics...') with explicit trigger guidance and even includes a 'NOT for' clause to prevent misuse. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a physicist would use: 'master equations', 'Lindblad dynamics', 'decoherence', 'quantum optics', 'cavity QED', 'open quantum systems'. Also includes negative triggers distinguishing from circuit-based tools. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche (open quantum systems vs circuit-based quantum computing). The explicit 'NOT for' clause naming competing tools (qiskit, cirq, pennylane) directly prevents conflicts with quantum algorithm skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
88%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill with excellent actionability and progressive disclosure. The code examples are complete and executable, and the content efficiently covers QuTiP's capabilities without unnecessary explanation. The main weakness is the lack of explicit validation steps in workflows—users could benefit from guidance on verifying simulation correctness (e.g., checking convergence, validating Hilbert space truncation).
Suggestions
Add validation checkpoints to common workflows, such as 'Verify convergence by comparing results with ntraj=100 vs ntraj=500' or 'Check that increasing N doesn't change results significantly'
Include a brief troubleshooting feedback loop in workflows: 'If results look unphysical, first check Hilbert space dimension, then verify operator definitions'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing executable code examples without explaining basic quantum mechanics concepts Claude already knows. Every section delivers actionable information without padding. | 3 / 3 |
Actionability | All code examples are fully executable and copy-paste ready, from installation commands to complete simulation workflows. The Jaynes-Cummings and damped oscillator examples are complete, runnable scripts. | 3 / 3 |
Workflow Clarity | The common workflows section provides clear sequences, but lacks explicit validation checkpoints. For simulations that could fail silently (wrong Hilbert space dimension, numerical instabilities), there are no feedback loops to verify correctness before proceeding. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear overview, quick start, and well-signaled one-level-deep references to detailed documentation files. The references section clearly maps topics to specific files for easy navigation. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
94%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 15 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 15 / 16 Passed | |
- 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.