Skip to main content
skill CX Codex

gather · insilico-org — Claude Code skill: research search and installation

This Claude Code skill gathers research sources and records findings with quotes. It runs when plsi research next selects the gather step.

MIT ★ 93 updated 2026-11-15

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

What gather does

gather starts with a seed paper, then runs five query families: reviews, direct searches, searches for opposing results, population-specific searches, and a single step through the seed’s references. It stores each finding with an exact quote from the source’s results section and records search details in the research graph.

The skill combines web search with the PLSI toolbelt. It uses plsi evidence search to retrieve evidence and plsi evidence verify to check identifiers; Europe PMC is the only source that returns abstracts. Quotes must come from retrieved text, since a paraphrase only verifies against itself. Calls should be spaced out: HTTP 429 and 503 responses become NETWORK_ERROR.

What it helps with

  • locate a seed review for a research question
  • build five groups of literature queries
  • record paper results with source quotes
  • tell an empty search apart from unusable results

Example prompts for the agent

  • Run the gather step for the current research question.
  • Find a seed paper and run all five query families.
  • Save the results as findings with exact source quotes.

How to install gather

1Skills CLI (Vercel)

npx skills add Insilico-org/plsi --skill gather -a claude-code

2Manually: put the files in place

~/.claude/skills/gather/SKILL.md

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

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about gather

How do I install gather in Claude Code?

Run npx skills add Insilico-org/plsi --skill gather -a claude-code. The skill file is at ~/.claude/skills/gather/SKILL.md.

What does gather do?

It searches research literature through five query families and records findings with quotes taken from source results.

What does gather need to run?

It uses PLSI commands plsi evidence search and plsi evidence verify, plus web search and the toolbelt. Search services can return NETWORK_ERROR for HTTP 429 or 503.

Source text

SKILL.md · MIT
---
name: gather
description: Use as PLSI Research Orchestrator when `plsi research next` says the move is `gather` - find a seed paper, run the five query families, read what came back and write each result down as a finding with its verbatim quote.
---

# Gather

Follow persona.md norms and `shared/team`. Owner: **PLSI Research Orchestrator**. Writes `finding` nodes and
`last_search` on the question; the shape is in `shared/research-graph`.

**Use both retrieval routes** (`lab/deep-search`, Three routes): your own web search and the toolbelt, which gives
identifiers code can verify and the publication types `design` comes from:

```bash
plsi evidence search --source europepmc --query "<query>" --limit 20   # the only source that returns abstracts
plsi evidence verify --kind pmid --id <id>
```

A quote verifies against whatever `text` you pass, so a finding from your own web search verifies as well as one
from the toolbelt.

**Pass retrieved text, never a summary of it.** A paraphrase passed as `text` verifies against itself and the
check is defeated silently. If a tool will not give you the source's own words, get them another way, or record
the finding with no `text` and say in the body that the quote could not be checked.

The services rate-limit (HTTP 429 and 503 come back as `NETWORK_ERROR`): space the calls out. A round cut short
by rate limiting is **not** an empty field; say so in `open` and record no absence.

When a search comes back thin, junk or empty, read `lab/deep-search`.

## 1. Seed first

Find **one good paper** first, ideally a recent review or meta-analysis on this question, and build queries from
its controlled vocabulary and wording. A review often shows the question is already settled.

## 2. Blocks, not sentences

One concept block per element of the question; synonyms OR'd inside a block; blocks AND'd together. A failed
search is then diagnosable: drop one block and see which was responsible.

Check every controlled-vocabulary term before using it; many model-proposed MeSH terms do not exist. A term that
does not resolve becomes a free-text synonym inside its block, never silently dropped.

## 3. Five query families, in this order

| # | Family | Purpose |
|---|---|---|
| 1 | **review** | map the field; find out whether this is already settled |
| 2 | **direct** | the question's own concept blocks |
| 3 | **against** | hunt the opposite result: "no association", "null", "failed to replicate" |
| 4 | **population** | restricted to the population that matters |
| 5 | **seed references** | one hop out from the seed paper's reference list, not recursive |

The against-family runs before the population restriction, because an unrestricted null damages a hypothesis
more than a restricted positive confirms it. Family 5 recovers the recall model-written queries lose.

## 4. Read the count before you read the papers

| Hits | What it means | What to do |
|---|---|---|
| **0** | genuinely novel, or the terms are wrong | re-query once with different vocabulary. Still zero: record the absence and stop |
| **1–20** | readable | read them |
| **20–200** | too many | filter by study design, strongest first, read the top |
| **200+** | the question is too broad | back to Ask and narrow. Do **not** read |

**Hits are not findings.** Plenty retrieved and nothing usable is `nothing-usable`, a statement about retrieval.
Only a genuine zero, twice, earns `unstudied`.

**At a zero, record the absence, never a finding.** `save` refuses a finding from a search that returned nothing
(refusal 5); the permitted output is `last_search` with two rounds, zero hits, and a `gap_why` naming the
vocabularies tried.

**"None found" has to be earned.** Write that no contradicting evidence exists only after a query designed to find
some, and name it. Otherwise the honest statement is *not searched*.

## 5. What becomes a finding

What was observed, in whom, and where it came from. Two papers reporting the same result in the same cohort are
**one finding with two sources**.

Every finding carries:

