SkillAgentSearch skills...

indication-dossier

Build a sourced research dossier for one therapeutic indication — patient population, epidemiology, disease biology, standard of care, regulatory path, and landmark trials

Install / Use

npx skills add xuzhougeng/wisp-science --skill indication-dossier

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Supported Platforms

Universal

Our assessment of indication-dossier

indication-dossier scores 83/100 on our quality scale, 811th of 1,141 Content & Media skills we index.

Its SKILL.md is 3.9 KB long, split into 7 sections with 1 code example: a solid amount of guidance for an agent.

With 1,167 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
15/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 8 days ago, so indication-dossier is actively maintained.
  • It is released under AGPL-3.0, a copyleft license: you can use it, but modified versions you distribute must carry the same license.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-02. Automated pattern scan on 2026-10-02. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

indication-dossier compared with similar skills

All 4 of these similar skills score higher than indication-dossier; compare them before choosing.

SkillScoreStarsUpdatedFormat
indication-dossier (this skill)by xuzhougeng831.2k8d agoSKILL.md
siyuanby siyuan-note10046.6ktodayMCP Server
algorithmic-artby anthropics100177.9k10d agoSKILL.md
pptxby anthropics100177.9k10d agoSKILL.md
designby nextlevelbuilder100130.2k11d agoSKILL.md

Frequently asked questions

How do I install indication-dossier?
Run npx skills add xuzhougeng/wisp-science --skill indication-dossier. The install tabs above show the steps for each supported agent.
Which AI agents does indication-dossier work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is indication-dossier safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is AGPL-3.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is indication-dossier still maintained?
The repository was last updated 8 days ago, so indication-dossier is actively maintained.

name: indication-dossier description: Build a sourced research dossier for one therapeutic indication — patient population, epidemiology, disease biology, standard of care, regulatory path, and landmark trials. Use when the user asks for an indication overview, disease landscape, or trial-design background. license: Apache-2.0

Indication dossier

Five research phases, each writing one waypoint JSON under <workdir>/waypoints/, ending in a cited Markdown report. Waypoints make the run resumable: a later invocation reads which files exist and continues from the first missing one. The only pause for user input is after Phase 1.

The framing rule

Treat the indication as a patient population, not a disease entry. Every section answers a population question — who are these patients, how are they identified and managed, which trials would help them — rather than a textbook question about the condition. Nesting is population nesting: everyone in the child indication is in the parent.

Some inputs are not billable diagnoses at all: a biological state ("immunosenescence"), a non-accepted indication ("ageing"), an iatrogenic population ("GLP-1 induced sarcopenia"). Detect and label this early — it changes the epidemiology evidence base, the regulatory path, and what a "complete" dossier even looks like.

Inputs

| Input | Required | Meaning | |---|---|---| | indication | yes | e.g. "sarcopenia", "idiopathic pulmonary fibrosis" | | additional_context | no | focus areas, parent indication, framing | | workdir | no | waypoint/report location; default ./do_not_commit/indication-dossier-<slug>/ |

Tooling

Preferred: clinical-trials MCP for CT.gov, pubmed MCP for literature, WebSearch/WebFetch for FDA guidance, specialty-society guidelines (NCCN, AASLD, …), and CDC/WHO data; WebFetch for remote PDFs, Read for local ones; Agent subagents for parallel evidence gathering. When a listed MCP is not connected, say so and fall back to WebSearch against the public site itself.

Run protocol

Read references/standards.md first — it defines what counts as a citable finding, the anti-fabrication rules, and the report style. Phase-by-phase instructions live in references/phases.md; waypoint formats in references/waypoints.md.

  1. Identity. Resolve definition, ICD codes, aliases, parent, diagnostic status; quick CT.gov landscape count. Write meta.json. Then show the resolved identity and end the turn asking Proceed / Revise identity / Stop — the expensive phases wait for the answer (Wisp has no separate interactive-question tool, so this is a normal turn end).
  2. Epidemiology. Case definition, prevalence/incidence, demographics, natural history → epidemiology.json.
  3. Biology & standard of care. Mechanism, biomarkers, approved therapies, guidelines, unmet need → biology_soc.json.
  4. Regulatory & trials. Accepted endpoints, precedents, design parameters, landmark trials, failures → regulatory_trials.json.
  5. Synthesis. No new research threads (single targeted gap-fills only). Write indication_dossier_report.md and research_output.json, then mark progress.json complete.

After each of phases 2–5, write the waypoint, emit a ≤200-word summary of findings and open uncertainties, and continue directly.

Resuming

When workdir already contains waypoints: list which phases are complete (file exists and is non-empty), show the meta summary, and ask which phase to run. Never overwrite an existing waypoint without confirmation.

Output layout

<workdir>/waypoints/
├── progress.json                 # loop control, flipped last
├── meta.json                     # phase 1
├── epidemiology.json             # phase 2
├── biology_soc.json              # phase 3
├── regulatory_trials.json        # phase 4
├── sources_evaluated.json        # appended by every phase
├── research_output.json          # phase 5, structured
└── indication_dossier_report.md  # phase 5, the deliverable

Related Skills

View on GitHub
GitHub Stars1.2k
CategoryContent
Updated8d ago
Forks119

Languages

Rust

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions