mpbt-hq/starfleetctl / fragments/starfleet-skills/starfleet
starfleet
VerifiedFleet coordination core — comms, board status, concurrency/isolation, and pointers to the themed starfleet-* skills. Load when handling inter-ship messages, checking the board, or unsure which starfleet skill applies.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.3 KB |
| reference.md | markdown | 1.6 KB |
SKILL.md
View on GitHub---
name: starfleet
description: "Fleet coordination core — comms, board status, concurrency/isolation, and pointers to the themed starfleet-* skills. Load when handling inter-ship messages, checking the board, or unsure which starfleet skill applies."
---
# starfleet — fleet coordination core
Fleet-wide coordination for concurrent AI-agent sessions ("ships"). This is the **core**
skill: comms, the board, and concurrency/isolation. Thematic sub-skills cover the rest —
see [Routing](#routing) below for which one to load when.
## Inter-ship communication (comms)
Ships communicate via `starfleetctl comms`. Messages arrive automatically via system prompt
injection — **never call `comms inbox` manually** (the poller already injects unseen messages).
### Comms rules
1. **Always answer.** When a `tell` or `ask` arrives, reply via `starfleetctl comms tell <sender>`.
Silence means the message was lost.
2. **Ack after responding.** `starfleetctl comms ack <id>` to clear from inbox.
3. **Comms questions → answer in two places:** via `comms tell` (so sender gets it) AND on the
local console (so the human can see it).
4. **Keep the board current.** Set status after starting or finishing work.
5. **Never call `comms --help`.** The full interface lives in this skill and the
`starfleetctl` reference.
### Key comms subcommands
| Command | Purpose |
|---|---|
| `comms tell <ship> "<msg>"` | Send a directive to a ship |
| `comms tell <ship> --stdin` | Send a large payload via stdin (`<<'EOF'` heredoc) |
⚠️ **Gocha**: `comms tell <ship> -F - <<EOF` is **NOT** a thing — there is no `-F`
flag. `-F` (and `-`) become part of the message text, and the heredoc on stdin is
ignored, so the receiver gets a message that literally contains `-F -`. For any
multi-line body always use `comms tell <ship> --stdin <<'EOF' ... EOF` (or the
`--attach <file>` form for very large payloads). Same for `broadcast`.
| `comms broadcast "<msg>"` | Send to all ships |
| `comms ask "<question>"` | Ask a question (async reply expected) |
| `comms ack <id>` | Acknowledge/remove a message from inbox |
| `comms board` | Show fleet status board |
| `comms board --json` | Machine-readable board (for scripts) |
| `comms status <status>` | Set own status (idle/working/blocked) |
## Concurrency / isolation
Ships must not work in the same git working tree simultaneously. Use separate clones
or worktrees. PR-branch ownership: every clone pushes to the **same GitHub PR branch** —
use `starfleetctl github pr claim` before mutating a PR.
### Key rules
- **Different working trees cannot clobber each other.** Parallelize across independent workspaces.
- **The hazard:** two actors mutating the **same** clone at once.
- **PR-branch ownership:** Use `starfleetctl github pr claim` before mutating a PR.
## Routing
| Skill | Load when |
|---|---|
| **`starfleet-tasks`** | capturing/working/managing tasks, dashboard topics, reports |
| **`starfleet-github`** | PR status/CI, PR claims, submitting/repairing PRs, backports |
| **`starfleet-timer`** | setting/listing/canceling timers (polling instead of watch-loops) |
| **`starfleet-sessions`** | spawning/managing ships, git worktrees, web console |
## Starfleetctl CLI
A Go CLI for fleet coordination. Bootstrap: `./starfleet-bootstrap` (updates `.starfleet-ai/`).
Full command reference: **`reference.md`** in this skill's directory.Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |