How do I install the Cbrn Mass Casualty Triage And Decon Coordination Cell skill?

Run npx skillmds add zwright8/cbrn-mass-casualty-triage-and-decon-coordination-cell in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Which AI agents work with Cbrn Mass Casualty Triage And Decon Coordination Cell?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Who published Cbrn Mass Casualty Triage And Decon Coordination Cell?

zwright8 (@zwright8) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cbrn Mass Casualty Triage And Decon Coordination Cell by zwright8

Name: Cbrn Mass Casualty Triage And Decon Coordination Cell
Rating: 4.2 (5 reviews)
Author: zwright8

File contents

CBRN Mass Casualty Triage and Decon Coordination Cell

Mission Scope

Treat this skill as planning and decision-support for U.S. and coalition warfighter teams in this domain.
Confirm echelon, operating environment, legal authorities, classification/releasability, and decision timeline.
Keep outputs unclassified by default unless the user provides handling guidance.

Workflow

Frame the mission problem with current constraints, assumptions, and required decision points.
Build at least one recommended option plus two alternates with explicit tradeoffs.
Bind each recommendation to external tools, protocol/message formats, and degraded-mode fallbacks.
Identify legal, safety, civilian-impact, and coalition interoperability constraints before release.
Publish commander-facing decisions and staff tasking with owners and suspense times.

Required Output Format

Deliver results in this order:

Situation snapshot.
Recommended option.
Alternative options.
Decision points.
Staff tasking.
Tool/protocol execution matrix.

Domain Products

Primary products for this skill: triage/decon throughput plan, casualty routing board, contamination control timeline.

External Tools and Protocol Integration

Use this baseline domain stack and map each recommendation to at least one primary tool and one cross-check source.

Suggested tools: CBRN sensor networks, hospital bed status APIs, EMS CAD feeds, plume models, JWARN-derived alerts.
Protocol/message standards: EDXL-HAVE, CAP, HL7 FHIR, CoT.
For each external dependency include: objective, required inputs, query template, output schema, transport protocol, timeout, retry, and fallback path.
Include provenance in every output: source tool, refresh time (UTC), confidence, and known data gaps.

Guardrails

This skill is decision support only; do not issue autonomous execution instructions.
Require human command review for recommendations that materially change force posture, mission risk, or escalation potential.
Separate facts, assessed judgments, and unknowns.
If legal basis, data provenance, or tool trust is uncertain, downgrade to advisory-only and publish a constrained/degraded branch.

Interoperability Validation Checklist

Run the mission assurance workflow in ../_shared/references/mission-assurance-checklist.md.
Bind outputs to ../_shared/references/warfighter-external-tool-and-protocol-catalog.md with tool_suite_id and protocol_stack_id.
Run authority gates from ../_shared/references/warfighter-tool-authority-gates.md before publishing high-consequence recommendations.

---name: cbrn-mass-casualty-triage-and-decon-coordination-celldescription: Coordinate triage, decontamination throughput, and care routing after chemical, biological, radiological, or nuclear incidents.---# CBRN Mass Casualty Triage and Decon Coordination Cell## Mission Scope- Treat this skill as planning and decision-support for U.S. and coalition warfighter teams in this domain.- Confirm echelon, operating environment, legal authorities, classification/releasability, and decision timeline.- Keep outputs unclassified by default unless the user provides handling guidance.## Workflow1. Frame the mission problem with current constraints, assumptions, and required decision points.2. Build at least one recommended option plus two alternates with explicit tradeoffs.3. Bind each recommendation to external tools, protocol/message formats, and degraded-mode fallbacks.4. Identify legal, safety, civilian-impact, and coalition interoperability constraints before release.5. Publish commander-facing decisions and staff tasking with owners and suspense times.## Required Output FormatDeliver results in this order:1. Situation snapshot.2. Recommended option.3. Alternative options.4. Decision points.5. Staff tasking.6. Tool/protocol execution matrix.## Domain ProductsPrimary products for this skill: triage/decon throughput plan, casualty routing board, contamination control timeline.## External Tools and Protocol IntegrationUse this baseline domain stack and map each recommendation to at least one primary tool and one cross-check source.- Suggested tools: CBRN sensor networks, hospital bed status APIs, EMS CAD feeds, plume models, JWARN-derived alerts.- Protocol/message standards: EDXL-HAVE, CAP, HL7 FHIR, CoT.- For each external dependency include: objective, required inputs, query template, output schema, transport protocol, timeout, retry, and fallback path.- Include provenance in every output: source tool, refresh time (UTC), confidence, and known data gaps.## Guardrails- This skill is decision support only; do not issue autonomous execution instructions.- Require human command review for recommendations that materially change force posture, mission risk, or escalation potential.- Separate facts, assessed judgments, and unknowns.- If legal basis, data provenance, or tool trust is uncertain, downgrade to advisory-only and publish a constrained/degraded branch.## Interoperability Validation Checklist- Run the mission assurance workflow in `../_shared/references/mission-assurance-checklist.md`.- Bind outputs to `../_shared/references/warfighter-external-tool-and-protocol-catalog.md` with `tool_suite_id` and `protocol_stack_id`.- Run authority gates from `../_shared/references/warfighter-tool-authority-gates.md` before publishing high-consequence recommendations.

Frequently asked questions