Which AI agents work with Coalition Integrated Air And Missile Defense Data Latency 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.

Coalition Integrated Air And Missile Defense Data Latency Cell by zwright8

Name: Coalition Integrated Air And Missile Defense Data Latency Cell
Rating: 4.2 (5 reviews)
Author: zwright8

Coalition Integrated Air And Missile Defense Data Latency Cell

Reduce coalition IAMD track and decision latency across mixed systems while preserving release governance. Use when operators need protocol-bound recommendations with measurable timing and failover effects.

zwright8 65117d4 2 files · 3.7 KB Updated Sep 10, 2026

File contents

Coalition Integrated Air and Missile Defense Data Latency Cell

Mission Scope

Treat this skill as a planning and decision-support aid for U.S. warfighter missions in its domain.
Start by confirming echelon, operating environment, available authorities, time horizon, and required decision points.
Keep products unclassified by default unless the user provides handling guidance and controlled data.

Workflow

Frame the mission problem with commander intent, latest indicators, and limiting assumptions.
Identify explicit branch triggers, invalidation thresholds, and confidence risks.
Build a recommended option plus at least two alternatives with clear tradeoffs in tempo, survivability, sustainment burden, and escalation risk.
Bind each critical recommendation to concrete external tools, protocol stack, and a degraded-mode branch.
Produce commander-facing and staff-action outputs with owners, suspense dates, and revalidation triggers.

Required Output Format

Situation snapshot.
Recommended option and rationale.
Alternative options with trigger conditions.
Decision points now/next/pre-delegated.
Staff tasking by owner and suspense.

Domain Products

Primary products for this skill: latency root-cause matrix, coalition track-handoff plan, release-authority timing ledger.

Domain Toolchain Defaults

Primary: tool_suite_id=ts-coalition-iamd-latency-v1 with protocol_stack_id=ps-coalition-iamd-latency-stack-v1.
Alternate: tool_suite_id=ts-joint-c2-fusion-v1 with protocol_stack_id=ps-cop-event-sharing-stack-v1.
Degraded: authenticated voice/readback + UTC acknowledgment ledger + commander decision log.

Domain Packet Defaults

Default packet ID: DPL-COAL-IAMD-LATENCY-001.
If no packet fully matches, define a provisional packet using the shared schema and assign a validation owner.

Toolchain Profile Binding

Default toolchain_id: TC-AIR-MSL-003.
Include primary_system, cross_check_system, protocol_binding, credential_scope, and fallback_path for each critical recommendation.

External Tools and Protocol Integration

Use baseline integration workflow in ../_shared/references/external-tools-protocols.md.
Bind concrete tool and protocol selections through ../_shared/references/warfighter-external-tool-and-protocol-catalog.md.
Use packet templates from ../_shared/references/domain-tool-packet-library.md and playbooks in ../_shared/references/tool-protocol-playbooks.md.
Include provenance fields: source system, refresh UTC, assumptions, confidence, and known gaps.

Authority and Assurance Gates

Apply ../_shared/references/human-agent-command-escalation-matrix.md and ../_shared/references/warfighter-tool-authority-gates.md.
Run interoperability and assurance checks from ../_shared/references/mission-assurance-checklist.md, ../_shared/references/tool-health-and-trust-monitoring.md, and ../_shared/references/us-joint-protocol-assurance-drill.md.
Downgrade to advisory-only if legal basis, authority scope, or protocol acknowledgment integrity is uncertain.

Guardrails

Flag assumptions that exceed evidence.
Separate facts, assessed judgments, and unknowns.
Do not fabricate authorities, approvals, or source evidence.

---name: coalition-integrated-air-and-missile-defense-data-latency-cedescription: Reduce coalition IAMD track and decision latency across mixed systems while preserving release governance. Use when operators need protocol-bound recommendations with measurable timing and failover effects.---# Coalition Integrated Air and Missile Defense Data Latency Cell## Mission Scope- Treat this skill as a planning and decision-support aid for U.S. warfighter missions in its domain.- Start by confirming echelon, operating environment, available authorities, time horizon, and required decision points.- Keep products unclassified by default unless the user provides handling guidance and controlled data.## Workflow1. Frame the mission problem with commander intent, latest indicators, and limiting assumptions.2. Identify explicit branch triggers, invalidation thresholds, and confidence risks.3. Build a recommended option plus at least two alternatives with clear tradeoffs in tempo, survivability, sustainment burden, and escalation risk.4. Bind each critical recommendation to concrete external tools, protocol stack, and a degraded-mode branch.5. Produce commander-facing and staff-action outputs with owners, suspense dates, and revalidation triggers.## Required Output Format1. Situation snapshot.2. Recommended option and rationale.3. Alternative options with trigger conditions.4. Decision points now/next/pre-delegated.5. Staff tasking by owner and suspense.## Domain ProductsPrimary products for this skill: latency root-cause matrix, coalition track-handoff plan, release-authority timing ledger.## Domain Toolchain Defaults- Primary: `tool_suite_id=ts-coalition-iamd-latency-v1` with `protocol_stack_id=ps-coalition-iamd-latency-stack-v1`.- Alternate: `tool_suite_id=ts-joint-c2-fusion-v1` with `protocol_stack_id=ps-cop-event-sharing-stack-v1`.- Degraded: authenticated voice/readback + UTC acknowledgment ledger + commander decision log.## Domain Packet Defaults- Default packet ID: `DPL-COAL-IAMD-LATENCY-001`.- If no packet fully matches, define a provisional packet using the shared schema and assign a validation owner.## Toolchain Profile Binding- Default `toolchain_id`: `TC-AIR-MSL-003`.- Include `primary_system`, `cross_check_system`, `protocol_binding`, `credential_scope`, and `fallback_path` for each critical recommendation.## External Tools and Protocol Integration- Use baseline integration workflow in `../_shared/references/external-tools-protocols.md`.- Bind concrete tool and protocol selections through `../_shared/references/warfighter-external-tool-and-protocol-catalog.md`.- Use packet templates from `../_shared/references/domain-tool-packet-library.md` and playbooks in `../_shared/references/tool-protocol-playbooks.md`.- Include provenance fields: source system, refresh UTC, assumptions, confidence, and known gaps.## Authority and Assurance Gates- Apply `../_shared/references/human-agent-command-escalation-matrix.md` and `../_shared/references/warfighter-tool-authority-gates.md`.- Run interoperability and assurance checks from `../_shared/references/mission-assurance-checklist.md`, `../_shared/references/tool-health-and-trust-monitoring.md`, and `../_shared/references/us-joint-protocol-assurance-drill.md`.- Downgrade to advisory-only if legal basis, authority scope, or protocol acknowledgment integrity is uncertain.## Guardrails- Flag assumptions that exceed evidence.- Separate facts, assessed judgments, and unknowns.- Do not fabricate authorities, approvals, or source evidence.

Frequently asked questions