Getting started
Skill claude-world/director-mode-lite/skills/getting-started
Guided five-minute onboarding for Director Mode Lite across Claude Code, Codex CLI, and Grok Build. Use after installation or when choosing a first workflow.From its SKILL.md
npx -y skills add claude-world/director-mode-lite --skill getting-startedAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- runs commandsInstructs the agent to run 3 commands, including `./scripts/verify-install.sh /path/to/project` and 2 more.
- fetches URLsInstructs the agent to fetch 1 URL, including https://claude-world.com.
SKILL.md
2.2 KB, 470 tokens by cl100k_base, as published. Nobody here has run it
Getting started
Director Mode is a set of adaptable workflows, not a permission or policy layer. Keep the user's preferred CLI controls and choose only the skills useful for the current task.
1. Verify the portable surfaces
./scripts/verify-install.sh /path/to/project
A full three-CLI install currently provides 35 skills, 14 canonical Claude
agents, 14 Codex adapters, 14 Grok adapters, shared guidance, and the session
relay. Python 3 is required for installation and relay packets. jq is only a
legacy automation dependency; a normal zero-hook install does not need it.
Active hooks are optional. The default install deliberately registers none.
Use --hooks guide only when a short non-blocking Claude/Codex SessionStart
context is useful. Grok reads the same guidance from AGENTS.md without an
inert passive hook.
2. Choose a starting point
director-mode: define outcome, context, constraints, evidence, and the next decision for substantial work.workflow: use the full research → plan → implement → verify → review flow.focus-problem: understand an unfamiliar bug or codebase area.session-relay: leave portable state for Claude, Codex, or Grok to continue.smart-commit: review and prepare a conventional commit when requested.
Testing and TDD skills are available when they fit the repository or the user asks for them; they are not imposed on every task.
3. Let another CLI continue
.director-mode/bin/director-relay create \
--from claude --to codex \
--goal "Finish the current feature" \
--summary "Implementation is partly complete" \
--next "Inspect the worktree and continue"
.director-mode/bin/director-relay continue --to codex
The second command prints a copyable native command. It launches nothing until
the user explicitly adds --run.
Help
agents: list available agent roles.skills: browse the skill catalog.docs/FAQ.md: installation and relay questions.- https://claude-world.com: tutorials and updates.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most project setup skills give in 470 tokens
Counted across 1,553 of the 3,091 authors here whose files we hold, read 2026-09-06
- Write the configuration filein 36 of 1553
- Create the directory structurein 35 of 1553, across 33 files
- Verify the setupin 31 of 1553, across 28 files
- Run the setup scriptin 30 of 1553, across 29 files
- Pre-determine the required sample sizein 29 of 1553, across 12 files
- Check if the configuration already existsin 29 of 1553
- Document every testin 26 of 1553, across 10 files
- Start with a hypothesisin 26 of 1553, across 11 files
- Ask one question at a timein 22 of 1553
- Test a single variable per testin 21 of 1553, across 9 files
- Read product marketing context before asking questionsin 19 of 1553, across 8 files
- Do not peek and stop earlyin 18 of 1553, across 7 files
Said here and by no other author read
- Verify the portable surfaces
- Choose a starting point
- Let another CLI continue
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.