Hackathon Quantinuum

Enables building and deploying quantum computing applications with Quantinuum, Guppy, Selene, and Fly.io. Use for the OpenClaw Clinical Hackathon, clinical o...

Security Scan

The skill's code, instructions, and required artifacts are consistent with its stated purpose (scaffolding, running, and deploying Guppy/Selene quantum apps), with only routine operational cautions about secrets, CORS, and running deployment helpers.

Purpose & Capability

The name/description (Quantinuum + Guppy + Selene + Fly.io + Lovable frontend) match the included templates and scripts: FastAPI backend template, React frontend, and deploy scripts are present. There are no unrelated credentials or binaries required by the manifest. The files and docs align with the stated purpose of building and deploying quantum web apps and hackathon demos.

Instruction Scope

Runtime instructions direct the agent/user to run the provided Python scripts to scaffold services and to deploy using Fly.io. The docs explicitly instruct managing API keys via Fly.io secrets and warn about PHI — appropriate for clinical demos. Two operational notes: (1) the Selene template enables permissive CORS (allow_origins = ["*"]) by default (the docs note to restrict it in production), and (2) the documentation includes a curl | sh snippet to install flyctl; piping install scripts is common but potentially risky if used blindly. Overall instructions stay within the skill's purpose but require the user to apply standard operational security before production use.

Install Mechanism

There is no automated install spec for the skill bundle (instruction-only), and code/templates are provided inline. That minimizes hidden-install risk. The docs reference installing flyctl (including a curl | sh example) and standard package installation (pip, npm) for the generated apps; these are expected for the described workflow but should be executed with standard caution.

Credentials

The skill manifest declares no required environment variables, which is reasonable for a template bundle. However the instructions and templates reference typical secrets like QUANTUM_API_KEY (Quantinuum), VITE_API_KEY (frontend), and recommend using Fly.io secrets. This is coherent but important: real deployments will require secret env vars and the frontend template can pick up VITE_API_KEY if set — users must not place sensitive keys in frontend builds or commit them to source. The number and type of env vars referenced are proportional to deploying to hardware and hosting on Fly.io.

Persistence & Privilege

The skill does not request always-on inclusion, does not modify other skills, and contains only templates/scripts that run in the user's environment. There is no installer creating persistent system-level components in the manifest. Generated apps may be configured to run continuously on Fly.io depending on fly.toml, but that's user-controlled.

Assessment

