chatgpt-lane
Skill1 starsChanged 4 days agoMITView on GitHub
Run a job on OpenAI GPT models through the Codex CLI (gpt-6.1-sol for execution, gpt-6-astra for second opinions, gpt-6-luna for bulk). Use when the user asks for GPT, Codex or ChatGPT, or when the orchestra routing table picks the GPT side. Needs the orchestra skill's scripts.
In this repository4 other files it gives its agents.
- councilSkill
- deepseek-laneSkill
- kimi-laneSkill
- orchestraSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Always pass -m. The CLI's own default may be an older model.
- Very specific: line 32
Follow the gates in the orchestra skill: status ok, re-run the check yourself, read the full diff (git -C ../wt-<task> diff), then merge …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ChatGPT lane (Codex CLI)
Models
| Model | Use | Effort |
| gpt-6.1-sol | Execution from a step-by-step brief | medium, high for hard work |
| gpt-6-astra | Second opinion, design critique, image generation | high |
| gpt-6-luna | Bulk and mechanical work | low |
Always pass -m. The CLI's own default may be an older model.
Run
git worktree add ../wt-<task> -b lane/<task>
../orchestra/scripts/mmo-run codex -m gpt-6.1-sol -e high --mode rw -C ../wt-<task> \
--brief brief.md --out out/<task>.md -t 1800
../orchestra/scripts/mmo-run codex -m gpt-6-astra -e high --mode ro --brief question.md --out out/astra.md--mode rouses the Codex read-only sandbox.--mode rwlets it edit inside the worktree only.- Several independent jobs: one worktree each, start them all, then wait.
After it finishes
Follow the gates in the orchestra skill: status ok, re-run the check yourself, read the full diff
(git -C ../wt-<task> diff), then merge and remove the worktree. On limit, move the job to the
kimi-lane or deepseek-lane; on auth, ask the user to run codex login.
Images
For README art and illustrations, ask gpt-6-astra to use its built-in image tool and save into the workspace
(--mode rw in a worktree, or -C a scratch folder). Spell out every label you want in quotes, then open the
file and check the spelling before you use it.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.