Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lingxling/tamarind
Access a collection of open-source molecular design and structural biology tools on the Tamarind Bio platform, via its REST API or MCP server — no local GPUs required. Tamarind bundles popular open-source models for structure prediction (AlphaFold, Boltz, Chai, ESMFold), protein, binder, and de novo design (RFdiffusion, ProteinMPNN, BoltzGen), antibody and nanobody design and developability, protein-ligand docking (DiffDock, Autodock Vina), binding-affinity prediction, MSA generation, and molecu
Passed 24 of 25 test cases with the skill, and 9 of 25 without it.
and 24 more in the full report
15 fixed9 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
I uploaded a ligand structure file `ligand.sdf` to Tamarind Bio. I want to construct a DiffDock submission payload referencing this file. Should my settings dictionary use `[email protected]/ligand.sdf` or `ligand.sdf`?
| Checked | Without skill | With skill |
|---|---|---|
| Sets file parameter values using bare filenames. | Missed | Passed |
| Omits email prefixes from file parameter strings. | Missed | Passed |
The instructions your model reads when the skill loads.
Tamarind Bio is a cloud platform that runs computational biology tools — structure prediction, protein and antibody design, docking, binding-affinity, MSA generation, and molecular dynamics — on managed GPUs. Users submit sequences or structures and get back predicted structures, designs, and biophysical scores, without provisioning their own hardware. It exposes hundreds of tools (AlphaFold, Boltz-2, Chai-1, RFdiffusion, ProteinMPNN, BoltzGen, ESMFold2, DiffDock, Autodock Vina, and many more) through one uniform job API.
Official docs: app.tamarind.bio/api-docs · platform UI at app.tamarind.bio
Tamarind publishes live, machine-readable sources. Prefer fetching them at runtime over trusting any hardcoded list — tool names, schemas, and endpoints change frequently:
https://app.tamarind.bio/llms.txt — LLM index: links to the spec, API docs, and MCP guide.https://app.tamarind.bio/openapi.yaml — OpenAPI 3.0 spec for the 8 core job endpoints (submit-job/-batch, jobs, result, upload, files, delete-job/-file; auth ApiKeyAuth). Fetch it for those exact shapes. Discovery/management endpoints (/tools, /usage-statistics, pipelines, …) aren't in it — use the MCP/REST discovery tools for those.https://docs.tamarind.bio/llms.txt — documentation index; every page has a .md form (e.g. docs.tamarind.bio/tamarind/batch.md, /tamarind/api.md, /tamarind/pipelines.md).GET /tools (REST) or MCP getAvailableTools + getJobSchema(jobType) are the source of truth for what tools exist and their parameters.This skill teaches the surface + the non-obvious behaviors those sources don't spell out (see the reference files). When in doubt about a shape, fetch openapi.yaml.
Use Tamarind when the user wants to:
This skill is the right fit when the work should run on Tamarind's managed cloud rather than on a local install. For purely local cheminformatics or one-off sequence I/O, use a local library (RDKit, BioPython) instead.
x-api-key header.TAMARIND_API_KEY environment variable or a .env file (use python-dotenv). Never commit keys to source control.Pricing: Every user gets 10 free jobs. For larger usage, contact [email protected] to purchase a subscription.
test cases passed, vs 9 / 25 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.