name	tamarind-bio
description	Use TamarindBioAgent for Tamarind Bio-style cloud protein and molecular workflows workflows, source provenance, and guarded API/tool access.
license	Apache-2.0
user-invocable	true

TamarindBioAgent

Use this skill when work needs Tamarind Bio-style cloud protein and molecular workflows rather than prompt-only reasoning.

Call get_tamarindbioagent_status to confirm configured environment variables, targets, and Apache-2.0 license metadata.
Call list_tamarindbioagent_api_targets before using any API target name.
Prefer read-only GET, HEAD, or OPTIONS API calls. For mutation-capable methods, require explicit user approval and pass allow_mutation=true.
Preserve returned identifiers, URLs, timestamps, accessions, DOIs, job IDs, or status fields in the final answer.
Use summarize_tamarindbioagent_resource for exported JSON payloads before drawing conclusions.
Do not run local commands unless the user approves the exact command and allow_execute=true is supplied.

Treat credentials as secrets; never print API keys or tokens.
Distinguish API-reported facts from inference.
Keep wet-lab, clinical, regulatory, and compute-impacting actions as plans until the user explicitly approves them.
When an API result is incomplete or unauthenticated, say so clearly.

name	tamarind-bio
description	Use TamarindBioAgent for Tamarind Bio-style cloud protein and molecular workflows workflows, source provenance, and guarded API/tool access.
license	Apache-2.0
user-invocable	true

Use this skill when work needs Tamarind Bio-style cloud protein and molecular workflows rather than prompt-only reasoning.

Call get_tamarindbioagent_status to confirm configured environment variables, targets, and Apache-2.0 license metadata.
Call list_tamarindbioagent_api_targets before using any API target name.
Prefer read-only GET, HEAD, or OPTIONS API calls. For mutation-capable methods, require explicit user approval and pass allow_mutation=true.
Preserve returned identifiers, URLs, timestamps, accessions, DOIs, job IDs, or status fields in the final answer.
Use summarize_tamarindbioagent_resource for exported JSON payloads before drawing conclusions.
Do not run local commands unless the user approves the exact command and allow_execute=true is supplied.

Treat credentials as secrets; never print API keys or tokens.
Distinguish API-reported facts from inference.
Keep wet-lab, clinical, regulatory, and compute-impacting actions as plans until the user explicitly approves them.
When an API result is incomplete or unauthenticated, say so clearly.

tamarind-bio