Nanako0129

Pilotfish Grok — AI skill for Claude Code

AI community

Grok Build–native multi-model orchestration, inspired by pilotfish.

How to install Pilotfish Grok

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Nanako0129/pilotfish-grok and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Pilotfish Grok does

Grok Build–native multi-model orchestration, inspired by pilotfish. Frontier main session plans; role agents execute; verification guards quality.

Alternatives in AI

Agent Rules Books — AGENTS.md rules / skills for AI coding agents: Codex, Cursor & Claude Code 2.6k ★
Multi Execute — 执行 - 多模型协作执行 (Multi-Model Collaborative Execution) 1.9k ★
Pilotfish — Multi-model orchestration layer for Claude Code — the frontier model plans, cheaper models execute, verificati 688 ★

README

pilotfish-grok

Grok Build–native multi-model orchestration in the [pilotfish](https://github.com/Nanako0129/pilotfish) family — same idea, install surface under `~/.grok/`.

**pilotfish-grok** ports pilotfish orchestration to Grok Build. It keeps the separation between machine configuration, role bindings, and model-free policy, and maps lifecycle and capability boundaries onto Grok agents and roles. Quality comes from explicit approval gates and fresh-context verification—not from using the strongest model for every step.

Everything installs globally under `~/.grok/`: one setup for every project.

Related lines: [pilotfish](https://github.com/Nanako0129/pilotfish) (Claude Code) and [pilotfish-codex](https://github.com/miyago9267/pilotfish-codex) (Codex). Each host has its own release train; this repo does not install Claude’s `Explore` shadow — `scout` owns discovery.

[繁體中文](./README.zh-TW.md)

Why
How it works
Architecture
Lifecycle
Install
Trust & security
What gets installed
Dual harness with Claude pilotfish
Updating
Model routing
Limitations
Uninstall
Versioning
Research & design
License

Why

A coding session spends most tokens on search, mechanical edits, tests, and docs—not on architecture judgments. Pilotfish routes volume work to leaf roles and keeps planning, approval, and final judgment in the main session.

On Grok Build today, accounts may only expose a single frontier model. In that regime pilotfish-grok still helps by:

Protecting main-session context (recon and bulk work run in child sessions)
Tiering reasoning effort per role (low for recon/mechanical, higher for security)
Enforcing capability modes (read-only / `exe