Update to Adaptyv Bio

{
  "name": "review-and-submit-experiment",
  "description": "Review and execute one explicitly approved Adaptyv Bio experiment transition at a time: submit a Draft, confirm a quote to create an unpaid invoice, reject a quote, or settle an invoice. Use for experiment submission, quote decisions, invoice review, or payment requests.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 295
    }
  ],
  "skill_md_contents": "---\nname: review-and-submit-experiment\ndescription: \"Review and execute one explicitly approved Adaptyv Bio experiment transition at a time: submit a Draft, confirm a quote to create an unpaid invoice, reject a quote, or settle an invoice. Use for experiment submission, quote decisions, invoice review, or payment requests.\"\n---\n\n# Review and Submit an Adaptyv Bio Experiment\n\nMANDATORY: If not already in context, read and adhere closely to `plugins/adaptyv-bio/skills/index/SKILL.md#cross-skill-best-practices`.\n\nThis workflow owns consequential transitions. Inspect current state first and execute at most the exact step the user approves.\n\n## Review current state\n\n1. Read the experiment, latest updates, quote, and invoice metadata relevant to the request. Do not infer current state from an earlier message.\n2. Summarize the experiment identifier and status, assay and target, sequence labels and count, material parameters, quote or invoice identifier, amount and currency when available, and the next documented transition.\n3. Explain the effect of the proposed action:\n   - Submitting a Draft advances it for Adaptyv review and quote preparation.\n   - Confirming a quote creates or finalizes an open unpaid invoice and does not settle payment.\n   - Rejecting a quote cancels that quote and may return the experiment to Draft according to the live response.\n   - Paying an invoice is the settling operation and can move funds through the selected payment method.\n4. Ask for explicit confirmation naming the one action, target identifier, and known financial consequence. Do not accept a prior approval for a different transition.\n\n## Execute one approved transition\n\n- For Draft submission, call the documented submit tool only when the current state is Draft and the user has approved that experiment identifier.\n- For quote confirmation, call the documented confirmation tool only after showing the exact quote and amount when available. Stop after the unpaid invoice is returned.\n- For quote rejection, call the documented rejection tool only after the user approves the quote identifier and understands the resulting state change.\n- For invoice settlement, require same-turn confirmation of the invoice identifier, exact amount and currency when available, and payment method. Use only a supported secure runtime payment flow; never request credentials in chat or construct a credential outside that flow.\n\nAfter any write, report the returned identifier, state, amount, and next step. Do not chain the next transition. If a response is missing or ambiguous, read current state before considering any retry.\n\n## Boundaries\n\n- Do not combine Draft submission, quote confirmation, and invoice settlement into one approval or tool sequence.\n- Do not use `skip_draft`, automatic quote acceptance, or any action that bypasses human review.\n- Do not call a payment tool to discover its challenge or supported method unless the user has explicitly authorized attempting payment for that invoice.\n- Do not imply that quote confirmation paid an invoice.\n- Do not submit or pay from the testing environment as evidence that production authorization exists.\n"
}