fleet-status
Quick fleet health check — who's online, who's idle, what's everyone working on
Skill by supportersimulator
Chalk Labs
Need help deploying fleet-status?
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.
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-status
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.
About
Reviews
Write a reviewNo 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-status
What's inside
- Skill name
fleet-status- Description
- Quick fleet health check — who's online, who's idle, what's everyone working on
- License
- MIT
- Instructions
- 232 lines in SKILL.md · view on GitHub
Before installing
- Instructions call the network
Files (1)
- SKILL.md
SKILL.md (first lines)
# Fleet Status
Instant situational awareness of the entire fleet. One command shows every node's state, active sessions, running tasks, and connectivity health.
## How It Works
1. Your local daemon collects UDP heartbeats from all peers (every 10s)
2. Heartbeats carry node status, git branch, session count, and task state
3. `/fleet/live` merges local state + cached heartbeats into a unified view
4. If a heartbeat is stale (>60s), the daemon does a 1s HTTP probe as fallback
## Quick Check
```bash
# One-liner summary — the most useful command in the fleet
curl -s http://127.0.0.1:8855/fleet/live | python3 -c "import sys,json;print(json.load(sys.stdin)['fleetStatus'])"
# -> "3/3 online: mac1 active, mac2 idle 5m, mac3 working"
# Full node details (JSON)
curl -s http://127.0.0.1:8855/fleet/live | python3 -m json.tool
# This node only
curl -s http://127.0.0.1:8855/health | python3 -m json.tool
# Peer registry with heartbeat timestamps
curl -s http://127.0.0.1:8855/peers | python3 -m json.tool
```
### Via the fleet status script
```bash
bash scripts/multi-fleet-status.sh
```
### Via Python
```python
import requests, json
def fleet_status():
"""Get fleet-wide status from local daemon."""
try:
r = requests.get("http://127.0.0.1:8855/fleet/live", timeout=3)
data = r.json()
print(data["fleetStatus"])
for node in data.get("nodes", []):
name = node["name"]
status = node["status"]
idle = node.get("idle_s", 0)
tasks = node.get("activeTasks", 0)
branch = node.get("git", {}).get("branch", "?")
print(f" {name}: {status} | idle {idle}s | tasks {tasks} | {branch}")
return data
except requests.ConnectionError:
print("ERROR: Fleet Nerve daemon not running on localhost:8855")
return None
```
## Status Classifications
| Status | Meaning | Condition |
|--------|---------|-----------|
| `working` | Has active fleet tasks running | activeTasks > 0 |
| `active` | Session recently active | idle_s < 300 (5 min) |
| `idle Nm` | Session quiet for N minutes | 300 <= idle_s < 900 |
| `dormant Nm` | Session quiet for N+ minutes | idle_s >= 900 (15 min) |
| `offline` | No heartbeat received | No UDP heartbeat in 60s AND HTTP probe fails |
## Full Response Format
```json
{
"fleetStatus": "3/3 online: mac1 active, mac2 idle 5m, mac3 working",
"timestamp": "2026-04-05T10:30:00Z",
"nodes": [
{
"name": "mac1",
"role": "chief",
"status": "active",
"idle_s": 42,
"activeSessions": 1,
"activeTasks": 0,
"git": {
"branch": "main",
"lastCommit": "abc1234",
"lastCommitMsg": "feat: fleet worker pool"
},
"surgeons": {
"cardiologist": true,
"neurologist": true,
"atlas": true
},
"heartbeat": {
"lastSeen": "2026-04-05T10:29:58Z",
"transport": "udp",
"stale": false
}
},
{
"name": "mac2",
"role": "worker",
"status": "idle 5m",
"idle_s": 312,
"activeSessions": 1,
"activeTasks": 0,
"git": {
"branch": "feature/auth",
"lastCommit": "def5678"
}
},
{
"name": "mac3",
"role": "worker",
"status": "working",
"idle_s": 5,
"activeSessions": 2,
"activeTasks": 1,
"taskSummary": "Running cross-exam on auth module (45s)"
}From supportersimulator/multi-fleet, MIT.
More from supportersimulator/multi-fleet
- 0.440score
fleet-rebuttal
supportersimulator
Cross-machine rebuttal protocol — the 4-phase cycle where machines produce verdicts, critique each other, and converge on a chief decision
SkillDFreshness: D★ 2Claude Code +9 - 0.440score
fleet-race
supportersimulator
Competitive branch racing — 3 machines solve the same problem in isolated worktrees, then propose/rebut/converge to the strongest solution
SkillDFreshness: D★ 2Claude Code +9 - 0.440score
fleet-healer
supportersimulator
Invariance layer — spawns background agents that automatically heal broken fleet communication channels until all reach ideal state
SkillDFreshness: D★ 2Claude Code +9 - 0.436score
fleet-dispatch
supportersimulator
Remote worker dispatch — send tasks to fleet nodes and track results with priority routing
SkillDFreshness: D★ 2Claude Code +9 - 0.436score
fleet-repair
supportersimulator
4-level repair escalation for broken fleet channels — notify, guide, assist, remote
SkillDFreshness: D★ 2Claude Code +9 - 0.436score
fleet-chain
supportersimulator
Chain orchestration — multi-step task dependencies across fleet nodes with automatic sequencing
SkillDFreshness: D★ 2Claude Code +9 - 0.436score
fleet-check
supportersimulator
Run the full 7-channel communication test — verifies every delivery path to a target node
SkillDFreshness: D★ 2Claude Code +9 - 0.436score
fleet-idle
supportersimulator
Productive idle protocol — automatic work discovery and suggestion when fleet nodes are idle
SkillDFreshness: D★ 2Claude Code +9 - 0.436score
fleet-liaison
supportersimulator
Interact with the fleet liaison agent — check status, read batched messages, escalate outbound, pause/resume monitoring
SkillDFreshness: D★ 2Claude Code +9 - 0.436score
fleet-onboard
supportersimulator
Run the fleet onboarding wizard — checks what's configured, what's missing, and guides new users through setup
SkillDFreshness: D★ 2Claude Code +9 - 0.436score
fleet-security
supportersimulator
HMAC message signing, replay prevention, peer validation, and session gold sanitization
SkillDFreshness: D★ 2Claude Code +9 - 0.436score
fleet-send
supportersimulator
Send a message to another machine in the fleet — context, task, alert, or broadcast with 7-priority fallback delivery
SkillDFreshness: D★ 2Claude Code +9
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
- Source
- GitHubgithub-graphql
More from supportersimulator
- 0.440score
fleet-healer
supportersimulator
Invariance layer — spawns background agents that automatically heal broken fleet communication channels until all reach ideal state
SkillDFreshness: D★ 2Claude Code +9 - 0.440score
fleet-rebuttal
supportersimulator
Cross-machine rebuttal protocol — the 4-phase cycle where machines produce verdicts, critique each other, and converge on a chief decision
SkillDFreshness: D★ 2Claude Code +9 - 0.440score
fleet-race
supportersimulator
Competitive branch racing — 3 machines solve the same problem in isolated worktrees, then propose/rebut/converge to the strongest solution
SkillDFreshness: D★ 2Claude Code +9 - 0.436score
fleet-check
supportersimulator
Run the full 7-channel communication test — verifies every delivery path to a target node
SkillDFreshness: D★ 2Claude Code +9 - 0.436score
fleet-dispatch
supportersimulator
Remote worker dispatch — send tasks to fleet nodes and track results with priority routing
SkillDFreshness: D★ 2Claude Code +9 - 0.436score
fleet-chain
supportersimulator
Chain orchestration — multi-step task dependencies across fleet nodes with automatic sequencing
SkillDFreshness: D★ 2Claude Code +9
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-status 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.
Cite this page
fleet-status skill. Agent Mart. https://agentmart.dev/skills/supportersimulator-fleet-status (last updated 2026-10-24)