Hardware-agnostic quantum ML framework with automatic differentiation. Use when training quantum circuits via gradients, building hybrid quantum-classical models, or needing device portability across IBM/Google/Rigetti/IonQ. Best for variational algorithms (VQE, QAOA), quantum neural networks, and integration with PyTorch/JAX/TensorFlow. For hardware-specific optimizations use qiskit (IBM) or cirq (Google); for open quantum systems use qutip.
88
86%
Does it follow best practices?
Impact
89%
1.07xAverage score across 3 eval scenarios
Passed
No known issues
Quality
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 hits all the marks. It provides specific capabilities, rich trigger terms that practitioners would naturally use, explicit 'Use when' guidance, and even includes boundary conditions that distinguish it from related skills. The negative triggers (when to use qiskit, cirq, or qutip instead) are a particularly strong feature for disambiguation.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and capabilities: automatic differentiation, training quantum circuits via gradients, building hybrid quantum-classical models, device portability, variational algorithms (VQE, QAOA), quantum neural networks, and integration with specific ML frameworks. | 3 / 3 |
Completeness | Clearly answers both 'what' (hardware-agnostic quantum ML framework with automatic differentiation) and 'when' (explicit 'Use when' clause covering training quantum circuits, building hybrid models, needing device portability). Also includes helpful negative triggers distinguishing when NOT to use it. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a user would say: 'quantum ML', 'quantum circuits', 'gradients', 'hybrid quantum-classical', 'VQE', 'QAOA', 'quantum neural networks', 'PyTorch', 'JAX', 'TensorFlow', and specific hardware vendors (IBM, Google, Rigetti, IonQ). These are terms practitioners would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche in quantum ML. Explicitly differentiates itself from related skills (qiskit for IBM-specific, cirq for Google-specific, qutip for open quantum systems), which greatly reduces conflict risk. | 3 / 3 |
Total | 12 / 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 strong actionability and excellent progressive disclosure. The code examples are executable and cover the key use cases (classification, VQE, device portability). Main weaknesses are some verbosity in best practices/resource sections and missing validation/convergence checkpoints in the optimization workflows.
Suggestions
Add convergence checking or validation steps to the optimization workflows (e.g., 'Check if energy has converged within threshold before proceeding' or 'Verify circuit output dimensions match expectations')
Trim the Best Practices section to 4-5 non-obvious items — remove entries like 'Start with simulators' and 'Test locally' which Claude would naturally do
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some unnecessary verbosity. The 'Best Practices' section has 10 items, several of which are obvious to Claude (e.g., 'Start with simulators', 'Test locally'). The 'Resources' section with external links adds limited value. The bulleted lists under Core Capabilities are somewhat padded. However, the code examples are lean and the overall structure is efficient. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code examples for the quick start, variational classifier, VQE workflow, and device switching. Installation commands are concrete with specific plugin packages. The code examples include imports, device creation, circuit definition, and optimization loops — all directly runnable. | 3 / 3 |
Workflow Clarity | The common workflows are clearly numbered (1. Define ansatz, 2. Train; 1. Build Hamiltonian, 2. Define ansatz, 3. Optimize) which is good. However, there are no validation checkpoints — no steps to verify circuit correctness, check convergence, validate Hamiltonian construction, or handle errors. For iterative optimization workflows, missing convergence checks and error handling caps this at 2. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure. The main file provides a concise overview with executable quick-start examples, then clearly signals one-level-deep references for each major topic area (quantum_circuits.md, quantum_ml.md, etc.). The 'Detailed Documentation' section provides a clean navigation index. References are well-organized and clearly labeled. | 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 | |
b58ad7e
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.