kdense-ginkgo-cloud-lab

name

kdense-ginkgo-cloud-lab

description

Submit and manage protocols on Ginkgo Bioworks Cloud Lab (cloud.ginkgo.bio), a web-based interface for autonomous lab execution on Reconfigurable Automation Carts (RACs). Use when the user wants to run protein expression and purification (cell-free, E. coli, or Pichia), HiBiT or A280 or LabChip quantification, IVT mRNA/circRNA synthesis, thermal shift / developability assays, Echo-MS enzyme or analyte methods, SPR target onboarding, fluorescent pixel art, or otherwise interact with Ginkgo Cloud Lab services. Covers protocol selection, input preparation, pricing, and ordering workflows.

Kdense Ginkgo Cloud Lab

Use this Codex adapter for the pinned upstream scientific skill.

Catalog status

• Status: active
• Source: kdense
• Audit reasons: none
• Upstream license: MIT license
• Inventory: ../../inventory.json
• Upstream instructions: ../../../vendor/scientific-agent-skills/skills/ginkgo-cloud-lab/SKILL.md

Procedure

1. Resolve the plugin root as three directories above this skill directory.
2. Read the matching inventory record and verify its status, reasons, source path, and pinned revision.
3. Read the upstream instructions only after confirming this record is still active in the current inventory.
4. Treat upstream frontmatter as source metadata, not as Codex configuration. Follow the instruction body only where it is compatible with available Codex tools and the current user-approved plan.
5. Treat tools named for another agent runtime as capability requests. Map them to an available Codex tool only when the behavior is equivalent; otherwise report the unavailable capability.
6. Ask before credentials, package installation, new network hosts, remote compute, writes, paid services, destructive actions, or imported executable code.
7. Use $science-provenance for produced scientific outputs and $science-review before presenting scientific claims.

Physical-experiment and remote-lab safety (mandatory)

This skill can drive real laboratory hardware or submit paid remote-lab work. Beyond the general gates, before any physical or remote action:

• Get explicit user approval to operate real devices or submit an order; never actuate hardware or send a job on your own initiative.
• Simulate or dry-run first and show the user the exact planned steps.
• Confirm samples, reagents, and the biosafety/containment level; refuse out-of-scope, hazardous, or dual-use protocols.
• Verify instrument state and the emergency-stop/abort path before starting, and stop immediately on any anomaly.
• For cloud/remote labs, surface the cost and get billing approval before submitting.

Boundaries

• This wrapper does not grant credentials, network access, package installation, or script execution.
• Do not change an inactive record to active from inside a research task.
• Preserve failures, uncertainty, source identifiers, and licensing constraints.