fleet-fleet-infrastructure — for Claude Code fleet-fleet-infrastructure, openfleet, community, for Claude Code, ide skills, devops_infrastructure_health(), ### 2. Agent Status, ### 3. Gateway, ### 4. IRC, NODE_OPTIONS="--max-old-space-size=4096"

v1.0.0
GitHub

このスキルについて

適した場面: Ideal for AI agents that need fleet infrastructure — devops domain knowledge. ローカライズされた概要: Advanced Vibe coding / Vibe Managing — AI-Native Project Lifecycle Orchestration # Fleet Infrastructure — DevOps Domain Knowledge The fleet runs on 6+ services. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

機能

Fleet Infrastructure — DevOps Domain Knowledge
Service Port What It Does Config
--------- ------ ------------- --------
Gateway (OpenArms) 18789 (WS), 9400 (HTTP) Agent sessions, heartbeats, MCP, CRONs Gateway config
Mission Control 8000 Tasks, agents, board memory, approvals Docker + env

# Core Topics

for Claude Code devops_infrastructure_health() ### 2. Agent Status ### 3. Gateway ### 4. IRC NODE_OPTIONS="--max-old-space-size=4096"
cyberpunk042 cyberpunk042
[0]
[0]
Updated: 4/9/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 10/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Quality floor passed for review
Review Score
10/11
Quality Score
52
Canonical Locale
en
Detected Body Locale
en

適した場面: Ideal for AI agents that need fleet infrastructure — devops domain knowledge. ローカライズされた概要: Advanced Vibe coding / Vibe Managing — AI-Native Project Lifecycle Orchestration # Fleet Infrastructure — DevOps Domain Knowledge The fleet runs on 6+ services. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

このスキルを使用する理由

推奨ポイント: fleet-fleet-infrastructure helps agents fleet infrastructure — devops domain knowledge. Advanced Vibe coding / Vibe Managing — AI-Native Project Lifecycle Orchestration # Fleet Infrastructure — DevOps Domain

おすすめ

適した場面: Ideal for AI agents that need fleet infrastructure — devops domain knowledge.

↓ 実現可能なユースケース for fleet-fleet-infrastructure

ユースケース: Applying Fleet Infrastructure — DevOps Domain Knowledge
ユースケース: Applying Service Port What It Does Config
ユースケース: Applying --------- ------ ------------- --------

! セキュリティと制限

  • 制約事項: When something breaks, you need to know what talks to what, what logs to check, and how to restart without losing state
  • 制約事項: Requires repository-specific context from the skill documentation
  • 制約事項: Works best when the underlying tools and dependencies are already configured

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is fleet-fleet-infrastructure?

適した場面: Ideal for AI agents that need fleet infrastructure — devops domain knowledge. ローカライズされた概要: Advanced Vibe coding / Vibe Managing — AI-Native Project Lifecycle Orchestration # Fleet Infrastructure — DevOps Domain Knowledge The fleet runs on 6+ services. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

How do I install fleet-fleet-infrastructure?

Run the command: npx killer-skills add cyberpunk042/openfleet/fleet-fleet-infrastructure. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for fleet-fleet-infrastructure?

Key use cases include: ユースケース: Applying Fleet Infrastructure — DevOps Domain Knowledge, ユースケース: Applying Service Port What It Does Config, ユースケース: Applying --------- ------ ------------- --------.

Which IDEs are compatible with fleet-fleet-infrastructure?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for fleet-fleet-infrastructure?

制約事項: When something breaks, you need to know what talks to what, what logs to check, and how to restart without losing state. 制約事項: Requires repository-specific context from the skill documentation. 制約事項: Works best when the underlying tools and dependencies are already configured.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add cyberpunk042/openfleet/fleet-fleet-infrastructure. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use fleet-fleet-infrastructure immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

fleet-fleet-infrastructure

Install fleet-fleet-infrastructure, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Fleet Infrastructure — DevOps Domain Knowledge

