run · insilico-org, analyst — Claude Code skill for cohort analysis
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.
MIT ★ 93 updated 2026-11-15
npx skills add Insilico-org/plsi --skill run -a claude-codeWhat run does
The skill registers the chosen hypothesis and data-release version with the Longevity Mothership, then runs the analysis using the fixed specification. It requires the plsi mothership commands and a data release on the local computer. The release.json file must not be read before the preregistration receipt arrives.
After the run, the skill sends the materials for a PLSI Challenger review and prepares a finding with the effect interval, sample size, p-value, and objections. Null results and failures are reported too; groups cannot be widened, and a changed specification or release needs a new preregistration. The skill does not send files itself: Data Controller handles their delivery.
What it helps with
- register a hypothesis and analysis spec before running it
- rerun an analysis against the same data-release version
- send results and supporting files for PLSI Challenger review
- write a finding that includes objections and null results
Example prompts for the agent
- Take this selected hypothesis through preregistration, analysis, and a PLSI finding.
- Register the specification, wait for the receipt, then run the unchanged analysis.
- Prepare the finding with PLSI Challenger's objections, including a null result.
How to install run
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill run -a claude-code2Manually: put the files in place
~/.claude/skills/run/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/run/
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill run -a codex2Manually: put the files in place
.agents/skills/run/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill run -a cursor2Manually: put the files in place
.cursor/skills/run/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Insilico-org/plsi skills/analyst/run2Manually: put the files in place
.github/skills/run/SKILL.md1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill run -a gemini-cli2Platform CLI
gemini skills install https://github.com/Insilico-org/plsi --path skills/analyst/runManually: put the files in place
.devin/skills/run/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 run
How do I install run in Claude Code?
Run npx skills add Insilico-org/plsi --skill run -a claude-code. The skill file is available at ~/.claude/skills/run/SKILL.md.
What does the run skill do?
It registers a selected hypothesis, analyzes the fixed data-release version, submits materials for PLSI Challenger review, and prepares a finding. Failures and null results are reported as well.
What does run need to work?
It needs the plsi mothership commands and a data release on the local computer. Analysis starts only after the preregistration receipt is received.
Source text
SKILL.md · MIT
---
name: run
description: Use as PLSI Cohort Analyst when the researcher picked a hypothesis - preregister it with the Longevity Mothership, run the identical analysis on the data release on this computer, and write the finding, null results included, for PLSI Challenger and PLSI Data Controller.
---
# PLSI preregister, run, report
**Status: draft**. The numbers come only from `plsi mothership analyze`;
the Mother reruns the same spec on the same release and must get the same result.
## When to use
- PLSI relays the researcher's pick from `analyst/hypothesize` (thread and `hypotheses.json` in `files`).
- PLSI relays the preregistration receipt, then Challenger's objections.
## Steps
1. **Preregister.** Check the budget line in the request `summary` ("Cohort Analyst analyses: <m> of <n>, <month>";
m < n, else a `result` "budget used"). The catalog carries no release version, so fetch the latest release and take only the `version` from the
command's output (it reports the version and the cell count, not the values):
```bash
plsi mothership release --version latest --out <PLSI_HOME>/work/<thread>/release.json
```
Never open or read `release.json` before the preregistration receipt arrives: the hypothesis and spec were fixed
without the values, and they stay that way. Write the picked hypothesis, that release version, the spec, the
outcome, `alpha`, `direction` and `parents` to `<PLSI_HOME>/work/<thread>/prereg-input.json`, then:
```bash
plsi mothership prereg --spec <PLSI_HOME>/work/<thread>/prereg-input.json
```
It writes the gate-checked message (its `data` names the file). Return that file for Data Controller
(`controller/egress`, kind "preregistration") and stop until PLSI relays the receipt. No receipt, no analysis.
2. **Run** on the preregistered release with the preregistered spec, unchanged (`release.json` from step 1 is
that release; fetch it again by version only if it is missing):
```bash
plsi mothership release --version <release> --out <PLSI_HOME>/work/<thread>/release.json
plsi mothership analyze --release <PLSI_HOME>/work/<thread>/release.json --spec <PLSI_HOME>/work/<thread>/spec.json
```
`spec.json` is the preregistration's `analysis`, copied unchanged; save the output as `result.json`.
`analyze` fails with `TOO_FEW_CELLS` or `DEGENERATE_CELLS`, or a coordinate is missing: return a `result` to PLSI
with the code and the preregistration id. That is the report; it does not go to Challenger or `finding`, and the
groups are never widened to make it run.
3. **Challenge.** Save the findings ledger (`plsi mothership findings`) as
`<PLSI_HOME>/work/<thread>/ledger.json`. Return one `result` with the preregistration message file, `release.json`,
`spec.json`, `result.json` and `ledger.json` in `files` and the work for Challenger (`challenger/challenge`, Claim mode). Wait for PLSI to relay the objections.
4. **Finding.** Write the summary: the effect with its interval, n, p against the preregistered `alpha` and
direction, the multiple-testing load, Challenger's objections as written, and the grade "observational,
self-selected cohort, hypothesis-generating"; no dates, links or id numbers (the gate refuses them). The gate
reads any run of 8 or more digits and separators as an id number, so round every number in the summary to 2-3
significant digits ("effect -1.2 (95% CI -2.1 to -0.37), n 46, p 0.012"); the exact numbers travel in the
finding's numeric `result`. Paraphrase an objection that quotes a long number. A null or
contrary result is written the same way. The command reruns the preregistered analysis itself, so the
finding's numbers are the code's:
```bash
plsi mothership finding --prereg <preregistration message file> --release <PLSI_HOME>/work/<thread>/release.json --summary "<summary>"
```
Return the finding file for Data Controller (`controller/egress`, kind "finding"); PLSI shows a `cleared` one on
one approval card and Data Controller sends it.
## Rules
- One preregistration, one analysis: a changed spec, group or release is a new preregistration.
- Every run is reported, failures and nulls included; never drop or retry an analysis because of its result.
- Never send anything yourself, never edit the release or the result, and never put a person, an instance or the
contributor code in any file.
© Insilico-org · MIT · Insilico-org/plsi
Similar skills
SKILL.md skills catalog →run by other authors comes first.