delegate-setup
Configure delegation fleet lanes: which implementer CLI handles which kind of work, with optional model and effort (or variant) dials. Discovers installed CLIs, proposes a lane map for user approval, and writes global or project config only after explicit yes. Use when the user asks to set up, configure, or reconfigure delegation lanes, a fleet of lanes, or which implementer handles feature/tests/ui work — not for dispatching a coding task to an implementer.
npx skills add amElnagdy/delegate-skills --skill delegate-setup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Delegate Setup You are the **orchestrator** in **setup mode**. Discover installed implementer CLIs, propose a **fleet of lanes**, and write configuration only after the user approves. This skill does **not** dispatch coding work. It only authors the lane map. One concept: **lanes**. Never say “routes.” Example lane: **feature** → implementer `opencode`, model `opencode/grok`, variant `high` (OpenCode uses `variant` for reasoning intensity, not `effort`). ## When NOT to use this - The user wants a task implemented — use the matching `*-delegate` skill instead. - A one-off model change on a single dispatch — pass `--model` / `--effort` / `--variant` on that relay. ## Hard rules 1. Every lane **must** include `implementer`. 2. Put dials on the same object (`model`, `effort` or `variant`, …) only if that implementer supports them — see [references/schema.md](references/schema.md). 3. Show a human-readable lane table **and** the full JSON before every write; re-show after every tweak. 4. Write **only** after an explicit approval (“yes”, “approve”, “write it”). 5. Ask scope unless already clear: **global** (all projects) vs **this repo only**. Never create a project file just because c
- When NOT to use this
- Hard rules
- Flow
- 1. Discover
- 2. Load existing (effective map)
- 3. Propose
- 4. Scope
- 5. Approve and write
- 6. Ready to delegate
- Reconfigure
node "<skill-dir>/scripts/discover.mjs" node "<skill-dir>/scripts/config.mjs" load --cwd "$PWD" node "<skill-dir>/scripts/config.mjs" validate "<lanes-json>" node "<skill-dir>/scripts/config.mjs" write --scope global "<lanes-json>"
What does the delegate-setup skill do?
Configure delegation fleet lanes: which implementer CLI handles which kind of work, with optional model and effort (or variant) dials. Discovers installed CLIs, proposes a lane map for user approval, and writes global or project config only after explicit yes. Use when the user asks to set up, configure, or reconfigure delegation lanes, a fleet of lanes, or which implementer handles feature/tests/ui work — not for dispatching a coding task to an implementer.
How do I install it?
Run `npx skills add amElnagdy/delegate-skills --skill delegate-setup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From amElnagdy/delegate-skills, a repository with 684 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.