The fleet runs on 6+ services. When something breaks, you need to know what talks to what, what logs to check, and how to restart without losing state.

The Service Map

ServicePortWhat It DoesConfig
Gateway (OpenArms)18789 (WS), 9400 (HTTP)Agent sessions, heartbeats, MCP, CRONsGateway config
Mission Control8000Tasks, agents, board memory, approvalsDocker + env
MC Frontend3000Web dashboard for PODocker
LocalAI8090Local LLM inference, embeddingsAICP project
IRC (miniircd)6667Real-time agent communicationscripts/setup-irc.sh
The Lounge9000Web IRC client for POscripts/setup-lounge.sh
ntfyexternalPush notifications to PO mobile3 topics

How They Connect

PO → MC Frontend (3000) → MC Backend (8000) ← Orchestrator (30s cycle)
                                              ↓
Gateway (18789) ← Agent Sessions ← MCP Server ← fleet/mcp/tools.py
     ↓                                          ↓
IRC (6667) ← The Lounge (9000) ← PO       Events → Board Memory
     ↓                                          ↓
ntfy (external) → PO mobile                Plane (optional)

The orchestrator is the brain — it reads from MC, writes context files, dispatches tasks, wakes agents, monitors health. It runs as a daemon (fleet/cli/orchestrator.py), not as a service.

Health Check Protocol

When you call devops_infrastructure_health():

1. MC Backend

Check: curl -s http://localhost:8000/api/v1/agents
Healthy: returns JSON array of agents
Unhealthy: connection refused, timeout, or 5xx error

2. Agent Status

Check: count agents where status = "online"
Healthy: 10/10 online (or expected count)
Warning: <8 online (some offline)
Critical: <5 online (fleet degraded)

3. Gateway

Check: gateway process running (PID file or ps)
Healthy: process exists, WebSocket accepting connections
Unhealthy: process dead, OOM killed, config error

4. IRC

Check: nc -z localhost 6667
Healthy: port responding
Unhealthy: miniircd not running

Common Issues and Fixes

SymptomCauseFix
Gateway OOMToo many concurrent sessions, NODE_OPTIONS too lowIncrease heap: NODE_OPTIONS="--max-old-space-size=4096"
Agents stuck "provisioning"last_seen_at not set on provisionPatch: set last_seen_at when status=online
MC returns 500Database migration needed or Docker restartdocker compose restart mc-backend
IRC not connectingminiircd not startedscripts/setup-irc.sh
Heartbeats not firingGateway config stale or agent session prunedscripts/clean-gateway-config.sh
Orchestrator crashMissing import or configCheck fleet orchestrator logs

The Daemon Ecosystem

4 daemons run alongside the gateway:

DaemonIntervalWhat It Does
Orchestrator30s13-step brain cycle: context → dispatch → health
Sync60sBoard sync, Plane sync
Monitor300sBudget monitoring, storm detection
Auth120sOAuth token refresh

Start all: fleet daemon start Check: fleet daemon status Logs: fleet logs (combined) or fleet logs orchestrator

IaC Principle

Everything is scripted. No manual steps after checkout:

  • scripts/setup.sh — zero to running fleet
  • scripts/start-fleet.sh — gateway startup
  • scripts/setup-mc.sh — MC Docker setup
  • make status — fleet overview
  • make gateway — start gateway
  • make mc-up — start MC

When you fix an infrastructure issue, the fix goes in a script — not in a "run this command" instruction. The next setup.sh run should produce the same result.

関連スキル

Looking for an alternative to fleet-fleet-infrastructure or another community skill for your workflow? Explore these related open-source skills.

すべて表示

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

カスタマイズ可能なウィジェットプラグインをprompts.chatのフィードシステム用に生成する

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

React フレームワーク

★ 138.4k
⑂ 0
ブラウザ

pr-review

Logo of pytorch
pytorch

Pythonにおけるテンソルと動的ニューラルネットワーク（強力なGPUアクセラレーション）

★ 98.6k
⑂ 0
開発者