← Tamarind BioCONTENT HISTORY

Update to Tamarind Bio

Snapshot Oct 27, 2026 · 00:11 UTC · version 2.0.1

Collection source: downloaded plugin package. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.

WHAT CHANGED

Supporting file metadata differs

Supporting file metadata differs

Observed in package metadata. These changes alone do not establish a new customer-facing feature.

Save Tamarind Bio and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Supporting files

Before

Sep 30, 2026 · 22:50 UTC

[]

After

Oct 27, 2026 · 00:11 UTC

[{"relative_path":"agents/openai.yaml","size_in_bytes":435}]

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

No SKILL.md text changes between these observations.

Full technical diff · 1 changed fields

changed /included_files

BEFORE
[]
AFTER
[
  {
    "relative_path": "agents/openai.yaml",
    "size_in_bytes": 435
  }
]
Full snapshot data
{
  "description": "Design, redesign, model, number, humanize, or search antibodies, nanobodies, VHHs, and TCRs with Tamarind Bio through MCP. Use for CDR-aware and repertoire-specific workflows when MCP is requested. Not for generic non-antibody binder design, ordinary complex folding, or developability scoring alone.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 435
    }
  ],
  "name": "tamarind-mcp-antibody",
  "skill_md_contents": "---\nname: tamarind-mcp-antibody\ndescription: Design, redesign, model, number, humanize, or search antibodies, nanobodies, VHHs, and TCRs with Tamarind Bio through MCP. Use for CDR-aware and repertoire-specific workflows when MCP is requested. Not for generic non-antibody binder design, ordinary complex folding, or developability scoring alone.\n---\n\n# Engineer antibodies through MCP\n\nClarify antibody versus VHH/nanobody/TCR and the goal: de novo CDR design, redesign, structure prediction, numbering, humanization, or repertoire/paratope search.\n\n## Select and inspect\n\nCall `getAvailableTools(modality=\"antibody\")`. Narrow with a live function such as antibody design or structure prediction, then call `getJobSchema` for the strongest fit.\n\nPrefer antibody-specific tools when chain pairing, CDR regions, framework numbering, epitope/hotspot steering, or humanization matters. Route generic co-folding to `tamarind-mcp-structure-prediction` and non-antibody binders to `tamarind-mcp-binder-design`.\n\n## Build and validate\n\nCapture the heavy/light or VHH sequence, framework, antigen structure and chain, epitope or hotspots, CDR regions and lengths, candidate count, and excluded residues required by the live schema. Upload structures with `uploadFile` and use the returned filename or an accepted prior-job `s3Path`.\n\nCall `validateJob`, require no mutation warning, and call `estimateTime`. Confirm chain identities, numbering scheme, CDR scope, candidate count, refolding plan, filters, and estimated spend before submission.\n\n## Execute and filter\n\nUse `tamarind-mcp-submit-and-poll`. For multiple independent candidates, use `tamarind-mcp-batch` rather than repeated `submitJob` calls.\n\nRank design outputs on interface confidence and geometry, then apply antibody-specific developability filters through `tamarind-mcp-developability`. Preserve sequence diversity and flag liabilities instead of selecting only the top scalar score. Predictions prioritize experiments; they do not replace binding and developability assays.\n"
}

SHA-256 of public snapshot: b6088706bbf6a77f0b8b14b2acfa136f253372dd9edbb937d5db587cf51d3251