cirq
FeaturedGoogle quantum computing framework. Use when targeting Google Quantum AI hardware, designing noise-aware circuits, or running quantum characterization experiments. Best for Google hardware, noise modeling, and low-level circuit design. For IBM hardware use qiskit; for quantum ML with autodiff use pennylane; for physics simulations use qutip.
Install
Quality Score: 99/100
Skill Content
Details
- Author
- K-Dense-AI
- Repository
- K-Dense-AI/scientific-agent-skills
- Created
- 9 months ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
cirq
Google quantum computing framework. Use when targeting Google Quantum AI hardware, designing noise-aware circuits, or running quantum characterization experiments. Best for Google hardware, noise modeling, and low-level circuit design. For IBM hardware use qiskit; for quantum ML with autodiff use pennylane; for physics simulations use qutip.
akcli-circuit-design
Read, analyze, diff, and draw electronic schematics with the zero-dependency `akcli` CLI (akcli) — no Altium or KiCad install required. Use this skill whenever the task involves: reading or parsing an Altium .SchDoc/.SchLib/.PcbDoc or a KiCad .kicad_sch/.kicad_sym/.kicad_pcb; extracting a netlist; running ERC, power-rail, BOM, or a design review on a schematic; producing a pin map / pinout / MCU pin->net table; diffing two schematic revisions (v1 vs v2); drawing or editing a KiCad schematic from an op-list; or working with JLC/LCSC/EDA parts, footprints, and connectivity. Triggers on keywords: SchDoc, kicad_sch, schematic, netlist, ERC, electrical rule check, design review, power rails, pinmap, pinout, schematic diff, draw KiCad, op-list.
akcli-circuit-debug
Systematically diagnose misbehaving schematics and `akcli` tool failures — no Altium or KiCad install required. Use this skill whenever the task involves: debugging net connectivity (a net that is split, merged wrongly, missing, or a pin that floats when it should not); triaging `akcli check` findings (real fault vs false positive, deciding whether a clean pass is trustworthy); investigating why `akcli plan`/`akcli draw` refused to write or what an exit code means; recovering from a failed apply (backup/rollback); or classifying parse failures and unsupported-input refusals before reporting a bug upstream. Triggers on keywords: debug, diagnose, troubleshoot, net split, floating pin, wrong net merge, false positive, ERC finding, exit code, parse error, refused, dangling endpoint, connectivity gate, rollback, backup, corrupt SchDoc, unsupported format.