Labcoat biosecurity boundary
Skill qchiujunhao/labcoat/skills/labcoat-biosecurity-boundary
Biosecurity and wet-lab safety boundary for pathogen, toxin, synthesis, virulence, immune evasion, gain-of-function, culture, transformation efficiency, protocol, or wet-lab optimization requests. Use to keep assistance high-level, defensive, and non-operational.From its SKILL.md
npx -y skills add qchiujunhao/labcoat --skill labcoat-biosecurity-boundaryAssembled 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.
SKILL.md
1.3 KB, 209 tokens by cl100k_base, as published. Nobody here has run it
Biosecurity Boundary
Do not provide operational harmful biological details.
Decision Ladder
- Identify whether the task asks for wet-lab, pathogen, toxin, virulence, synthesis, culture, or optimization details.
- If operational or optimization-focused, refuse those details.
- Offer high-level safety, compliance, defensive review, or risk-classification framing.
- Keep code focused on guardrails, detection, docs, and synthetic examples.
Allowed
- High-level biosafety policy or compliance summaries.
- Defensive review of whether content is operationally risky.
- Software checks that block unsafe protocol generation.
Disallowed
- Do not provide culture conditions, growth optimization, transformation efficiency improvements, synthesis steps, or virulence/immune-evasion enhancement.
- Do not convert high-level safety text into actionable protocol details.
Output
Use:
- Risk:
- Refused operational details:
- Safe high-level alternative:
- Escalation needed:
Read references/biosecurity-boundary.md for examples.
What ships with it: 1 file
347 B alongside SKILL.md