Skill
Target prioritization matrix
A general, interview-driven target-discovery workbench: name the biology and the modality you care about, and get back a scored table of candidate targets — druggability, essentiality, genetic constraint, curated safety, and the real number of drugs already targeting each — assembled from GeneCore intelligence and DrugCore/TrialCore/BiomedCore/PatentCore cross-links.
New to Amass? Connect Amass to Claude first
The prompt
Paste this into Claude
oncology — essential druggable protein kinases; modality: small molecule (flag PROTAC); score on essentiality, constraint, safety, competitionUse the Target prioritization matrix skill.
Seed / scope: oncology — essential, druggable protein kinases (cell-cycle & mitotic checkpoint)
Modality: small molecule (also flag PROTAC tractability)
Criteria: target class · small-molecule tractability · essentiality · genetic constraint (LOEUF) ·
curated safety liabilities · competition (# drugs targeting) · clinical/literature/IP activity scan
Stance: show the full field, most-essential first, so I can weigh validation vs therapeutic-window risk
Shortlist size: 12
Output format: markdown table + CSVWhy not just ask the model?
Ask a plain model to "shortlist druggable, essential kinase targets for oncology and score them by essentiality, safety and competition" and it names a handful of famous kinases and invents the numbers — gene-effect scores, LOEUF values, "drugs in development" counts — that read authoritative and are fabricated.
- Plain model: a few remembered kinases; made-up essentiality, constraint, safety, and competition figures.
- Amass: the real GeneCore records for the live filtered search — every gene-effect score (PLK1 −2.73, WEE1 −2.48, CDK1 −2.34…), every gnomAD LOEUF, every curated safety liability (AURKA: mutagenic / cardiac / neutropenia), and the real
referencesDrugCoreedge count per target (AURKA 19 → WEE1/TTK 2), verbatim from the returned fields.
Why a skill, not a prompt?
Because the value is the interview and the orchestration, not one question. The skill asks modality first, then which criteria to score, then the output format — and turns those answers into GeneCore enum filters (targetClass=ENZYME, isEssential=true, isDruggable=true, tractabilityModality). It unions two query angles to broaden past a single relevance ranking (10 + 10 at the default limit, overlap 4 → 16 unique), reads the target-intelligence fields straight from the search response, then fans out one get_amass_genecore_record per candidate for the referencesDrugCore competition edge and one TrialCore / BiomedCore / PatentCore search each for the activity scan. Then — because it is a general workbench — it offers to freeze this exact configuration into a dedicated, one-line reusable skill, so the workbench spawns the narrow, repeatable tool.
Honest scope
Candidates are a union of relevance-ranked top-10 GeneCore searches — a broadened sample, not a census. Target-intelligence fields are verbatim from the upstream reference databases as harmonized in GeneCore; null = "no data recorded," not zero. drugs_targeting is the length of each gene's referencesDrugCore edge — 0 would mean unprecedented, not undruggable. The TrialCore / BiomedCore / PatentCore columns are capped ≤10 samples: on this mature class all 12 kinases saturate at 10+, so those columns don't differentiate — the discriminating competition signal is the DrugCore edge, and the skill says so rather than presenting three dead columns as a ranking. And essentiality is double-edged — a pan-essential kinase is a strong dependency and a narrow-therapeutic-window risk.
Install the skill
Add the skill to Claude
Install every Amass skill with one command, npx skills add amass-technologies/public-skills or download the SKILL.md from GitHub and add it to Claude (Settings → Capabilities → Skills, or drop it in your Claude Code skills directory). Then paste the prompt above to trigger it.
More from the library
Keep exploring
| Short name | Source id | Registry | Copy of |
|---|---|---|---|
| Acute, 50/75 mg vs placebo | NCT04072354 | ClinicalTrials.gov | |
| ↳ EUCTR2019-000470-36-BG | EU CTR | NCT04072354 | |
| Acute, 75/100 mg vs placebo | NCT04092686 | ClinicalTrials.gov |
Watchlist Monitor
Name the trials, papers, approvals or drugs you need to follow; get one Excel board that re-reads them through Amass at every check and tells you exactly what changed: status, dates, enrollment, results posted, label revisions, retractions, new links.

Landscape Monitor
Name a field; get it mapped across trials, papers, patents, drugs, genes and approvals into a landscape page with charts, a workbook and a one-page briefing, every record screened with its reason. Ask for an update later to see what is new and what changed.
| record_type | title | id | source |
|---|---|---|---|
| paper | Mechanisms of Resistance to KRASG12C Inhibitors | PMID:33466360 | Cancers (JuFo 2) |
| paper | Oncogenic KRAS blockade therapy: renewed enthusiasm and persistent challenges | PMID:34607583 | Molecular Cancer (JuFo 3) |
| paper | KRAS G12C Mutations in NSCLC: From Target to Resistance | PMID:34064232 | Cancers (JuFo 2) |
Biomedical Evidence Scout
Name a drug, target, mechanism, or indication; get a landscape briefing that maps the published literature AND the clinical pipeline together — every paper and trial carrying a real Amass ID, PMID, or NCT you can check.
Run it yourself
Connect Amass to Claude and paste the prompt.
The connector takes about a minute to add, then this workflow runs on your own inputs.
- Data
- No training on your data
- Hosting
- EU-hosted, enterprise
- Isolation
- Tenant-isolated by architecture
- Certification
- ISO 27001, SOC 2, NIS2: in motion