How do I install the Homeland Spaceport Gnss Interference Emergency Cell skill?

Run npx skillmds add zwright8/homeland-spaceport-gnss-interference-emergency-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 Homeland Spaceport Gnss Interference Emergency 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 Homeland Spaceport Gnss Interference Emergency Cell?

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

Homeland Spaceport Gnss Interference Emergency Cell by zwright8

Name: Homeland Spaceport Gnss Interference Emergency Cell
Rating: 4.2 (5 reviews)
Author: zwright8

File contents

Homeland Spaceport GNSS Interference Emergency Cell

Mission Scope

Treat this skill as planning and decision support for U.S. warfighter operations.
Confirm command authority, data handling limits, and decision timeline before recommendations.
Keep outputs unclassified unless explicit handling guidance is provided.

Workflow

Frame the operational problem, desired effect, constraints, and branch triggers.
Build primary and alternate options with confidence, dependencies, and timing.
Tie every critical recommendation to tool outputs and protocol exchange paths.
Publish commander decision prompts plus staff action tracker with owners and suspense.

Required Output Format

Situation snapshot.
Recommended course of action.
Alternate/degraded branch.
Decision gates and authorities.
Staff tasks and suspense.

Domain Products

Primary products: mission option matrix, protocol-bound tool invocation packet, risk and confidence register.

External Tools and Protocol Integration

Use ../_shared/references/external-tools-protocols.md and ../_shared/references/tool-protocol-playbooks.md.
Use packet template DPL-SPACEPORT-GNSS-001 from ../_shared/references/domain-tool-packet-library.md.
Bind tool and protocol choices to ts-spaceport-gnss-emergency-v1 and ps-spaceport-gnss-emergency-stack-v1 from ../_shared/references/warfighter-external-tool-and-protocol-catalog.md.
Align execution profile with space-satcom-resilience-v1 from ../_shared/references/joint-operations-external-toolchain-profiles.md.
Include source freshness UTC, confidence, and degraded transition triggers.

Guardrails

Separate observed facts, assessed judgment, and unknowns.
Flag any recommendation that lacks dual-source corroboration.
Require explicit human approval before recommending actions that materially change force posture.

Domain Toolchain Defaults

Primary: tool_suite_id=ts-spaceport-gnss-emergency-v1 with protocol_stack_id=ps-spaceport-gnss-emergency-stack-v1.
Alternate: choose one profile-aligned suite from the shared catalog and document tradeoffs.
Degraded: manual reporting and acknowledgment chain with explicit timing and confidence penalties.

Domain Packet Defaults

Default packet ID: DPL-SPACEPORT-GNSS-001.
If scope mismatch exists, define a provisional packet and assign validation owner with suspense.

---name: homeland-spaceport-gnss-interference-emergency-celldescription: Coordinate launch safety and range continuity during GNSS jamming, spoofing, and timing instability events.---# Homeland Spaceport GNSS Interference Emergency Cell## Mission Scope- Treat this skill as planning and decision support for U.S. warfighter operations.- Confirm command authority, data handling limits, and decision timeline before recommendations.- Keep outputs unclassified unless explicit handling guidance is provided.## Workflow1. Frame the operational problem, desired effect, constraints, and branch triggers.2. Build primary and alternate options with confidence, dependencies, and timing.3. Tie every critical recommendation to tool outputs and protocol exchange paths.4. Publish commander decision prompts plus staff action tracker with owners and suspense.## Required Output Format1. Situation snapshot.2. Recommended course of action.3. Alternate/degraded branch.4. Decision gates and authorities.5. Staff tasks and suspense.## Domain ProductsPrimary products: mission option matrix, protocol-bound tool invocation packet, risk and confidence register.## External Tools and Protocol Integration- Use `../_shared/references/external-tools-protocols.md` and `../_shared/references/tool-protocol-playbooks.md`.- Use packet template `DPL-SPACEPORT-GNSS-001` from `../_shared/references/domain-tool-packet-library.md`.- Bind tool and protocol choices to `ts-spaceport-gnss-emergency-v1` and `ps-spaceport-gnss-emergency-stack-v1` from `../_shared/references/warfighter-external-tool-and-protocol-catalog.md`.- Align execution profile with `space-satcom-resilience-v1` from `../_shared/references/joint-operations-external-toolchain-profiles.md`.- Include source freshness UTC, confidence, and degraded transition triggers.## Guardrails- Separate observed facts, assessed judgment, and unknowns.- Flag any recommendation that lacks dual-source corroboration.- Require explicit human approval before recommending actions that materially change force posture.## Domain Toolchain Defaults- Primary: `tool_suite_id=ts-spaceport-gnss-emergency-v1` with `protocol_stack_id=ps-spaceport-gnss-emergency-stack-v1`.- Alternate: choose one profile-aligned suite from the shared catalog and document tradeoffs.- Degraded: manual reporting and acknowledgment chain with explicit timing and confidence penalties.## Domain Packet Defaults- Default packet ID: `DPL-SPACEPORT-GNSS-001`.- If scope mismatch exists, define a provisional packet and assign validation owner with suspense.

Frequently asked questions