Skip to content
Agentmart
Submit a tool

fleet-healer

Invariance layer — spawns background agents that automatically heal broken fleet communication channels until all reach ideal state

Skill by supportersimulator

IndexedMIT★ 2
Write a review

Chalk Labs

Need help deploying fleet-healer?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/supportersimulator-fleet-healer

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Invariance layer — spawns background agents that automatically heal broken fleet communication channels until all reach ideal state

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/fleet-healer

What's inside

Skill name
fleet-healer
Description
Invariance layer — spawns background agents that automatically heal broken fleet communication channels until all reach ideal state
License
MIT
Instructions
185 lines in SKILL.md · view on GitHub

Before installing

  • Instructions call the network
  • Instructions read files in your home folder (~/.ssh, ~/.aws…)

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Fleet Healer

The invariance layer for fleet communication. When channels degrade, healing agents spawn in the background — invisible to the user — and work autonomously to restore all channels to ideal state. The only acceptable steady state is **all channels working on all nodes**.

## When to Spawn Healing Agents

| Trigger | Source | Urgency |
|---------|--------|---------|
| `send_with_fallback()` falls through to P3+ | Delivery system | High — message used non-ideal channel |
| Watchdog detects stale peer (>90s heartbeat age) | Watchdog monitor | Medium — peer may be unreachable |
| Session start with degraded fleet health | Session init | Medium — inherited problem |
| `repair_with_escalation()` reaches L3+ | Repair system | High — lower levels failed |

## What Healing Agents Do

Each agent runs in the background via the Agent tool with `run_in_background=true`. They are invisible to the user and report results to `/tmp/atlas-agent-results/`.

### Channel Diagnoser

Probes all 8 channels to each peer, reports which work and why others fail.

```python
# Spawn a channel diagnoser for a specific peer
Agent(
    prompt="""Diagnose all fleet channels to peer 'mac1':
    1. Check NATS: python3 tools/fleet_nerve_nats.py ping mac1
    2. Check HTTP direct: curl -sf http://<mac1-ip>:8855/health
    3. Check HTTP tunnel: curl -sf http://127.0.0.1:<tunnel-port>/health
    4. Check SSH: ssh -o ConnectTimeout=5 <mac1-user>@<mac1-ip> echo ok
    5. Check seed file: ls -la .fleet-messages/mac1/
    Write results to /tmp/atlas-agent-results/heal-diagnose-mac1-$(date +%s).json""",
    run_in_background=True
)
```

### Daemon Restarter

If the target daemon is down, sends restart instructions via SSH seed.

```python
Agent(
    prompt="""Fleet daemon on 'mac3' is not responding.
    1. SSH in: ssh <mac3-user>@<mac3-ip> "pgrep -f fleet_nerve || echo DEAD"
    2. If dead, restart: ssh <mac3-user>@<mac3-ip> "launchctl kickstart -k gui/$(id -u)/com.multifleet.nerve"
    3. Wait 10s, verify: curl -sf http://<mac3-ip>:8855/health
    4. Write result to /tmp/atlas-agent-results/heal-daemon-mac3-$(date +%s).json""",
    run_in_background=True
)
```

### Tunnel Establisher

If direct HTTP fails, checks and creates SSH tunnels.

```python
Agent(
    prompt="""Direct HTTP to 'mac1' is failing. Establish SSH tunnel.
    1. Check existing tunnel: pgrep -f "ssh.*-L.*8856.*mac1"
    2. If none, create: ssh -f -N -L 8856:<mac1-ip>:8855 <mac1-user>@<mac1-ip>
    3. Verify tunnel: curl -sf http://127.0.0.1:8856/health
    4. If tunnel also fails, check if SSH itself works: ssh -o ConnectTimeout=5 <mac1-user>@<mac1-ip> echo ok
    5. Write result to /tmp/atlas-agent-results/heal-tunnel-mac1-$(date +%s).json""",
    run_in_background=True
)
```

### Config Updater

Detects IP changes and updates config (e.g., mac2 `.254` to `.196`).

```python
Agent(
    prompt="""Peer 'mac2' is unreachable at configured IP.
    1. Read current config: cat .multifleet/config.json | python3 -c "import sys,json; c=json.load(sys.stdin); print(c['peers']['mac2'])"
    2. Scan local network for mac2: arp -a | grep -i <mac2-mac-address>
    3. If new IP found, update config.json with new IP
    4. Re-probe: curl -sf http://<new-ip>:8855/health
    5. Write result to /tmp/atlas-agent-results/heal-config-mac2-$(date +%s).json""",
    run_in_background=True
)
```

### NATS Reconnector

If NATS peers are stale, attempts reconnect or tunnel restart.

```python
Agent(
    prompt="""NATS connectivity to 'mac3' is stale.
    1. Check local NATS: nats server check connection
    2. Check NATS routes: nats server report jetstream 2>/dev/null || nats server report connections
    3. If no route to mac3, check if NATS tunnel is alive: pgrep -f "ssh.*4222.*mac3"
    4. If tunnel dead, restart: ssh -f -N -L 4223:<mac3-ip>:4222 <mac3-user>@<mac3-ip>
    5. Verify: python3 tools/fleet_nerve_nats.py ping mac3
    6. Write result to /tmp/atlas-agent-results/heal-nats-mac3-$(date +%s).json""",
    run_in_background=True
)
```

## Healing Loop

The healing loop runs until convergence or escalation. Each iteration is a background agent.

```
while not all_channels_ideal():
  diagnose() -> identify broken channels per peer
  for each broken channel:
    spawn appropriate healer agent (background)
    wait(30s)
    re-probe channel
  if improved: log success, continue checking remaining
  if stuck after 3 attempts: escalate to human via seed file
```

### Practical Implementation

```python
# Master healer agent — orchestrates the loop
Agent(

From supportersimulator/multi-fleet, MIT.

More from supportersimulator/multi-fleet

Signals

Stars
2
Forks
0
Open issues
0
Last commit (this folder)
Apr 5, 2026 (7 months ago)
Last release
Apr 18, 2026 (6 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from supportersimulator

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get fleet-healer running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying fleet-healer?

CallGet help
Cite this page

fleet-healer skill. Agent Mart. https://agentmart.dev/skills/supportersimulator-fleet-healer (last updated 2026-10-24)