How do I install the Joint Near Space Haps Mesh Resilience Cell skill?

Run npx skillmds add zwright8/joint-near-space-haps-mesh-resilience-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.

Is Joint Near Space Haps Mesh Resilience Cell safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Joint Near Space Haps Mesh Resilience 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.

Is Joint Near Space Haps Mesh Resilience Cell free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Joint Near Space Haps Mesh Resilience Cell?

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

Joint Near Space Haps Mesh Resilience Cell by zwright8

Name: Joint Near Space Haps Mesh Resilience Cell
Rating: 4.5 (4 reviews)
Author: zwright8

Joint Near Space Haps Mesh Resilience Cell

Synchronize resilient high-altitude pseudo-satellite and tactical mesh operations for U.S. warfighters under jamming, weather, and attrition pressure. Use when missions require assured C2 continuity between terrestrial and near-space nodes.

zwright8 dedafd9 2 files · 3.3 KB Updated Sep 10, 2026

File contents

Joint Near-Space HAPS Mesh Resilience Cell

Mission Scope

Treat this skill as planning and decision support for U.S. warfighter operations in this domain.
Confirm authority, classification/releasability, coalition sharing limits, and required commander decisions.
Keep outputs advisory unless explicit command approval is documented.

Workflow

Build the mission picture with threat indicators, critical dependencies, and timing constraints.
Compare primary, alternate, and degraded branches with explicit triggers and uncertainty notes.
Bind each branch to concrete tool/protocol integrations and validation owners.
Publish commander decision points, staff tasking, and revalidation windows.

Required Output Format

Situation snapshot.
Recommended branch and rationale.
Alternate/degraded branches with trigger thresholds.
Decision authorities, timing gates, and escalation criteria.
Staff actions (owner, suspense, and verification method).

Domain Products

Primary products: HAPS continuity matrix, mesh failover trigger ledger, commander comms branch brief.

External Tools and Protocol Integration

Use ../_shared/references/external-tools-protocols.md and ../_shared/references/tool-protocol-playbooks.md.
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/stack entries in ../_shared/references/warfighter-external-tool-and-protocol-catalog.md.

Domain Toolchain Defaults

Primary: tool_suite_id=ts-near-space-haps-resilience-v1 with protocol_stack_id=ps-near-space-haps-resilience-stack-v1.
Alternate: tool_suite_id=ts-space-satcom-v1 with protocol_stack_id=ps-space-ground-failover-stack-v1.
Degraded: authenticated voice/text branch with UTC event logs, cross-check witness, and delayed machine reconciliation.

Guardrails

Separate observed facts, assessed confidence, and unknowns.
If tool trust, authority, or data freshness is below threshold, 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 IDs: DPL-C2-DISP-002, DPL-SPECTRUM-REMEDIATION-002, DPL-SPACE-C2-LINK-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.

---name: joint-near-space-haps-mesh-resilience-celldescription: Synchronize resilient high-altitude pseudo-satellite and tactical mesh operations for U.S. warfighters under jamming, weather, and attrition pressure. Use when missions require assured C2 continuity between terrestrial and near-space nodes.---# Joint Near-Space HAPS Mesh Resilience Cell## Mission Scope- Treat this skill as planning and decision support for U.S. warfighter operations in this domain.- Confirm authority, classification/releasability, coalition sharing limits, and required commander decisions.- Keep outputs advisory unless explicit command approval is documented.## Workflow1. Build the mission picture with threat indicators, critical dependencies, and timing constraints.2. Compare primary, alternate, and degraded branches with explicit triggers and uncertainty notes.3. Bind each branch to concrete tool/protocol integrations and validation owners.4. Publish commander decision points, staff tasking, and revalidation windows.## Required Output Format1. Situation snapshot.2. Recommended branch and rationale.3. Alternate/degraded branches with trigger thresholds.4. Decision authorities, timing gates, and escalation criteria.5. Staff actions (owner, suspense, and verification method).## Domain ProductsPrimary products: HAPS continuity matrix, mesh failover trigger ledger, commander comms branch brief.## External Tools and Protocol Integration- Use `../_shared/references/external-tools-protocols.md` and `../_shared/references/tool-protocol-playbooks.md`.- 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/stack entries in `../_shared/references/warfighter-external-tool-and-protocol-catalog.md`.## Domain Toolchain Defaults- Primary: `tool_suite_id=ts-near-space-haps-resilience-v1 with protocol_stack_id=ps-near-space-haps-resilience-stack-v1`.- Alternate: `tool_suite_id=ts-space-satcom-v1 with protocol_stack_id=ps-space-ground-failover-stack-v1`.- Degraded: authenticated voice/text branch with UTC event logs, cross-check witness, and delayed machine reconciliation.## Guardrails- Separate observed facts, assessed confidence, and unknowns.- If tool trust, authority, or data freshness is below threshold, 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 IDs: DPL-C2-DISP-002, DPL-SPECTRUM-REMEDIATION-002, DPL-SPACE-C2-LINK-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.

Frequently asked questions