assess · insilico-org — Claude Code skill for health data assessment
A skill for Claude Code assesses health data through PLSI maps. It runs after new data arrives or when asked about biological age, risk markers, or trends.
MIT ★ 93 updated 2026-11-15
npx skills add Insilico-org/plsi --skill assess -a claude-codeWhat assess does
The skill selects PLSI maps for a question, reads their states, and projects maps that do not have a current state. It sends PLSI values with units, dates, and statuses, changes since the last projection, and measurement gaps. PLSI decides what the user sees; PLSI Visualizer draws the charts.
The skill does not project a map marked current, since doing so would erase its changes. It reports each map’s inference boundaries when interpreting results. If no installed map covers a needed quantity, it sends a request to add one. User maps are checked with plsi maps validate, then installed and projected with PLSI commands.
What it helps with
- assess biological age from a map’s data
- compare marker changes with the previous projection
- find measurement gaps for a health question
- request a map for a quantity no installed map covers
Example prompts for the agent
- Assess my state and trends using the new PLSI data.
- Show changes since the last projection and any measurement gaps.
- Add this coordinate to a user map and validate it.
How to install assess
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill assess -a claude-code2Manually: put the files in place
~/.claude/skills/assess/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/assess/
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill assess -a codex2Manually: put the files in place
.agents/skills/assess/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill assess -a cursor2Manually: put the files in place
.cursor/skills/assess/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Insilico-org/plsi skills/consultant/assess2Manually: put the files in place
.github/skills/assess/SKILL.md1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill assess -a gemini-cli2Platform CLI
gemini skills install https://github.com/Insilico-org/plsi --path skills/consultant/assessManually: put the files in place
.devin/skills/assess/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 assess
How do I install assess in Claude Code?
Run npx skills add Insilico-org/plsi --skill assess -a claude-code. The skill file is installed at ~/.claude/skills/assess/SKILL.md.
What does assess do?
It chooses PLSI maps, evaluates their states, and sends PLSI values, changes, and measurement gaps. It does not create a report for the user.
What does assess need to work?
The skill uses PLSI and its plsi commands to read states, create projections, and work with maps. Map selection and projections use the --instance parameter.
Source text
SKILL.md · MIT
---
name: assess
description: Use as PLSI Health Consultant when PLSI asks where the user stands (biological age, risk markers, trends), after new data was ingested, or when PLSI hands it an extension coordinate to add to a user map.
---
# PLSI assess
## When to use
- After PLSI Data Processor recorded new observations (`processor/intake`, `processor/history`); PLSI hands over the
new `states`.
- The user asks about their state, clocks, trends or what to measure next.
- Before `nostradamus/plan` (plans are gated on a fresh projection).
## Steps
1. Select maps. Read each map's coverage (`present`, `missing`, `ratio`, `tags`) and choose one or more for the user's question; say in one line why, and which maps you rejected. After new `lifestyle` observations (or when the question is about alcohol, smoking, vaping, shift work or abstinence), include `lifestyle_context`.
```bash
plsi maps select --instance <instance>
plsi maps show blood_phenoage
plsi clocks list
```
2. Read each chosen map that arrived in the request's `states` with `plsi state show`; when `current` is true, do not
re-project it (that would erase its changes) and take Changed and Gaps from Data Processor's storyline in the
request `summary`. Project only the chosen maps with no state or `current` false. Projecting writes
`states/<map>/latest.json`, the saved state every plan refers to.
```bash
plsi state show --instance <instance> --map blood_phenoage
plsi project --instance <instance> --map blood_phenoage
```
3. Read `data.storyline` of each map you projected: clock accelerations, change vs the previous projection per coordinate, and gaps. Report values with units, dates and status (`present`, `stale`, `missing`, `error`).
4. When no installed map has a quantity you need, put a `processor/add-map` request in your `result` (the quantity, its unit, why); see `shared/team` Map gaps. When PLSI hands you an extension coordinate (`engineer/extend`), add it to a user map `user_<topic>.yaml` (schema `contracts/MapContract.schema.json`; copy the structure of `plsi maps show <id>`). Use `id: user_<topic>`, `claim_level: designed`, LOINC codes in `accepts.codes` (`reject_codes` for look-alikes) and a `source` on every conversion.
```bash
plsi maps validate user_topic.yaml --live
plsi maps install --instance <instance> --file user_topic.yaml
plsi project --instance <instance> --map user_topic
```
5. Send ONE `result` to PLSI; `states` lists every projected map with its `state_hash`, and `summary` holds, compactly:
- **Maps:** chosen and rejected, one line why.
- **Now:** the key values with units, dates and status; clock accelerations; what the map does not support.
- **Changed:** each coordinate that moved since the previous projection (old -> new, dates), or "first projection".
- **Gaps:** each as a measurement request from the gap's `suggestion`: test name, why it matters for this map or
question, where (at home: wearable, cuff, scale, finger-prick kit; or a lab or clinic draw, fasting if needed),
and which coordinate it fills. Most useful first, at most 5.
- **Red flags:** a `red_flag:` line (`orchestrator/urgent`) for any coordinate the lab flagged critical or beyond a
critical limit from a verified source (`plsi evidence verify`); `uncertain` when no source exists. Do not
interpret it further. Very low weight-for-height goes as a `scope:` line instead.
PLSI decides what the user sees and PLSI Visualizer draws the charts; you never render a report or message the user.
## Rules
- Values come only from `project` or `state show`; never compute or estimate a coordinate yourself.
- Never re-project a `current` state (step 2); a stale `latest.json` blocks plans.
- Fix every violation `maps validate` returns before installing; never edit shipped maps.
- State the map's `inference_boundaries` when interpreting: say what the map does not support.
- `lifestyle_context` holds only **active** lifestyle items (not stopped/resolved, not ended). Past periods remain
in the event log; never invent abstinence when the user did not state it. When reading `active_lifestyle`, treat
`dose` as quantity/frequency/regularity on a stable habit `text` — not a second identity. A stop must use the same
habit text the active row used (`processor/intake`, Lifestyle).
© Insilico-org · MIT · Insilico-org/plsi
Similar skills
SKILL.md skills catalog →assess by other authors comes first.