- a **verbatim quote** from the **results** sentence, not the conclusion. Copy it; never retype it.
- **`design`** and **`species`** from their closed lists in `shared/research-graph`, plus **`population`** in your
  own words and **`observed`** where the source gives a date. Put the shape in the field and the specifics in
  `population` and the body; if no value fits, use the most cautious one that does and say why in the body. `species` is what the result is **about**; a mouse result is `animal`, never `human`.
- **`origin`**: the narrowest shared source of the result (registration id, else named cohort, else consortium,
  else research group). Two papers reporting two endpoints of one trial share an origin and are one line of
  evidence. Reuse the exact string from `origins_in_use` when the source is already there: a second wording
  invents an independent line that does not exist. If you cannot tell, leave it empty.
- `studies` when the source is an aggregate: the number it pools, as a descriptor.

**A finding never computes.** Numbers go down as they appear, with no conversions or ratios.

**Ask of any marker-based finding:** if this number improved and nothing else changed, would the person be better
off? If no or unknown, the finding is `surrogate-only` and the question inherits that gap.

**Not a finding:** a review's summary of other work (go to the primary source, or record it as *one* finding
attributed to the review); a mechanism proposed in a discussion section (a hypothesis for Explain); an animal
result stated as a human one; anything the source does not say, including something true it never claimed.

## 6. Stopping

Count novelty each round: retrieved sources not already seen. When a round returns almost nothing new, stop and
record `last_search: {rounds, hits, new}`. A quiet round comes back as a `signal`; if you think the search rather
than the field was the problem, say so in `open` and keep the direction open. About five rounds of refinement is
usually what pays.

## Rules

- Verify every published identifier (`plsi evidence verify --kind pmid|doi|nct|label|evipedia|model|rule`) before
  it goes into `sources`. The user's own record has no kind: a `personal-record` source carries the event or state
  reference as written, and its quote stays unverified. Say so.
- A personal record is structured fields. Put the relevant dates in the body and name them in the hypothesis's
  `if_false`, where Test can use them.
- A private source (a Mothership release, a licensed database, a document the user supplied) is an ordinary finding
  with its release identifier and no `text`, so its quote stays unverified, and it obeys every refusal.
- Abstracts and metadata only: quote verification is partial, and unverified quotes are common. Say so rather
  than claiming more.
- Code never closes a direction: only `close_direction` does.

© Insilico-org · MIT · Insilico-org/plsi

Similar skills

SKILL.md skills catalog →

gather by other authors comes first.

gather raphaelsalaja A skill for Claude Code gathers design references from selected sources into one linked board. It runs on requests for inspiration or help improving a screen. CX Codex +1 187installs gather-business-context official Data Analytics Maintainers gather-business-context extracts business definitions, metric context, and source owners before analytical work starts. It frames the question so subsequent skills operate on verified facts. CX Codex GP ChatGPT +1 1installs find-skills vercel-labs find-skills is a Claude Code skill that locates agent skills for a task and helps assess the results. It activates when someone asks for a capability that may already be installable. CX Codex +1 4,400,000installs frontend-design official anthropics The frontend-design skill guides intentional visual design for new interfaces and redesigns. Use it when a generic generated UI is not enough. CX Codex +1 1,025,790installs agent-browser vercel-labs This Claude Code skill automates browser interaction for tasks like navigating sites, filling forms, and testing web apps. It also supports exploratory QA and Electron app automation. CX Codex +1 1,600,000installs design-taste-frontend Leonxlnx The design-taste-frontend Claude Code skill sets design rules and checks for websites. It activates for new pages, redesigns, and requests to fix a generic-looking site. CX Codex +1 802,600installs grill-me Matt Pocock grill-me interviews you about a plan or design to expose gaps and sharpen decisions. Use it before implementation starts. CX Codex +1 1,424,476installs grill-with-docs Matt Pocock The grill-with-docs skill interviews you about a plan or design and creates ADRs and a glossary along the way. Use it when decisions need sharper definition. CX Codex +1 1,219,756installs

From the same set85

The whole set →
pandaomics Skill for Claude Code queries PandaOmics tools via PLSI when open target evaluation is finished. Connects commercial scoring, grant records, and expert lists using the user's personal token. CX Codex +1 ★ 93repo stars stress This Claude Code skill builds a stress-support plan from current wellbeing context. It screens for crisis signs and reasons to involve a clinician first. CX Codex +1 ★ 93repo stars google-health This Claude Code skill connects Google Health and imports wearable metrics. It runs when PLSI is asked to link an account or fetch a date range. CX Codex +1 ★ 93repo stars panel This Claude Code skill coordinates a physician’s patient panel, handling its roster, incoming files, and clinic summaries. Requests about an individual patient go to that patient’s ward bot. CX Codex +1 ★ 93repo stars food-log The food-log Claude Code skill connects a food diary or imports nutrition history when PLSI requests it. It checks Google Health first, then can use FatSecret or an app export. CX Codex +1 ★ 93repo stars run 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 stack This Claude Code skill evaluates supplements for longevity goals against research and personal care context. It activates for questions about vitamins, supplements, or an existing stack. CX Codex +1 ★ 93repo stars urgent The urgent Claude Code skill detects emergencies and mental-health crises from user messages, bot flags, or critical values. It pauses other flows and directs the person to care. CX Codex +1 ★ 93repo stars

Project sponsors

Companies that keep this analytics open