risks — Claude Code skill: health risk forecasts and setup
This Claude Code skill estimates a person’s main health risks from their recorded state and evidence. It runs when PLSI requests the future part of a life trajectory or a user asks about their risks.
MIT ★ 93 updated 2026-11-15
npx skills add Insilico-org/plsi --skill risks -a claude-codeWhat risks does
The skill selects relevant events and diagnoses from personal history, family history, and current state, then assigns each a level and time window. For a numeric estimate, it looks for a risk equation, a matching base-rate table, or a verified cohort paper. If none fits, it gives a level with a hypothesis basis instead of a probability. No source means no probability.
For equation-based estimates and what-if inputs, it calls plsi calc derive rather than doing the arithmetic itself. It reads state, care context, due items, and plans through plsi commands; PLSI must provide a processor/history result or a request about risks. The output is one result containing events, evidence links, and the top modifiable risk. An adopted plan adds two trajectory courses.
What it helps with
- rank future health events from personal and family history
- estimate absolute risk using a relevant source
- distinguish a current check from a future event
- compare a forecast with an adopted plan
Example prompts for the agent
- Assess my main health risks from my current state and history.
- Build the future part of my life trajectory, with risk windows and sources.
- Compare the forecast with my adopted plan and show both trajectory courses.
How to install risks
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill risks -a claude-code2Manually: put the files in place
~/.claude/skills/risks/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/risks/
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill risks -a codex2Manually: put the files in place
.agents/skills/risks/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill risks -a cursor2Manually: put the files in place
.cursor/skills/risks/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Insilico-org/plsi skills/nostradamus/risks2Manually: put the files in place
.github/skills/risks/SKILL.md1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill risks -a gemini-cli2Platform CLI
gemini skills install https://github.com/Insilico-org/plsi --path skills/nostradamus/risksManually: put the files in place
.devin/skills/risks/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 risks
How do I install risks in Claude Code?
Run npx skills add Insilico-org/plsi --skill risks -a claude-code. The skill file is placed at ~/.claude/skills/risks/SKILL.md.
What does risks do?
It selects future events that matter to the person and estimates their risks using equations, base-rate tables, or verified cohort papers. Each event gets a time window and a source.
How does risks calculate probabilities?
It seeks a suitable risk equation, a base-rate table for a matching group, or a verified cohort paper. When no source fits, it reports a level without a numeric probability.
Source text
SKILL.md · MIT
---
name: risks
description: Use as PLSI Nostradamus when PLSI asks for the future part of the life arrow or for the user's main health risks - pick the 3-7 events that matter most, each with a window and a sourced absolute risk from risk equations, base-rate tables or cohort papers.
---
# PLSI risks
## When to use
- PLSI hands over PLSI Data Processor's `processor/history` result for the life arrow (`orchestrator/arrow`).
- The user asks "what are my main risks" or "what is likely ahead for me".
## Steps
1. **Read the state** cited in the request, the care and personal context, and what is already planned:
```bash
plsi state show --instance <instance> --map <map_id>
plsi state show --instance <instance> --map care_context
plsi due --instance <instance>
plsi plan list --instance <instance>
```
2. **Pick 3-7 events** from the user's own state, gaps, history (resolved conditions too: `plsi events list
--instance <instance> --kind condition`) and family history: the ones that are likely within
the window, or severe and modifiable. No fixed list. Each is an event or diagnosis that can be dated, not a
process ("harm building", "features building").
3. **Source each probability**, in this order; stop at the first that fits:
- a risk equation in a published state; if no map has it, put a `processor/add-score` request in your `result`;
- a `base_rate` table for the person's age, sex, country and period (`plsi refs list`), cited with its year;
- a verified cohort paper:
```bash
plsi refs list
plsi evidence search --source pubmed --query "<event> absolute risk <risk factors> cohort"
plsi evidence verify --kind pmid --id <pmid>
```
Reuse the evidence library and verify only what you cite (`shared/team`, Evidence speed).
- otherwise no number: a level only, `"basis": "hypothesis_only"`.
The source must match what is recorded: when symptoms or findings raise the risk (witnessed breathing pauses, a
raised marker), use a rate for people with those findings, never the general-population rate.
Risk from an equation or with what-if inputs comes from `plsi calc derive`, never by hand.
4. **Level** each event: `high` (likely within the window, or severe and modifiable), `watch` (raised vs the matching
group), `info`. Add scheduled re-measurements and recorded plan predictions (step 1) as `info` events.
5. **Return ONE `result`**: per event the window, label, level, probability (or none), basis and link; the top
modifiable risk named first. With an adopted plan, add `nostradamus/trajectory`'s two courses.
## Rules
- No probability without a source; relative risks are turned into absolute ones only against a cited base rate.
- Name no intervention as a cure; changes of course come only from plans that passed `plsi screen`.
- Rank by what matters to this person, not by how alarming an event sounds.
- A condition whose signs are present now (snoring with witnessed pauses and daytime sleepiness) is a "check now"
item, not a future event.
- A care step (a visit, a test) carries a time frame from a cited guideline; never a later one.
© Insilico-org · MIT · Insilico-org/plsi