Skip to main content
skill CX Codex

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

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

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

2Manually: put the files in place

~/.claude/skills/run/SKILL.md

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

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.

run Yiming Wu The run skill routes a task through a team pipeline, assigning work to different roles. Use it when a task needs discovery stages and a handoff to implementation. CX Codex +1 ★ 1,596repo stars run Insilico-org This Claude Code skill runs a PLSI research cycle for a project topic. It follows the cursor for one assigned move, saves the result, then stops when the budget or topic state calls for it. CX Codex +1 ★ 93repo stars minimal-run-and-audit lllllllama minimal-run-and-audit is a Claude Code skill that captures and standardizes evidence from deep learning reproduction runs, including inference, evaluation, and smoke tests. CX Codex +1 502,400installs explore-run lllllllama explore-run plans bounded exploratory machine learning runs with comparability caveats and saves summaries to explore_outputs. CX Codex +1 362,600installs dart-run-static-analysis dart-lang dart-run-static-analysis runs dart analyze to catch errors and dart fix --apply to resolve mechanical linter issues. Helps verify Dart code quality during development and before commits. CX Codex +1 21,200installs cloud-run-basics official google The cloud-run-basics skill helps an agent manage Cloud Run services, jobs, and worker pools when a project needs HTTP deployment, scheduled work, or pull-based background processing. CX Codex +1 17,532installs platform-apex-test-run forcedotcom platform-apex-test-run runs Apex tests via the Salesforce CLI, analyzes code coverage, and guides test-fix loops. Useful when investigating unit test failures or low coverage. CX Codex +1 7,300installs run-tests dotnet run-tests picks the right dotnet test invocation for a .NET repository — classic, VSTest, bridged MTP or native MTP — and runs the scope you asked for. CX Codex +1 7,000installs

From the same set85

The whole set →
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 assess 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. 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 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 roster This Claude Code skill maintains a physician’s patient roster and tracks each person’s status. It activates when a patient is added, paused, closed, or removed, or shares data with the physician. CX Codex +1 ★ 93repo stars arrow The arrow Claude Code skill turns a health history into a timeline of past events, current state, and forecasts. It runs when someone shares their story or asks to see their main risks on one chart. CX Codex +1 ★ 93repo stars

Project sponsors

Companies that keep this analytics open