This bundle appears to be what it claims: templates and scripts for building quantum-backed web apps and deploying them to Fly.io. Before running anything, review the included scripts (scripts/*.py) to see what commands they execute (they likely call flyctl, docker/npm, and may run subprocesses). Do not paste production API keys into frontend code — use Fly.io secrets and keep QUANTUM_API_KEY server-side. Tighten CORS (do not leave allow_origins = ["*"]) and add authentication/rate-limiting before exposing services. Avoid blindly running curl | sh from docs; install flyctl from an official source you trust. If you plan to handle clinical data, follow the skill's own advice: use synthetic/de‑identified data and ensure HIPAA/DPA compliance and data residency controls. If you want extra assurance, request the contents of scripts/create_quantum_app.py and scripts/flyio_deploy.py so you can inspect any subprocess calls or network operations they perform.

QuantinuumClaw – Quantum Guppy/Selene Stack

This skill provides everything needed to build production-ready quantum applications using Quantinuum (hardware/emulator), Guppy (quantum language), Selene (FastAPI backend), and Fly.io (deployment), with optional Lovable frontend. It is tuned for the OpenClaw Clinical Hackathon and general quantum web apps.

When to Use This Skill

Use when:

• Building for the OpenClaw Clinical Hackathon or any clinical/healthcare quantum project
• Building web applications that use quantum computing (optimization, chemistry, ML, random, crypto)
• Deploying quantum algorithms as REST APIs or creating dashboards for quantum results
• User mentions: clinical, healthcare, drug discovery, treatment optimization, patient stratification, molecular simulation, clinical trials, Guppy, Selene, Fly.io

Example requests: "Build a quantum portfolio optimizer with a web interface" · "Deploy my Guppy algorithm to the cloud" · "Create a clinical molecular simulation demo" · "Set up a quantum ML service on Fly.io"

Stack at a Glance

Component	Role
Quantinuum	Quantum hardware (H-series) or emulator
Guppy	Quantum programming (circuits, gates, measurement)
Selene	FastAPI backend that runs Guppy and exposes REST API
Fly.io	Hosts the Selene backend in the cloud
Lovable	React/TS frontend template; use assets/lovable-template/ or any app that calls the Selene API

Quick Start (One Command)

From the repo root:

python3 scripts/create_quantum_app.py \
  --app-name "clinical-demo" \
  --use-case "chemistry" \
  --description "Clinical molecular simulation" \
  --deploy

Then set VITE_API_URL in the frontend to your Fly.io app URL (e.g. https://clinical-demo.fly.dev).

Clinical use-case → --use-case mapping:

Clinical idea	--use-case	Notes
Drug discovery / molecular sim	chemistry	Molecules, energy, properties
Treatment / resource optimization	optimization	QAOA-style optimization
Patient stratification / ML	ml	Quantum ML models
Trial randomization	random	Quantum RNG
Secure keys / protocols	crypto	Quantum-safe crypto

General use cases (portfolio, finance, etc.) also use optimization, chemistry, ml, random, crypto, or finance. See references/clinical-use-cases.md for detailed clinical mappings.

Full Workflow: Creating a Quantum Application

Step 1: Define the use case

Identify the problem (optimization, simulation, ML, cryptography, clinical, etc.).

Step 2: Create Selene backend

python3 scripts/setup_selene_service.py \
  --app-name "my-quantum-app" \
  --use-case "chemistry" \
  --description "Quantum chemistry simulator"

This creates a backend dir with FastAPI, health check, Dockerfile, and fly.toml.

Step 3: Implement your Guppy circuit

Edit my-quantum-app/main.py → QuantumService._run_real_quantum(). Use references/guppy_guide.md for syntax. For clinical: chemistry (molecule, shots, precision), optimization (objective, constraints), ML (features, epochs).

Step 4: Deploy to Fly.io

python3 scripts/flyio_deploy.py --app-name "my-quantum-app" --service-dir "my-quantum-app" --region "lhr"

Set secrets with fly secrets set; use emulator for demos if preferred.

Step 5: Frontend

Use assets/lovable-template/ or run:

python3 scripts/lovable_integrate.py \
  --app-name "my-frontend" \
  --backend-url "https://my-quantum-app.fly.dev" \
  --quantum-use-case "chemistry"

Then npm install and npm run dev in the frontend dir.

Step 6: Connect and test

Point frontend VITE_API_URL to the Fly.io backend; hit /health to verify.

Clinical Use Case Cheat Sheet

• Drug discovery / molecular simulation: chemistry — VQE-style energy/property in Guppy; expose molecule type and params via API.
• Treatment / resource optimization: optimization — Define objective (cost, wait time); run QAOA in Selene; display results in UI.
• Patient stratification / classification: ml — Map patient features to model inputs; return risk/stratum or classification.
• Randomization (e.g. trials): random — Quantum RNG from Guppy; expose bits/shots in API.
• Security / key material: crypto — Key generation or quantum-safe primitives; keep keys on backend only.

Data and Compliance (Clinical / Hackathon)

• Demos: Use synthetic or de-identified data only. Do not send real PHI to quantum backends or store in Fly.io without a compliance plan.
• API keys: Store in Fly.io secrets (fly secrets set), never in code or frontend.
• Production: Add auth, rate limiting, and consider HIPAA/DPA; restrict CORS in Selene.

Resources

scripts/

• create_quantum_app.py — All-in-one: backend + deploy + frontend
• setup_selene_service.py — Scaffold Selene backend
• flyio_deploy.py — Deploy to Fly.io
• lovable_integrate.py — Frontend wired to backend URL

references/

• guppy_guide.md — Guppy syntax, gates, circuits, examples
• selene_api.md — Endpoints, request/response, errors, jobs
• flyio_config.md — Fly.io scaling, regions, secrets, monitoring
• lovable_patterns.md — Frontend patterns, dashboard, API client
• clinical-use-cases.md — Detailed clinical use-case mappings and compliance notes

assets/

• selene-template/ — Backend boilerplate (main.py, Dockerfile, fly.toml, .env.example)
• lovable-template/ — React/TS frontend with QuantumDashboard and API client

Advanced: Multi-Quantum Use Cases

• Optimization dashboard: Selene + QAOA/VQE; Lovable with sliders; Fly.io with scaling.
• Chemistry explorer: Guppy molecular simulations; 3D viewer; optional persistent storage.
• Quantum ML API: Selene exposing QNN/QSVM; Lovable for training/predictions; Fly.io (GPU if needed).

Performance, Cost, and Security

• Queuing: Use job queues for long-running quantum jobs; WebSockets or polling in frontend.
• Caching: Cache identical computations to reduce quantum hardware cost.
• Fly.io: Scale to zero when idle (min_machines_running = 0); use references/flyio_config.md for VM sizing.
• Security: No API keys in frontend; rate limiting on Selene; HTTPS in production; see references/selene_api.md for auth patterns.

Troubleshooting

• Guppy import error: pip install guppy in backend; or use mock mode for demos.
• Selene not starting: Check fly.toml, fly logs, and env vars.
• Frontend can’t connect: Verify VITE_API_URL, CORS in Selene, and curl .../health.
• Fly.io deploy fails: fly deploy --clean; fly logs --phase build; ensure fly auth login.
• Quantum results wrong: Validate circuit logic and measurement; test with emulator first.

Next Steps

After initial setup: monitor quantum usage/costs; add auth to Selene if public; improve error handling and logging; consider persistence for job history.

---

For detailed clinical use-case specs and compliance reminders, see references/clinical-use-cases.md.