Labcoat biomedical discipline
Skill qchiujunhao/labcoat/skills/labcoat-biomedical-discipline
Skills, hooks, and CLI checks for safer biomedical AI coding agents.
npx -y skills add qchiujunhao/labcoat --skill labcoat-biomedical-disciplineAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
General Labcoat router for biomedical, bioinformatics, omics, clinical-adjacent research software, gene, variant, disease, drug, protein, cell type, tissue, or pathway claims. Use to identify biomedical risk category and load the relevant Labcoat skill before coding, reviewing, or writing.
SKILL.md
1.9 KB, as published. Nobody here has run it
Labcoat Biomedical Discipline
Use this skill first for biomedical or clinical-adjacent coding-agent work. Identify the risk category, then load the smallest relevant Labcoat skill.
Decision Ladder
- Classify the work: entity, omics reproducibility, evidence/claims, clinical boundary, biosecurity boundary, biomedical ML, dependency/minimal code, or PR review.
- Require explicit context for genome build, species, identifier system, evidence provenance, and patient/synthetic status when relevant.
- Prefer existing codebase behavior, standard library, and already-installed dependencies.
- Escalate unknown genome build, species, patient-specific interpretation, PHI status, or high-risk biosecurity ambiguity to a human.
Allowed
- Build research software, bioinformatics tooling, checks, tests, and documentation.
- Use synthetic examples clearly marked as synthetic.
- Summarize high-level safety or compliance constraints.
- Ask precise clarification questions when domain ambiguity changes correctness.
Disallowed
- Do not invent genome builds, species, evidence, PMID, DOI, clinical validity, or treatment recommendations.
- Do not give patient-specific diagnosis, dosing, triage, or treatment advice.
- Do not provide actionable wet-lab optimization, pathogen/toxin engineering, or biosecurity-sensitive protocol details.
- Do not weaken Labcoat hooks, rules, or tests to make a loop pass.
Output
Use:
- Risk category:
- Required context:
- Labcoat skills to load:
- Minimal safe next action:
Read references/trigger-map.md when deciding which specific Labcoat skill applies.