Starlight SI
Use this skill for Codex-native /si behavior: lane selection, dispatch packet design, explicit fanout/council execution, and handoffs between Starlight agent wrappers.
When the local prompt shortcut is installed, /si expands into this skill. On mobile or remote ChatGPT surfaces where slash commands are unavailable, treat si: or starlight si at the start of a prompt as /si.
Operating Rules
- Read repo-local
AGENTS.md before editing or dispatching.
- Route first. Produce a compact lane recommendation or dispatch packet before running any cross-agent action.
- Do not launch fanout from hooks or ambient prompts. Fanout requires explicit wording such as
/si fanout, run fanout, dispatch, council, or smoke test.
- Keep default dispatch read-only unless Frank asks for implementation.
- Save or report receipts for any fanout/council run, including command, repo, lanes, and output path.
- For mobile prompts, keep output compact and command-ready. Mobile can steer the connected host, but local shell execution still happens on that host.
- If the request wants a swarm, route to the Starlight Swarm lane and require a coordinator, worker inputs, expected artifacts, stop conditions, evidence, and handoff format before execution.
Lane Defaults
- Codex: repo edits, tests, validation, installs, and implementation.
- Claude: long-form reasoning, docs, planning, and large context review.
- Grok: fast external critique, media routing, and alternate review.
- Antigravity: high-autonomy repo/task runs through existing Starlight wrappers.
- DeepAgent/OpenCode: specialized repo execution when already configured.
- Motion/image tools: visual, media, animation, or design-polish work.
Safe Commands
Prefer existing Starlight wrappers and scripts:
pwsh "$HOME\Starlight-Intelligence-System\scripts\si-dispatch.ps1" -Repo . -Task "<task>" -Json
pwsh "$HOME\Starlight-Intelligence-System\scripts\si-council.ps1" -Mode audit -Repo . -Json
Invoke-SiFanout -Task "<task>" -RepoKey sis -Lanes codex,grok -Json
Invoke-SiCouncil -Mode audit -RepoKey sis -Json
For a dry route without execution, return:
{
"intent": "audit|implement|design|research|deploy|ops",
"repo": "detected repo",
"lanes": ["codex"],
"readOnly": true,
"why": "short reason",
"nextCommand": "only if explicit dispatch was requested"
}
Verification
For implementation work, run local fast checks first. For Vercel-connected web apps, prefer preview verification before production promotion. Do not leave local dev servers running.
1---2name: starlight-si3description: Codex-native Starlight Intelligence /si router for choosing local agent lanes, building handoff packets, and running explicit read-only fanout or council dispatch across Codex, Claude, Grok, Antigravity, OpenCode, DeepAgent, and image tools. Use when prompts mention /si, the installed /si prompt shortcut, mobile alias si:, starlight si, route, dispatch, fanout, council, which agent/tool, local CLI lanes, or Starlight multi-agent orchestration.4---56# Starlight SI78Use this skill for Codex-native `/si` behavior: lane selection, dispatch packet design, explicit fanout/council execution, and handoffs between Starlight agent wrappers.910When the local prompt shortcut is installed, `/si` expands into this skill. On mobile or remote ChatGPT surfaces where slash commands are unavailable, treat `si:` or `starlight si` at the start of a prompt as `/si`.1112## Operating Rules13141. Read repo-local `AGENTS.md` before editing or dispatching.152. Route first. Produce a compact lane recommendation or dispatch packet before running any cross-agent action.163. Do not launch fanout from hooks or ambient prompts. Fanout requires explicit wording such as `/si fanout`, `run fanout`, `dispatch`, `council`, or `smoke test`.174. Keep default dispatch read-only unless Frank asks for implementation.185. Save or report receipts for any fanout/council run, including command, repo, lanes, and output path.196. For mobile prompts, keep output compact and command-ready. Mobile can steer the connected host, but local shell execution still happens on that host.207. If the request wants a swarm, route to the Starlight Swarm lane and require a coordinator, worker inputs, expected artifacts, stop conditions, evidence, and handoff format before execution.2122## Lane Defaults2324- Codex: repo edits, tests, validation, installs, and implementation.25- Claude: long-form reasoning, docs, planning, and large context review.26- Grok: fast external critique, media routing, and alternate review.27- Antigravity: high-autonomy repo/task runs through existing Starlight wrappers.28- DeepAgent/OpenCode: specialized repo execution when already configured.29- Motion/image tools: visual, media, animation, or design-polish work.3031## Safe Commands3233Prefer existing Starlight wrappers and scripts:3435```powershell36pwsh "$HOME\Starlight-Intelligence-System\scripts\si-dispatch.ps1" -Repo . -Task "<task>" -Json37pwsh "$HOME\Starlight-Intelligence-System\scripts\si-council.ps1" -Mode audit -Repo . -Json38Invoke-SiFanout -Task "<task>" -RepoKey sis -Lanes codex,grok -Json39Invoke-SiCouncil -Mode audit -RepoKey sis -Json40```4142For a dry route without execution, return:4344```json45{46 "intent": "audit|implement|design|research|deploy|ops",47 "repo": "detected repo",48 "lanes": ["codex"],49 "readOnly": true,50 "why": "short reason",51 "nextCommand": "only if explicit dispatch was requested"52}53```5455## Verification5657For implementation work, run local fast checks first. For Vercel-connected web apps, prefer preview verification before production promotion. Do not leave local dev servers running.
frankxai