Menú
High-level orchestration skill for QEC research workflows. Initializes and updates project state, keeps a durable research log, routes work to future domain skills and MCP backends, and enforces explicit validation and provenance.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Provides guidance for choosing among QEC decoder backends such as ldpc, PyMatching, fusion-blossom, Chromobius, MWPF, tesseract-decoder, and MQT QECC based on artifact shape, code family, noise model, and validation goals.
Guides exact-MWPM graphlike decoding with fusion-blossom, including erasure-aware matching updates, while keeping clear boundaries with PyMatching and non-graphlike decoder lanes.
Provides guidance for decoding graphlike Stim detector models and sampled trajectories with PyMatching, using the repo's registry-backed decoder service and explicit graphlike-DEM constraints.
Guides search-based decoder planning with tesseract-decoder for small or medium QEC studies, keeping its baseline value separate from scalable matching or hypergraph lanes.
Guides use of MQT QECC for toolkit-native code, decoder, color-code, and state-preparation workflows while keeping clear boundaries with Stim-native and qLDPC-native lanes.
Guides reproduction of folded-H surface-code cultivation workflows from the MSC_foldedH repo, including sample-circuit inspection, handoff runs, and boundaries around the currently supported stabilizer-based escape path.
| name | qec-research |
| description | High-level orchestration skill for QEC research workflows. Initializes and updates project state, keeps a durable research log, routes work to future domain skills and MCP backends, and enforces explicit validation and provenance. |
| version | 0.1.0 |
| author | QEC Research Skills |
| license | MIT |
| tags | ["QEC","research","orchestration","state","provenance"] |
| dependencies | [] |
Use this skill to coordinate a QEC research task at the project level:
Use this skill when the user asks for overall project progress, research planning, repo structure, state updates, or cross-cutting workflow decisions.
Do not use this skill when a narrower domain skill exists and the task is purely local to that workflow.
Required files:
research-state.yamlresearch-log.mdAssumptions:
research-state.yaml.research-log.md.research-state.yaml and research-log.md before closing substantive work.Before closing work:
Problem: the repo structure evolves, but the state file still describes an older plan.
Fix: update current_focus, phase, decisions, and next_actions together.
Problem: too many skills get proposed before the core contract exists.
Fix: record the proposed skill in the backlog, but do not add it until it supports a real demo or workflow.
Problem: a plan assumes Stim, ldpc, Lean, or QUITS without stating why.
Fix: add the backend decision and rationale to research-state.yaml.