Agent skill · Databases

TTD

Query the Therapeutic Target Database (TTD) for drug-target-disease interaction data. Use this skill when the user asks about therapeutic targets, drugs, diseases, or their relationships — including target-drug mappings, clinical status of drugs, disease indications, UniProt/gene associations, and pathway annotations. Triggers on queries like "what drugs target EGFR", "which diseases is Imatinib used for", "find targets for lung cancer", or any lookup involving TTD IDs, gene symbols, drug names, or disease names.

BioTender-maxgithub.com/BioTender-maxGitHub ↗
claude-codeships scriptsNOASSERTION
Install
npx skills add BioTender-max/awesome-bio-agent-skills --skill ttd --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 6
SKILL.md size: 5 KB
Bundled scripts: yes
Path: skills/drugclaw/ttd/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 135
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# TTD — Therapeutic Target Database **Source:** https://ttd.idrblab.cn/ **Paper:** https://academic.oup.com/nar/article/52/D1/D1465/7275004 **Data dir:** `resources_metadata/dti/TTD` ## Data files (4 required) | File | Content | |------|---------| | `P1-01-TTD_target_download.txt` | Target info: name, UniProt, gene, type, function, disease indication, pathway | | `P2-01-TTD_target_drug.txt` | Target ↔ Drug links with clinical status (Approved / Phase I–III / Experimental) | | `P1-06-Target_disease.txt` | Target ↔ Disease associations | | `P1-07-Drug_disease.txt` | Drug ↔ Disease associations | **File formats:** - `P1-01`, `P2-01` — block format: blank-line separated records, each line `<ID>\t<KEY>\t<VALUE>` - `P1-06`, `P1-07` — TSV with header row --- ## Query API ### `query(entities, entity_type="auto", data_dir=DATA_DIR)` Returns a **list of dicts**, one per queried entity. | Parameter | Type | Description | |-----------|------|-------------| | `entities` | `str` or `list[str]` | One or more entity names / IDs | | `entity_type` | `"auto"` / `"target"` / `"drug"` / `"disease"` | Restrict search; `"auto"` tries target → drug → disease | | `data_dir` | `str` | Path to TTD data direc

What's inside
Steps it walks through
  1. Data files (4 required)
  2. Query API
  3. query(entities, entitytype="auto", datadir=DATADIR)
  4. queryjson(entities, ...) → str
  5. Input formats accepted
  6. Output structure
  7. Target result
  8. Drug result
  9. Disease result
  10. Not found
  11. Usage examples
  12. Notes
Ships with 5 files
  • README.md
  • __init__.py
  • example.py
  • retrieve.py
  • ttd_skill.py
Commands it runs
python 17_TTD.py EGFR Imatinib "Lung cancer"
python 17_TTD.py TTDTARGET00001
More from awesome-bio-agent-skills
All skills →
About this skill
What does the TTD skill do?

Query the Therapeutic Target Database (TTD) for drug-target-disease interaction data. Use this skill when the user asks about therapeutic targets, drugs, diseases, or their relationships — including target-drug mappings, clinical status of drugs, disease indications, UniProt/gene associations, and pathway annotations. Triggers on queries like "what drugs target EGFR", "which diseases is Imatinib used for", "find targets for lung cancer", or any lookup involving TTD IDs, gene symbols, drug names, or disease names.

How do I install it?

Run `npx skills add BioTender-max/awesome-bio-agent-skills --skill ttd --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From BioTender-max/awesome-bio-agent-skills, a repository with 135 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going