How do I install the Khala Fleet skill?

Run npx skillmds@latest add tuyv/khala-fleet 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 Khala Fleet safe to use?

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

Which AI agents work with Khala Fleet?

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 Khala Fleet free to use?

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

Who published Khala Fleet?

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

Khala Fleet by tuyv — Agent Skill

Name: Khala Fleet
Author: tuyv

Khala Fleet

Operate an OpenAgents Khala coding fleet safely. Use when the user asks to connect or list fleet accounts, spawn/delegate coding work to Codex or Claude workers, start/monitor/pause/drain/stop a sustained fleet run, burn down a backlog with parallel workers, verify fleet work actually completed, or diagnose dispatch failures like "0/1 available" or target_pylon_unavailable.

tuyv f0ad1b4 4 files · 6.7 KB Updated Sep 17, 2026

File contents

Khala Fleet Management

This is the canonical, repo-scope khala-fleet skill. It is a launcher, not the law: the authoritative procedure lives in this repo and wins whenever anything disagrees. Read these first, in full, every invocation:

The Khala -> Pylon -> Codex Coding Delegation Runbook section of AGENTS.md / CLAUDE.md at the repo root.
docs/khala-code/2026-07-02-khala-fleet-bundled-skill.md (how this skill is bundled, discovered at repo scope, and materialized into ~/.agents/skills/khala-fleet/ by Khala Code Desktop).
The fleet spec under specs/khala-fleet-delegate/ and the packages/khala-fleet-intents/ intents package.

Quick orientation while you open those:

Fleet = the owner's linked Codex/Claude accounts, each an ISOLATED local worker reached through Khala -> Pylon -> assignment.
Dispatch ladder: one bounded task (codex_spawn / $PYLON khala request --workflow codex_agent_task with pinned repo/commit/verify) → parallel wave (heartbeat capacity first, one claim per unit) → sustained fleet run (fleet_run_start / fleet_run_status / fleet_run_control).
Done = closeout checklist ok + exact token_usage_events rows. Counter movement alone is NEVER completion evidence.
Never run login flows against ~/.codex or the owner's live ~/.claude. worker auth uses isolated per-account homes only.

Frequently asked questions