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.
85
81%
Does it follow best practices?
Impact
90%
1.40xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
89%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 a strong description with excellent trigger terms, clear 'when' guidance, and outstanding distinctiveness through explicit negative boundaries. Its main weakness is that it describes the domain and topics rather than listing concrete actions the skill performs (e.g., 'solve', 'simulate', 'plot'), which keeps specificity from reaching the top score.
Suggestions
Add concrete action verbs describing what the skill does, e.g., 'Solves master equations, simulates Lindblad evolution, models decoherence channels, and computes steady states for open quantum systems.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (quantum physics simulation for open quantum systems) and mentions some specific areas like master equations, Lindblad dynamics, decoherence, quantum optics, and cavity QED, but doesn't list concrete actions the skill performs (e.g., 'solve master equations', 'simulate Lindblad evolution', 'plot Wigner functions'). | 2 / 3 |
Completeness | Clearly 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). Also includes explicit negative guidance on when NOT to use it, which strengthens the 'when' clause. | 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', 'physics research'. Also includes negative triggers distinguishing from circuit-based quantum computing with specific alternative tool names. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche in open quantum systems simulation, and explicitly differentiates itself from circuit-based quantum computing tools (qiskit, cirq, pennylane), greatly reducing conflict risk with related quantum computing skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent actionability and progressive disclosure. The code examples are concrete and executable, and the reference structure is well-organized. The main weaknesses are moderate verbosity (three full workflow examples could be condensed or moved to references) and lack of explicit validation/verification steps in the simulation workflows.
Suggestions
Move the Common Workflows section (damped oscillator, entanglement dynamics, Jaynes-Cummings) to a references/examples.md file and keep only one brief example in the main skill to improve conciseness.
Add validation checkpoints to workflows, e.g., 'Verify Hilbert space convergence: re-run with N+5 and confirm results match within tolerance' or 'Check trace of density matrix ≈ 1.0 after evolution'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary verbosity. The Common Workflows section with three full examples (damped oscillator, entanglement dynamics, Jaynes-Cummings) is extensive and could be trimmed or moved to references. The Quick Start already demonstrates the pattern; the workflows are somewhat redundant. However, it doesn't over-explain basic concepts Claude would know. | 2 / 3 |
Actionability | All code examples are fully executable with proper imports, concrete parameter values, and complete workflows from setup to visualization. The solver selection guide provides clear decision criteria. Code is copy-paste ready throughout. | 3 / 3 |
Workflow Clarity | The workflows are clearly sequenced within individual examples, and the solver selection guide helps with decision-making. However, there are no validation checkpoints or error-recovery feedback loops—simulations can silently produce wrong results if Hilbert space is too small or parameters are wrong. The troubleshooting section exists but isn't integrated into workflows as verification steps. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview structure, each section providing essential code snippets while pointing to dedicated reference files (core_concepts.md, time_evolution.md, visualization.md, analysis.md, advanced.md). References are one level deep and clearly signaled with descriptive labels. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
25e1c0f
Table of Contents
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.