Qubit Desk — will your circuit actually run on that device?

Paste an OpenQASM 2.0/3.0 circuit and your target device's calibration data, and find out in one sitting whether it will run, whether its signal survives decoherence, and what the run costs. A free in-browser read parses the QASM properly — expanding for-loops onto the qubits each iteration touches and register broadcasts into real operation counts, costing a gate defined in the file from its own body, and never counting a definition's body as circuit — then runs fourteen named checks: width, the native basis and each foreign gate's decomposition cost, the coupling map and the SWAPs routing forces, mid-circuit measurement against what the device supports, the critical path against T1 and T2, the success probability the error rates imply, and the shot and parameter-shift gradient budget against the session. A check whose device field is missing reports as not-assessable, never as a pass. Three metered lanes then work the run: hardware feasibility, the decoherence and mitigation budget, and the shot and gradient plan. A derived work of three SkillSafe skills, each credited on the lane it informs: @k-dense-ai/qiskit for hardware execution, @k-dense-ai/qutip for open-system dynamics, and @k-dense-ai/pennylane for the variational surface.

Every public app is built from a security-scanned skill and must pass a clean scan — skill and frontend — before it can be listed. Have a skill of your own? Turn it into an app — or read the step-by-step walkthrough.