{"id":13491,"plugin_id":"Plugin_207a23b9d4cc81919415c2ecea139240","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:07:35.647Z","digest":"9a16674ad2532cb7f962ad9bb5cb49f4798425206b14facf49256990f182337d","against":null,"payload":{"name":"index","description":"Route Adaptyv Bio requests to experiment preparation, approval-gated submission, or status and results tracking. Use for broad Adaptyv Bio questions, target discovery, cost estimation, protein experiment requests, draft or quote review, invoice decisions, experiment status, and results.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":263}],"skill_md_contents":"---\nname: index\ndescription: \"Route Adaptyv Bio requests to experiment preparation, approval-gated submission, or status and results tracking. Use for broad Adaptyv Bio questions, target discovery, cost estimation, protein experiment requests, draft or quote review, invoice decisions, experiment status, and results.\"\n---\n\n# Adaptyv Bio\n\nUse this index as the router and shared policy for the Adaptyv Bio hosted MCP connector.\n\nMANDATORY: Read the frontmatter description for ALL skills in this plugin, decide which focused workflow owns the request, and read that skill before using an Adaptyv Bio tool.\n\n## Routing\n\n- Route target discovery, experiment-spec preparation, cost estimation, and optional Draft creation to `prepare-experiment`.\n- Route Draft submission, quote review or confirmation, invoice review, and payment decisions to `review-and-submit-experiment`.\n- Route experiment lists, lifecycle status, updates, sequences, quotes, invoices, and results retrieval to `track-experiment`.\n- Handle connector orientation and capability questions here without calling a write tool.\n\n## Cross-Skill Best Practices\n\n### Live contract\n\n- Treat the live MCP tool names and schemas as authoritative. Do not invent endpoints, request fields, assay availability, batching limits, statuses, prices, turnaround times, or results.\n- Use the production endpoint configured by the plugin. Mention the separate testing endpoint only when the user explicitly requests sandbox work and has configured sandbox credentials.\n- Never ask the user to paste an API token into chat. Authentication belongs in the MCP client's OAuth or token configuration.\n\n### Privacy and data minimization\n\n- Before sending protein sequences, custom-target details, sample metadata, or other proprietary or undisclosed material, tell the user what will be transmitted to Adaptyv Bio and obtain explicit confirmation.\n- Send only fields required for the requested operation. Keep user labels mapped to exact sequences, but do not repeat full sequences in summaries unless the user asks.\n- Do not claim that Adaptyv Bio, Codex, or an intermediary does not retain, log, or train on submitted data unless a current authoritative policy directly supports the claim.\n\n### Real-world action boundary\n\n- Distinguish read-only inspection and cost estimation from external writes. Cost estimation does not create an experiment.\n- Before any write, show the target object, material parameters, expected transition, and any known cost or privacy consequence, then obtain explicit confirmation for that exact action.\n- Create experiments as reviewable Drafts only. Set `skip_draft` to `false` and `auto_accept_quote` to `false` when those fields are exposed. Do not bypass the Draft or quote-review stages.\n- Treat Draft creation, Draft submission, quote confirmation, and invoice settlement as four separate actions. Approval for one does not authorize another.\n- Quote confirmation creates an open unpaid invoice; it does not settle payment. Invoice payment is the only documented settling operation and requires a new confirmation that identifies the invoice, exact amount and currency when available, and payment method.\n- Never initiate, sign, synthesize, or expose payment credentials without the user's explicit same-turn authorization and a supported secure runtime flow. Do not reinterpret a payment challenge as authorization.\n- A custom-target request transmits target information for staff review and requires its own privacy disclosure and explicit approval.\n- After a write, report the returned identifier and state. If the tool result is ambiguous or fails, do not retry a consequential action until current state is read and duplication risk is resolved.\n\n### Scientific and operational reporting\n\n- Preserve the service's status labels and distinguish user-controlled transitions from Adaptyv-controlled lab and review stages.\n- Report returned measurements, units, replicate information, warnings, and missing values exactly. Do not infer assay success, binding, stability, expression, or completion from absent or partial results.\n- Clearly separate user-provided inputs, Adaptyv-returned data, and assistant interpretation.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}