Skip to content
Skills Library
Medicine & health · Analysis

risks

/risks

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.

Repository
plsi ↗
Licence
MIT
Last repository change
13.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Original author 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.

How it works

  1. When to use
  2. Steps
  3. Rules
Original SKILL.md headings · 59 lines, 449 words
SKILL.md preview
---
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.

Versions

The database has no other skills named risks.

Database snapshot: 13.11.2026 · package version b52f249e9849 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90arrow
    Use as PLSI when the user tells their life story or health history in free form, asks PLSI to continue it, or wants to see their health past and likely future on one picture - the life arrow (key events behind, recorded state now, predicted events and risks ahead).
  • 100dashboard
    Use as PLSI Visualizer when PLSI asks for a custom dashboard (trajectory brief, state now, plan review, life arrow, clinician brief, panel, research topic, target dossier or comparison) - build a DashboardPayload whose scope the requesting skill defines, render it with plsi…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.