Which AI agents work with Joint Denied Environment Vertical Datum Reconciliation 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.

Joint Denied Environment Vertical Datum Reconciliation Cell by zwright8

Name: Joint Denied Environment Vertical Datum Reconciliation Cell
Rating: 4.2 (5 reviews)
Author: zwright8

Joint Denied Environment Vertical Datum Reconciliation Cell

Reconcile vertical datum mismatches in denied environments to prevent fires and mobility error. Use when multi-source terrain products disagree and precision effects depend on elevation trust.

zwright8 3cfedbe 2 files · 3.8 KB Updated Sep 10, 2026

File contents

Joint Denied Environment Digital Map Vertical Datum Reconciliation 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 domain indicators, commander priorities, and branch triggers.
Identify assumptions, decision thresholds, and invalidation signals.
Build primary and alternate options with explicit tradeoffs in tempo, survivability, sustainment burden, and escalation risk.
Integrate dependencies across C2, intelligence, fires/effects, sustainment, protection, legal constraints, and coalition interoperability.
Produce commander-facing outputs and a staff-action plan with owners, suspense dates, and triggers.

Required Output Format

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

Domain Products

Primary products for this skill: vertical datum discrepancy ledger, terrain correction priority queue, precision-risk advisory.

Domain Toolchain Defaults

Primary: tool_suite_id=ts-vertical-datum-reconciliation-v1 with protocol_stack_id=ps-vertical-datum-reconciliation-stack-v1.
Alternate: tool_suite_id=ts-joint-c2-fusion-v1 with protocol_stack_id=ps-cop-event-sharing-stack-v1.
Degraded: use authenticated voice/readback + UTC acknowledgment ledger + manual fallback board.

External Tool Stack and Protocols

Preferred tools: mission-domain planners, operational dashboards, independent cross-check analytics, and command-approved audit ledgers.
Preferred protocol families: USMTF, API/JSON, Link 16 J-series, NATO APP-11/ADatP-3 where coalition exchange is required.
Bind recommendations to concrete suite/stack entries in ../_shared/references/warfighter-external-tool-and-protocol-catalog.md.
Use protocol packets in ../_shared/references/tool-protocol-playbooks.md and ../_shared/references/domain-tool-packet-library.md.
Include provenance fields: source system, refresh UTC, confidence, and key gaps.

Domain Packet Defaults

Default packet IDs: DPL-VERTICAL-DATUM-RECON-001.
If no packet fully matches, define a provisional packet using the shared schema and assign a validation owner.

Tool Invocation Contract

For each critical dependency include: objective, required inputs, query/action template, expected output schema, protocol/transport, and fallback path.
Map each tool output to a commander decision point and a staff task with suspense.
If confidence drops below mission threshold, mark recommendations provisional and issue a degraded-mode branch.

Authority and Assurance Gates

Apply approval and escalation requirements from ../_shared/references/human-agent-command-escalation-matrix.md and ../_shared/references/warfighter-tool-authority-gates.md.
Run protocol conformance checks from ../_shared/references/us-joint-protocol-assurance-drill.md before high-impact recommendations.
If authority, legal basis, or acknowledgment integrity is uncertain, downgrade to advisory-only with explicit commander prompts.

---name: joint-denied-environment-vertical-datum-reconciliation-celldescription: Reconcile vertical datum mismatches in denied environments to prevent fires and mobility error. Use when multi-source terrain products disagree and precision effects depend on elevation trust.---# Joint Denied Environment Digital Map Vertical Datum Reconciliation 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 domain indicators, commander priorities, and branch triggers.2. Identify assumptions, decision thresholds, and invalidation signals.3. Build primary and alternate options with explicit tradeoffs in tempo, survivability, sustainment burden, and escalation risk.4. Integrate dependencies across C2, intelligence, fires/effects, sustainment, protection, legal constraints, and coalition interoperability.5. Produce commander-facing outputs and a staff-action plan with owners, suspense dates, and triggers.## Required Output Format1. Situation snapshot.2. Recommended option.3. Alternative options.4. Decision points now/next/pre-delegated.5. Staff tasking by owner and suspense.## Domain ProductsPrimary products for this skill: vertical datum discrepancy ledger, terrain correction priority queue, precision-risk advisory.## Domain Toolchain Defaults- Primary: `tool_suite_id=ts-vertical-datum-reconciliation-v1` with `protocol_stack_id=ps-vertical-datum-reconciliation-stack-v1`.- Alternate: `tool_suite_id=ts-joint-c2-fusion-v1` with `protocol_stack_id=ps-cop-event-sharing-stack-v1`.- Degraded: use authenticated voice/readback + UTC acknowledgment ledger + manual fallback board.## External Tool Stack and Protocols- Preferred tools: mission-domain planners, operational dashboards, independent cross-check analytics, and command-approved audit ledgers.- Preferred protocol families: USMTF, API/JSON, Link 16 J-series, NATO APP-11/ADatP-3 where coalition exchange is required.- Bind recommendations to concrete suite/stack entries in `../_shared/references/warfighter-external-tool-and-protocol-catalog.md`.- Use protocol packets in `../_shared/references/tool-protocol-playbooks.md` and `../_shared/references/domain-tool-packet-library.md`.- Include provenance fields: source system, refresh UTC, confidence, and key gaps.## Domain Packet Defaults- Default packet IDs: DPL-VERTICAL-DATUM-RECON-001.- If no packet fully matches, define a provisional packet using the shared schema and assign a validation owner.## Tool Invocation Contract- For each critical dependency include: objective, required inputs, query/action template, expected output schema, protocol/transport, and fallback path.- Map each tool output to a commander decision point and a staff task with suspense.- If confidence drops below mission threshold, mark recommendations `provisional` and issue a degraded-mode branch.## Authority and Assurance Gates- Apply approval and escalation requirements from `../_shared/references/human-agent-command-escalation-matrix.md` and `../_shared/references/warfighter-tool-authority-gates.md`.- Run protocol conformance checks from `../_shared/references/us-joint-protocol-assurance-drill.md` before high-impact recommendations.- If authority, legal basis, or acknowledgment integrity is uncertain, downgrade to advisory-only with explicit commander prompts.

Frequently asked questions