How do I install the Joint Denied Comms Line Of Bearing Triangulation Cell skill?

Run npx skillmds add zwright8/joint-denied-comms-line-of-bearing-triangulation-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 Joint Denied Comms Line Of Bearing Triangulation 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 Joint Denied Comms Line Of Bearing Triangulation Cell?

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

Joint Denied Comms Line Of Bearing Triangulation Cell by zwright8

Name: Joint Denied Comms Line Of Bearing Triangulation Cell
Rating: 4.5 (4 reviews)
Author: zwright8

File contents

Joint Denied Comms Line-of-Bearing Triangulation Cell

Mission Scope

Treat this skill as a planning and decision-support aid for U.S. warfighter missions in this domain.
Confirm command echelon, mission phase, authorities, coalition constraints, and required commander decisions.
Keep output unclassified by default unless handling guidance is provided.

Workflow

Frame mission problem with time constraints, threat picture, force posture, and readiness state.
Build one recommended COA plus at least two alternatives with explicit tradeoffs.
Identify branch/sequel triggers, data dependencies, and command approval gates.
Bind each critical recommendation to external tools, protocol stack, and degraded-mode fallback.
Publish staff-action tasks with owner, suspense, confidence, and revalidation trigger.

Required Output Format

Situation snapshot and key changes
Recommended COA and rationale
Alternative COAs with triggers
Decision points and escalation gates
Staff task tracker with owners/suspense
Tool invocation packets and protocol bindings

Domain Products

Primary products for this skill: line-of-bearing fusion plot, emitter confidence map, action recommendation matrix.

Domain Tooling and Protocol Baseline

Preferred external toolsets for this domain: EW direction-finding systems, triangulation solver tools, SIGINT correlation boards, ATAK/WinTAK.
Preferred protocol profiles for coordination and machine exchange: CoT, Link 16 J-series, USMTF, API/JSON.
Use ../_shared/references/warfighter-external-tool-and-protocol-catalog.md to select tool_suite_id and protocol_stack_id.
Use ../_shared/references/domain-tool-packet-library.md to select packet_id and protocol_profile.

Interoperability and Trust Validation

Run ../_shared/references/mission-assurance-checklist.md prior to release.
Apply authority and escalation controls from ../_shared/references/warfighter-tool-authority-gates.md.
Include provenance, UTC freshness, confidence, and known-gap declarations for every critical recommendation.

Guardrails

Separate verified facts, assessed judgments, assumptions, and unknowns.
Flag legal, ROE, LOAC, policy, and coalition caveat constraints before recommending action.
Do not fabricate classified sources, authorities, or approvals.
If data trust or authority is below threshold, downgrade to advisory-only and request human command decision.

---name: joint-denied-comms-line-of-bearing-triangulation-celldescription: Generate emitter geolocation and command options when conventional comms are denied and only direction-finding reports are available.---# Joint Denied Comms Line-of-Bearing Triangulation Cell## Mission Scope- Treat this skill as a planning and decision-support aid for U.S. warfighter missions in this domain.- Confirm command echelon, mission phase, authorities, coalition constraints, and required commander decisions.- Keep output unclassified by default unless handling guidance is provided.## Workflow1. Frame mission problem with time constraints, threat picture, force posture, and readiness state.2. Build one recommended COA plus at least two alternatives with explicit tradeoffs.3. Identify branch/sequel triggers, data dependencies, and command approval gates.4. Bind each critical recommendation to external tools, protocol stack, and degraded-mode fallback.5. Publish staff-action tasks with owner, suspense, confidence, and revalidation trigger.## Required Output Format1. Situation snapshot and key changes2. Recommended COA and rationale3. Alternative COAs with triggers4. Decision points and escalation gates5. Staff task tracker with owners/suspense6. Tool invocation packets and protocol bindings## Domain ProductsPrimary products for this skill: line-of-bearing fusion plot, emitter confidence map, action recommendation matrix.## Domain Tooling and Protocol Baseline- Preferred external toolsets for this domain: EW direction-finding systems, triangulation solver tools, SIGINT correlation boards, ATAK/WinTAK.- Preferred protocol profiles for coordination and machine exchange: CoT, Link 16 J-series, USMTF, API/JSON.- Use ../_shared/references/warfighter-external-tool-and-protocol-catalog.md to select tool_suite_id and protocol_stack_id.- Use ../_shared/references/domain-tool-packet-library.md to select packet_id and protocol_profile.## Interoperability and Trust Validation- Run ../_shared/references/mission-assurance-checklist.md prior to release.- Apply authority and escalation controls from ../_shared/references/warfighter-tool-authority-gates.md.- Include provenance, UTC freshness, confidence, and known-gap declarations for every critical recommendation.## Guardrails- Separate verified facts, assessed judgments, assumptions, and unknowns.- Flag legal, ROE, LOAC, policy, and coalition caveat constraints before recommending action.- Do not fabricate classified sources, authorities, or approvals.- If data trust or authority is below threshold, downgrade to advisory-only and request human command decision.

Frequently asked questions