agentleFS
furkandvrcfurkandvrc/conductor/skills/setup/SKILL.md

setup

Skill4 starsChanged 32 days agoMITView on GitHub

First-run setup and health check for the Conductor plugin in Claude Code or Codex. Detect which worker CLIs are installed, add OpenAI-compatible endpoints, choose the orchestrator, start the dashboard and the optional Pixel Agents office, and fix what is missing. Use on "set up conductor", "conductor doesn't work", "configure workers", "add a local model", "conductor kurulum", "worker'ları ayarla".

  • Pipes a download into a shell
  • Reads credentials
  • Installs packages

191 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use add-voice-transcription, add-discord and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • juancruzmunozalbeloSkill

    add-voice-transcription

    Add voice message transcription to NanoClaw using OpenAI's Whisper API. Automatically transcribes WhatsApp voice notes so the agent can read and respond to them.

    Also in 5 projects that use this

  • MicrosoftSkill

    add-discord

    Add Discord bot channel integration via Chat SDK.

    Also in 11 projects that use this

  • MicrosoftSkill

    add-slack

    Add Slack channel integration via Chat SDK.

    Also in 11 projects that use this

  • juancruzmunozalbeloSkill

    add-telegram-swarm

    Add Agent Swarm (Teams) support to Telegram. Each subagent gets its own bot identity in the group. Requires Telegram channel to be set up first (use /add-telegram). Triggers on "agent swarm", "agent teams telegram", "telegram swarm", "bot pool".

    Also in 7 projects that use this

  • +8 more from microsoft

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 168 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Requirements: Check that node (version 18 or later), python3, curl and bash are on PATH.

    line 11
  2. Very specific:

    Workers: Run delegate status. In Codex, use the full path to bin/delegate printed at session start.

    line 14
  3. Very specific:

    Dashboard and office: Run conductor-panel start and give the user http://127.0.0.1:4747.

    line 52
  4. Very specific:

    Smoke test: Run one cheap read-only task on an available worker, for example delegate <worker> "In one sentence, what does README.md …

    line 56

“Common” is measured: kept by at least 6 in 10 of the 168 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Conductor setup

Work through these steps in order. Report a short checklist to the user at the end. Install nothing, and never touch credentials, without the user's go-ahead.

  1. Requirements. Check that node (version 18 or later), python3, curl and bash are on PATH. Report anything missing with the install command for the user's OS.
  2. Workers. Run delegate status. In Codex, use the full path to bin/delegate printed at session start. You only need one worker; the rest are optional.

    WorkerInstallSign in
    claudenpm install -g @anthropic-ai/claude-codeclaude
    codexnpm install -g @openai/codexcodex login
    gemini (Antigravity)https://antigravity.googleagy
    cursorcurl https://cursor.com/install -fsS | bashcursor-agent login
    copilotnpm install -g @github/copilotcopilot, then /login
    gemini-clinpm install -g @google/gemini-cliGEMINI_API_KEY
    opencodenpm install -g opencode-aiopencode auth login
    qwennpm install -g @qwen-code/qwen-codefirst run

    Sign-ins are interactive, so the user must run them. In Claude Code, suggest the ! <command> prefix. A worker that is installed but signed out fails at run time; it shows "last run failed" in delegate list.

  3. Endpoints (optional). For any OpenAI-compatible API (Ollama, LM Studio, vLLM, llama.cpp server, OpenRouter…), send the user to the dashboard: Workers → Add an endpoint. They can add as many as they like, each with its own key and model. Never ask for API keys in the chat.
  4. Custom CLIs (optional). To add another headless CLI, the user adds it to ~/.config/conductor/workers.json under custom. Arguments are substituted per argv item, never through a shell:

    { "custom": [ { "id": "aider", "label": "Aider", "cmd": "aider",
        "args": ["--message", "{prompt}", "--model", "{model}"],
        "readArgs": ["--dry-run"], "writeArgs": ["--yes-always", "--no-auto-commits"],
        "goodAt": "small, precise edits" } ] }
  5. Orchestrator. On the dashboard, open Settings → Orchestrator. There the user can install Conductor into Claude Code and/or Codex (one click each) and choose who orchestrates; "Automatic" detects it per session. The orchestrator never delegates to itself. In Codex, the user must approve the plugin's hook once when Codex asks.
  6. Dashboard and office. Run conductor-panel start and give the user http://127.0.0.1:4747. The Office page needs npm install -g pixel-agents. Pixel Agents' own hook approval is for the user to give in its UI.
  7. Smoke test. Run one cheap read-only task on an available worker, for example delegate <worker> "In one sentence, what does README.md describe?". Confirm that it appears on the Tasks page.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.