hallmarks — Claude Code skill: aging analysis and setup
This Claude Code skill maps a gene, pathway, or candidate to aging hallmarks and supporting evidence. It activates for requests to assess those links and possible biomarkers.
MIT ★ 93 updated 2026-11-15
npx skills add Insilico-org/plsi --skill hallmarks -a claude-codeWhat hallmarks does
The skill relates a gene or candidate to the twelve aging hallmarks in López-Otín et al. 2023. It starts with curated Open Genes records, searches PubMed and Europe PMC, then identifies biomarkers or aging clocks that could test each proposed link.
Each link gets an evidence class and model system. Animal and cell findings remain Low, while a curated mechanism label alone cannot establish a hallmark connection. The analysis also names a result that would weaken the link and flags when a biomarker change alone does not show that a person is better off. It needs the plsi commands and Open Genes data; dataset references require a separate web search.
What it helps with
- map a gene to aging hallmarks
- separate human evidence from animal findings
- grade a link by its weakest evidence
- identify biomarkers and a result that could falsify a link
Example prompts for the agent
- Map
TP53to the aging hallmarks and grade the evidence for each link. - Frame this candidate for a grant using aging hallmarks and possible biomarkers.
- Assess this mechanism against aging hallmarks and name evidence that could disprove the link.
How to install hallmarks
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill hallmarks -a claude-code2Manually: put the files in place
~/.claude/skills/hallmarks/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/hallmarks/
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill hallmarks -a codex2Manually: put the files in place
.agents/skills/hallmarks/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill hallmarks -a cursor2Manually: put the files in place
.cursor/skills/hallmarks/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Insilico-org/plsi skills/targets/hallmarks2Manually: put the files in place
.github/skills/hallmarks/SKILL.md1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill hallmarks -a gemini-cli2Platform CLI
gemini skills install https://github.com/Insilico-org/plsi --path skills/targets/hallmarksManually: put the files in place
.devin/skills/hallmarks/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about hallmarks
How do I install hallmarks in Claude Code?
Run npx skills add Insilico-org/plsi --skill hallmarks -a claude-code. The skill file is placed at ~/.claude/skills/hallmarks/SKILL.md.
What does hallmarks do?
It connects a gene, pathway, or candidate to aging hallmarks, grades the evidence, and suggests biomarkers or aging clocks for testing the links.
What does hallmarks need to work?
It needs the plsi commands and curated Open Genes data. Literature searches use PubMed and Europe PMC; dataset references are checked through a separate web search.
Source text
SKILL.md · MIT
---
name: hallmarks
description: Use as PLSI Target Hunter when the researcher wants a target, pathway or candidate framed against the hallmarks of aging - which hallmarks it touches, on what evidence, and which aging clocks or biomarkers could show an effect.
---
# PLSI hallmark framing
The framing is easily overstated, so the shape of the evidence matters more than the amount.
## When to use
- "Which hallmarks does <target> act on?", "frame this candidate for a grant", a candidate from `targets/discover`
or a mechanism from `targets/evaluate`.
## Steps
1. **Start from the curated record.**
```bash
plsi targets dossier --gene <SYMBOL> # `aging` is Open Genes' curation, with identifiers
plsi targets brief --gene <SYMBOL> # the same evidence, split human and animal
```
The aging block gives a confidence level, the aging mechanisms the curators assigned, why the gene was curated,
and the studies: lifespan experiments (animal) and longevity associations (human genetics), kept apart.
`curated: false` means Open Genes does not cover the gene; the literature search starts there.
2. **Read the computed frame.**
```bash
plsi targets hallmarks --gene <SYMBOL> # from the dossier on disk; contacts nothing
```
One row per hallmark of the twelve in López-Otín et al. 2023 (PMID 36599349; say so, since the earlier list has
nine), each marked `touched` or not and naming the Open Genes mechanisms it rests on.
- **`silence`** on an untouched row says which absence it is: no mechanism vocabulary for that hallmark in the
source, nothing filed by the curators, or a gene the source does not cover.
- **`unmapped_mechanisms`** are curated mechanisms the mapping does not place; name them and map them in prose.
- **`touched_count`** is breadth of curation, not a score; never rank by it.
- The mapping is PLSI's reading of Open Genes' words. Where you disagree with a row, say so and why.
- Compare `counts` with `shown` (the lists are sampled; say `n of N`) and check `perturbed` on every animal row
(an experiment that changed another gene is not evidence about this one).
Then widen with the literature:
```bash
plsi evidence search --source pubmed --query "<target> <hallmark>" --limit 20
plsi evidence search --source europepmc --query "EXT_ID:<pmid>" --limit 1 # the abstract for one paper
plsi evidence verify --kind <pmid|doi> --id <id>
plsi refs list --kind dataset
```
`pubmed` ranks by relevance without abstracts; `europepmc` gives abstracts ranked by date. The `dataset`
references are bookmarks, not queryable sources: open them with your own web search and say which you checked
by hand and which you could not.
3. **Grade each link by its weakest cited step**, naming the model system:
| Evidence under the link | Class |
|---|---|
| human genetic association or a human trial | may reach `evidence_backed` |
| animal lifespan or phenotype work | Low; `species: animal` wherever it is written |
| cell or in-vitro work | Low |
| pathway membership or a curated mechanism label alone | `hypothesis_only` |
A curated mechanism label carries no study; a link resting only on one is `hypothesis_only` until you find the
paper. A label that restates what the protein is says nothing about aging.
4. **Readouts.** For each mapped hallmark, the human biomarkers or aging clocks that could show an effect, where they
come from and what change would refute the link. A link with no readout is a label.
```bash
plsi clocks list
```
Say whether improving the readout alone is known to mean the person is better off; an untied surrogate is a
limit.
5. **Return one `result`** with `<PLSI_HOME>/work/<thread>/hallmarks_<gene>_<YYYYMMDD>.md` (the `thread` from the
request, or `<gene>-hallmarks`, saying which you used): a table of hallmark, link, direction, evidence class,
model system, identifiers, readout and falsifier, then one paragraph on which links are strongest and which are
labels. Name the `target_<gene>.json` from `plsi targets show` in `files` when one was written.
## Rules
- **No hallmark link is stronger than its weakest cited step.** Animal and cell data stay Low.
- **A curated mechanism label is not a hallmark**, and the mapping between them is stated.
- **An absence in Open Genes is an absence in Open Genes.** Name the silent source.
- **A human readout on an animal-evidence row says so**: put the species in the readout cell too.
- Nothing here is advice for a person's plan, and no personal data goes into it.
© Insilico-org · MIT · Insilico-org/plsi