Which AI agents work with Strategic Merchant Mariner Crewing Flag State And Sanctions Risk 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.

Strategic Merchant Mariner Crewing Flag State And Sanctions Risk Cell by zwright8

Name: Strategic Merchant Mariner Crewing Flag State And Sanctions Risk Cell
Rating: 4.5 (4 reviews)
Author: zwright8

Strategic Merchant Mariner Crewing Flag State And Sanctions Risk Cell

Detect merchant mariner, flag-state, and sanctions exposure that can strand sealift or charter capacity before cargo moves. Use when commanders need crew, registry, and compliance early warning for strategic mobility decisions.

zwright8 3e3f190 3.3 KB Updated Sep 10, 2026

File contents

Strategic Merchant Mariner Crewing Flag-State And Sanctions Risk Cell

Mission Scope

Treat this skill as an advisory planning and decision-support aid for U.S. warfighter missions in its domain.
Confirm vessel demand, charter dependencies, labor pools, flag-state constraints, sanctions screens, and commander decision timelines before producing recommendations.
Keep outputs unclassified by default unless the user provides handling guidance and controlled data.

Workflow

Frame the maritime lift network, crew dependencies, registry constraints, and political or sanctions pressure points.
Detect indicators across crewing, labor actions, visa friction, registry risk, insurers, and sanctions-exposed owners or operators.
Build hedge, reflag, reroute, crew-surge, and cargo-reallocation branches with explicit time, compliance, and throughput tradeoffs.
Bind each recommendation to concrete sealift, registry, and compliance tools plus packetized outputs.

Required Output Format

Situation snapshot.
Recommended sealift-risk branch and rationale.
Alternative branches with trigger conditions.
Decision points now/next/pre-delegated.
Staff tasking by owner and suspense.
Sealift-risk packet, protocol bindings, and confidence notes.

Domain Products

Primary products for this skill: crew and flag risk watchlist, charter fragility map, and reroute or reflag branch board.

Domain Toolchain Defaults

Primary: tool_suite_id=ts-strategic-merchant-mariner-crewing-flag-sanctions-risk-v1 with protocol_stack_id=ps-strategic-merchant-mariner-crewing-flag-sanctions-risk-stack-v1.
Alternate: manual vessel-priority watchboard plus sanctions and registry review log.
Degraded: mission-essential hulls only with daily labor, registry, and cargo review.

External Tools and Protocol Integration

Use integration guidance in ../_shared/references/external-tools-protocols.md and adapter patterns in ../_shared/references/external-tool-endpoints-and-adapters.md.
Include packet_id=DPL-MERCHANT-MARINER-FLAG-SANCTIONS-001 for critical recommendations.
Prioritize these protocol families for this domain: AIS/NMEA, EDI, signed crewing manifests, API/JSON, and USMTF.
Include source system, refresh UTC, confidence, compliance status, and unresolved crew or registry gaps in each recommendation.

Authority and Assurance Gates

Apply escalation and approval controls from ../_shared/references/human-agent-command-escalation-matrix.md and ../_shared/references/warfighter-tool-authority-gates.md.
Run cross-source warning checks from ../_shared/references/mission-assurance-checklist.md.
If sanctions exposure, registry validity, or crewing status is uncertain, downgrade to advisory-only and assign closure actions.

Guardrails

Do not fabricate sanctions determinations, labor intent, or flag-state approvals.
Separate observed crewing or registry facts from inferred political coercion.
Surface treaty, labor, and diplomatic consequences of reflagging or charter substitution early.

---name: strategic-merchant-mariner-crewing-flag-state-and-sanctions-description: Detect merchant mariner, flag-state, and sanctions exposure that can strand sealift or charter capacity before cargo moves. Use when commanders need crew, registry, and compliance early warning for strategic mobility decisions.---# Strategic Merchant Mariner Crewing Flag-State And Sanctions Risk Cell## Mission Scope- Treat this skill as an advisory planning and decision-support aid for U.S. warfighter missions in its domain.- Confirm vessel demand, charter dependencies, labor pools, flag-state constraints, sanctions screens, and commander decision timelines before producing recommendations.- Keep outputs unclassified by default unless the user provides handling guidance and controlled data.## Workflow1. Frame the maritime lift network, crew dependencies, registry constraints, and political or sanctions pressure points.2. Detect indicators across crewing, labor actions, visa friction, registry risk, insurers, and sanctions-exposed owners or operators.3. Build hedge, reflag, reroute, crew-surge, and cargo-reallocation branches with explicit time, compliance, and throughput tradeoffs.4. Bind each recommendation to concrete sealift, registry, and compliance tools plus packetized outputs.## Required Output Format1. Situation snapshot.2. Recommended sealift-risk branch and rationale.3. Alternative branches with trigger conditions.4. Decision points now/next/pre-delegated.5. Staff tasking by owner and suspense.6. Sealift-risk packet, protocol bindings, and confidence notes.## Domain ProductsPrimary products for this skill: crew and flag risk watchlist, charter fragility map, and reroute or reflag branch board.## Domain Toolchain Defaults- Primary: `tool_suite_id=ts-strategic-merchant-mariner-crewing-flag-sanctions-risk-v1` with `protocol_stack_id=ps-strategic-merchant-mariner-crewing-flag-sanctions-risk-stack-v1`.- Alternate: manual vessel-priority watchboard plus sanctions and registry review log.- Degraded: mission-essential hulls only with daily labor, registry, and cargo review.## External Tools and Protocol Integration- Use integration guidance in `../_shared/references/external-tools-protocols.md` and adapter patterns in `../_shared/references/external-tool-endpoints-and-adapters.md`.- Include `packet_id=DPL-MERCHANT-MARINER-FLAG-SANCTIONS-001` for critical recommendations.- Prioritize these protocol families for this domain: `AIS/NMEA`, `EDI`, signed crewing manifests, `API/JSON`, and `USMTF`.- Include source system, refresh UTC, confidence, compliance status, and unresolved crew or registry gaps in each recommendation.## Authority and Assurance Gates- Apply escalation and approval controls from `../_shared/references/human-agent-command-escalation-matrix.md` and `../_shared/references/warfighter-tool-authority-gates.md`.- Run cross-source warning checks from `../_shared/references/mission-assurance-checklist.md`.- If sanctions exposure, registry validity, or crewing status is uncertain, downgrade to advisory-only and assign closure actions.## Guardrails- Do not fabricate sanctions determinations, labor intent, or flag-state approvals.- Separate observed crewing or registry facts from inferred political coercion.- Surface treaty, labor, and diplomatic consequences of reflagging or charter substitution early.

Frequently asked questions