Skip to main content
skill CX Codex

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

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Insilico-org/plsi --skill assess -a claude-code
Open on GitHub

What 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-code

2Manually: put the files in place

~/.claude/skills/assess/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/assess/

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.

assess OrchestKit The assess skill rates code or design decisions 0-10 across seven dimensions: correctness, readability, complexity, performance, security, maintainability and compliance. CX Codex +1 211installs assess-react-native-migration callstackincubator assess-react-native-migration audits product repositories and decides whether a mobile app should move to React Native, before anyone writes migration code. CX Codex +1 2,700installs llm-risk-assess OWASP llm-risk-assess assesses LLM applications against OWASP Top 10 for LLM Applications 2025. Built for teams embedding models in chatbots, RAG pipelines, or AI agents. CX Codex +1 186installs acreadiness-assess official github acreadiness-assess runs an AgentRC AI-readiness scan on your repository and generates a standalone HTML report at reports/index.html. Handy before configuring AI agent instructions. CX Codex +1 158installs agentic-ai-risk-assess OWASP agentic-ai-risk-assess evaluates autonomous agents and multi-agent workflows against the OWASP Top 10 for Agentic Applications 2026 framework. CX Codex +1 156installs experience-lwc-widget-assess forcedotcom experience-lwc-widget-assess is a Claude Code skill that assesses whether a Lightning web component can be represented as an HXL declarative widget. CX Codex +1 129installs assess-patch-risk official OpenAI assess-patch-risk is a Codex skill that traces a patch’s program impact, regression risk, and eligibility for automatic merging. It runs on supplied patch files, provider pull-request comparisons, or commit ranges. CX Codex GP ChatGPT +1 ★ 8,052repo stars

From the same set85

The whole set →
nudge The nudge Claude Code skill manages reminders between plan check-ins. It schedules messages about follow-up visits, measurement windows and the first days of a plan. CX Codex +1 ★ 93repo stars add-score add-score — a Claude Code skill that adds a new derived measure to a PLSI map. It activates when a request needs a score or equation the existing maps do not compute. CX Codex +1 ★ 93repo stars forget The forget Claude Code skill removes PLSI records tied to one person. It runs when PLSI relays a request to erase the user’s data or that of someone they added. CX Codex +1 ★ 93repo stars mothership This Claude Code skill checks Mothership access and reads its public catalog and findings ledger. It prepares research notes or registry contributions for review by the Data Controller. CX Codex +1 ★ 93repo stars apple-health This Claude Code skill connects Apple Health and sends metrics to PLSI. It activates for connection requests or imports covering a requested date range. CX Codex +1 ★ 93repo stars run This Claude Code skill preregisters a research hypothesis, runs its analysis, and prepares a finding. It starts after a researcher selects a hypothesis and PLSI relays the registration receipt and Challenger objections. CX Codex +1 ★ 93repo stars sleep This Claude Code skill reads sleep data and builds a plan around the user's request. It activates for requests to improve sleep or interpret sleep measurements. CX Codex +1 ★ 93repo stars ask This Claude Code skill turns a research direction into a question that search can settle, or breaks it into child questions. It activates when plsi research next selects ask. CX Codex +1 ★ 93repo stars

Project sponsors

Companies that keep this analytics open