← Browse

@companion-inc/indication-dossier

A

Build a source-backed biomedical indication dossier. Use when a research task asks for disease biology, target rationale, patient segmentation, biomarkers, trials, drugs, competitive landscape, or translational evidence.

skillclaude

Install

agr install @companion-inc/indication-dossier --target claude

Writes 1 file into .claude/skills/, pinned to git-a53108d0.

  • .claude/skills/indication-dossier/SKILL.md

Document


name: indication-dossier description: Build a source-backed biomedical indication dossier. Use when a research task asks for disease biology, target rationale, patient segmentation, biomarkers, trials, drugs, competitive landscape, or translational evidence.

Indication Dossier

Use this skill to assemble a biomedical evidence packet for a disease, target, mechanism, biomarker, or therapy.

Workflow:

  1. Define the indication, patient segment, intervention or target, and decision the dossier must support.
  2. Gather evidence from literature, clinical trials, Open Targets, ChEMBL, CIViC, ClinGen, cBioPortal, DepMap/COSMIC-compatible sources, and other Feynman Bio Tools as relevant.
  3. Separate human evidence, model-system evidence, mechanism, biomarkers, clinical precedent, safety, and open questions.
  4. Rank claims by source strength and reproducibility. Flag missing cohorts, confounders, and assay limitations.
  5. Save the dossier and provenance sidecar in outputs/.

Do not turn sparse evidence into a clinical recommendation.

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-a53108d0a6792026-07-31