Qpu Submit
Submit a neutral-atom experiment_spec.json plus its Pulser sequence file to a Rydberg QPU on Pasqal Cloud, with an optional pre-calibration batch that measures the device's Rabi frequency and Rydberg resonance and compensates the submitted jobs. Writes batch IDs for harvest-and-analyze. For a QPU reached over SSH through a cluster scheduler, use submit-to-cea. Triggered by phrases like "submit this spec to the QPU", "run this sequence on Fresnel", "send it to the neutral-atom hardware".
Install
/plugin marketplace add pasqal-io/agent-marketplaceThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add pasqal-io/agent-marketplace --skill qpu-submitgit clone --depth 1 https://github.com/pasqal-io/agent-marketplace.git /tmp/agent-marketplace
mkdir -p ~/.claude/skills
cp -r /tmp/agent-marketplace/skills/qpu-submit ~/.claude/skills/qpu-submitPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# qpu-submit Submit a spec-driven scan to a QPU and record what was submitted. **One batch, one job per scan point** — one queue slot, one atom loading, one labelled object `harvest-and-analyze` reads back. RUNS ON: a QPU, through the cloud API. Billed shots, and a submitted batch cannot be recalled. Everything before the confirmation gate happens on this machine and costs nothing. This skill submits **whatever sequence file you give it**. It contains no physics of its own: the register, pulse schedule and observable all come from the `build_sequence()` / `compute_observable()` pair that `spec-to-sequence` generated. A worked example lives in [`examples/square_lattice_eom_quench/`](../../examples/square_lattice_eom_quench/). Device selection: `--device` (default: `spec["device"]`); for **SA1** also set `PASQAL_REGION=sa` and use a project with SA1 access. **Ruby (CEA)** is not on the Pasqal Cloud — use the `submit-to-cea` skill. ## Support scripts Paths like `support/…` below are relative to **this skill's directory** — expand them to the skill's absolute location when running commands from your project directory (keep outputs like `--out-dir` in your project, not the plugin). ``` support/ submit_qpu.py ← calibration + submission batch_tags.py ← the labels every batch carries (shared, do not edit here) pasqal_auth.py ← credentials, projects and credits (shared, do not edit here) ```
Details
- Skill name
qpu-submit- Repository
- pasqal-io/agent-marketplace
- Path
skills/qpu-submit/SKILL.md- License
- Apache-2.0
- Repo updated
- 3 November 2026
FAQ
What does the Qpu Submit skill do?
Submit a neutral-atom experiment_spec.json plus its Pulser sequence file to a Rydberg QPU on Pasqal Cloud, with an optional pre-calibration batch that measures the device's Rabi frequency and Rydberg resonance and compensates the submitted jobs. Writes batch IDs for harvest-and-analyze. For a QPU reached over SSH through a cluster scheduler, use submit-to-cea. Triggered by phrases like "submit this spec to the QPU", "run this sequence on Fresnel", "send it to the neutral-atom hardware".
How do I install the Qpu Submit skill?
Claude Code plugin: /plugin marketplace add pasqal-io/agent-marketplace. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Qpu Submit popular?
It lives in pasqal-io/agent-marketplace, which has 9 GitHub stars and 0 forks.
Related skills
Application to Idea
9pasqal-io/agent-marketplace
Scope a rough problem or application into a first technical idea for a neutral-atom (Rydberg) QPU: which documented Pulser method could serve it — MIS, QUBO, an Ising or XY simulation, a graph kernel — what would be measured, at what size, or an honest no-fit. Writes a note for idea-to-spec; use idea-to-spec when a protocol or paper exists. Triggered by phrases like "can neutral atoms do anything with my problem", "is this a fit for a Rydberg QPU", "I don't know what to measure on the QPU".
Apply Genci Tgcc Cea
9pasqal-io/agent-marketplace
Apply for QPU hours on Ruby (Pasqal Orion), the analogue neutral-atom machine at GENCI/CEA TGCC - via the French eDARI portal or the EuroHPC Quantum Access Pilot call - then get the TGCC computing account. For requests such as "apply for TGCC hours", "eDARI application", "apply for Ruby/Pasqal QPU allocation", "EuroHPC quantum hours", "Quantum Access Pilot", or "attach to a project / rattachement". Access only, not running experiments. Unsure which route fits? Use choose-access-method.
Choose Access Method
9pasqal-io/agent-marketplace
Decide which neutral-atom QPU access route to pursue - free CEA/GENCI/ EuroHPC access to Ruby (weeks of lead time, specific eligibility) versus Pasqal Cloud pay-as-you-go (today, any country, a card). For requests such as "how do I get QPU access", "which account should I use", "Pasqal Cloud vs CEA", "do I qualify for free QPU time", or "fastest way to real hardware". Hands off to create-pasqal-cloud-account or apply-genci-tgcc-cea: this skill is the decision, not the sign-up flow.
Spec to Sequence
9pasqal-io/agent-marketplace
Generate a Pulser sequence builder for a neutral-atom (Rydberg) experiment from an experiment_spec.json. Output is a *_sequence.py with two standardised functions — build_sequence() and compute_observable() — consumed by validate-emu, qpu-submit and harvest-and-analyze. Triggered by phrases like "generate the Pulser sequence", "write the sequence file for this spec", "spec to sequence", "turn the spec into Pulser code".
Ears Translator
8UserAd/ClaudeSkills
Translate user stories and informal requirements into EARS (Easy Approach to Requirements Syntax) format. Use when Claude needs to (1) convert user stories to formal requirements, (2) transform informal requirements into structured EARS format, (3) review and improve existing requirements using EARS patterns, (4) create testable, unambiguous system requirements. Triggers on requests like "convert to EARS", "write requirements", "formalize these user stories", "EARS format".
Jarvis
10thatmike1/claude-skills
The sidekick thread Mike talks to about all his other threads. It hands out work, hears back when results come in, and translates results he cannot eyeball. Use when the user says jarvis, or asks where to start, to fire agents and hear back, or to oversee one lane.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.