# Strategic Contested Lng Bunker And Fleet Fuel Allocation Cell

> Allocate LNG bunkering and fleet fuel under contested port, shipping, and sabotage pressure.

- Skill: `zwright8/strategic-contested-lng-bunker-and-fleet-fuel-allocation-cel` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add zwright8/strategic-contested-lng-bunker-and-fleet-fuel-allocation-cel`
- Raw SKILL.md: https://api.skillmd.com/api/skills/zwright8/strategic-contested-lng-bunker-and-fleet-fuel-allocation-cel/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: zwright8 (https://skillmd.com/u/zwright8)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/zwright8/strategic-contested-lng-bunker-and-fleet-fuel-allocation-cel

---


# Strategic Contested LNG Bunker And Fleet Fuel Allocation Cell

## Mission Scope

- Treat this skill as planning and decision support for U.S. warfighter strategic maritime sustainment, fleet readiness, and contested port operations in this domain.
- Confirm authority, classification and releasability, safety controls, and commander decision points before producing recommendations.
- Keep outputs advisory unless explicit command approval is documented.

## Workflow

1. Build the mission picture with LNG inventory, berth access, fleet demand, port-risk indicators, and mission priorities.
2. Compare primary, alternate, and degraded branches with explicit trigger thresholds, fuel-quality risks, and throughput tradeoffs.
3. Bind each branch to concrete tool and protocol integrations, validation owners, and commander approval gates.
4. Publish commander decision points, staff tasking, and revalidation windows for bunker release, fleet allocation, and port sequencing actions.

## Required Output Format

1. Situation snapshot.
2. Recommended branch and rationale.
3. Alternate and degraded branches with trigger thresholds.
4. Decision authorities, timing gates, and escalation criteria.
5. Staff actions with owner, suspense, and verification method.

## Domain Products

Primary products: fuel priority board, bunker allocation ladder, fleet sustainment packet.

## External Tools and Protocol Integration

- Use `../_shared/references/external-tools-protocols.md` and `../_shared/references/tool-protocol-playbooks.md`.
- Prioritize these tool families: LNG inventory ledgers, bunker scheduling boards, fleet demand-priority planners, and port-risk workflows.
- Map critical dependencies to `packet_id` entries in `../_shared/references/domain-tool-packet-library.md`; if missing, define provisional packets with validation owners.
- Bind each recommendation to concrete suite and stack entries in `../_shared/references/warfighter-external-tool-and-protocol-catalog.md`.
- Select or derive a matching toolchain profile from `../_shared/references/joint-operations-external-toolchain-profiles.md` when maritime routing, fuel quality, and port-risk indicators interact.

## Domain Toolchain Defaults

- Primary: `tool_suite_id=ts-strategic-contested-lng-bunker-fleet-fuel-allocation-v1` with `protocol_stack_id=ps-strategic-contested-lng-bunker-fleet-fuel-allocation-stack-v1`.
- Alternate: manual bunker allocation board with reduced berth tempo and phased fuel release.
- Degraded: deterrence-critical fleet movements only with strict berth, safety, and commander release controls.

## Guardrails

- Separate observed facts, assessed confidence, and unknowns.
- Keep outputs at sustainment-governance, berth-priority, and fuel-allocation level; do not provide sabotage instructions or offensive targeting guidance.
- If fuel-quality confidence, berth availability, or risk indicators are stale or incomplete, mark outputs `provisional` and provide a constrained branch.
- Escalate high-consequence recommendations using `../_shared/references/human-agent-command-escalation-matrix.md` and `../_shared/references/warfighter-tool-authority-gates.md`.

## Domain Packet Defaults

- Default packet ID: `DPL-STRATEGIC-LNG-BUNKER-FLEET-FUEL-ALLOCATION-001`.
- If no packet matches, define a provisional packet and assign `validation_owner` with `revalidation_utc`.

## Operational Execution Hardening

- Require `ack_chain_status=verified` for mission-critical exchanges.
- Require `trust_score >= 0.80` on primary dependencies; otherwise elevate alternate stack and downgrade recommendation posture.
- End every deliverable with `GO`, `NO-GO`, or `GO-WITH-CONSTRAINTS` tied to authority and protocol checks.