agentleFS
lgzarturolgzarturo/codeconductor/.agents/skills/conductor-setup/SKILL.md

conductor-setup

Skill0 starsChanged 26 days agoMITView on GitHub

Configure a Rails project to work with Conductor (parallel coding agents)

  • Reads credentials
  • Installs packages

11 other projects use a version of this, 3 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use conductor-review.

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.
  • airclearSkill

    conductor-review

    Acts as a Principal Software Engineer and Code Review Architect to review completed or in-progress work against project standards, style guides, and the implementation plan. Use when the user wants a quality check on their code or before finalizing a track.

    Also in 4 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. 0 are common, 9 are distinctive, and 7 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 7

    Very specific

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

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

    Create conductor.json in the project root if it doesn't already exist:

    line 24
  2. Very specific:

    Create bin/conductor-setup if it doesn't already exist:

    line 37
  3. Very specific:

    Create the script directory if needed, then create script/server if it doesn't already exist:

    line 58
  4. Distinctive:

    If this file exists and configures Redis, update it to use:

    line 84
  5. Distinctive:

    If this file exists, update the development adapter to use:

    line 90
  6. Distinctive:

    If this file configures Redis for caching, update to use:

    line 98
  7. Distinctive:

    If this file exists and configures a Redis cache store, update to use:

    line 104
  8. Very specific:

    Don't overwrite existing files: Check if conductor.json, bin/conductor-setup, and script/server exist before creating them.

    line 111
  9. Distinctive:

    Rails config updates: Only modify Redis-related configuration.

    line 112
  10. Very specific:

    Create directories as needed: Create script/ directory if it doesn't exist.

    line 113
  11. Distinctive:

    After creating the files:

    line 117
  12. Very specific:

    Run script/server to verify it starts without errors

    line 119
  13. Very specific:

    Check that Rails configs properly reference ENV['REDIS_URL'] or ENV.fetch('REDIS_URL', ...)

    line 120
  14. Distinctive:

    Use this skill only when the task clearly matches the scope described above.

    line 123
  15. Distinctive:

    Do not treat the output as a substitute for environment-specific validation, testing, or expert review.

    line 124
  16. Distinctive:

    Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

    line 125

“Common” is measured: kept by at least 6 in 10 of the 11 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

Set up this Rails project for Conductor, the Mac app for parallel coding agents.

When to Use

  • You need to configure a Rails project so it runs correctly inside Conductor workspaces.
  • The project should support parallel coding agents with isolated ports, Redis settings, and shared secrets.
  • You want the standard conductor.json, bin/conductor-setup, and script/server scaffolding for a Rails repo.

What to Create

1. conductor.json (project root)

Create conductor.json in the project root if it doesn't already exist:

{
  "scripts": {
    "setup": "bin/conductor-setup",
    "run": "script/server"
  }
}

2. bin/conductor-setup (executable)

Create bin/conductor-setup if it doesn't already exist:

#!/bin/bash
set -e

# Symlink .env from repo root (where secrets live, outside worktrees)
[ -f "$CONDUCTOR_ROOT_PATH/.env" ] && ln -sf "$CONDUCTOR_ROOT_PATH/.env" .env

# Symlink Rails master key
[ -f "$CONDUCTOR_ROOT_PATH/config/master.key" ] && ln -sf "$CONDUCTOR_ROOT_PATH/config/master.key" config/master.key

# Install dependencies
bundle install
npm install

Make it executable with chmod +x bin/conductor-setup.

3. script/server (executable)

Create the script directory if needed, then create script/server if it doesn't already exist:

#!/bin/bash

# === Port Configuration ===
export PORT=${CONDUCTOR_PORT:-3000}
export VITE_RUBY_PORT=$((PORT + 1000))

# === Redis Isolation ===
if [ -n "$CONDUCTOR_WORKSPACE_NAME" ]; then
  HASH=$(printf '%s' "$CONDUCTOR_WORKSPACE_NAME" | cksum | cut -d' ' -f1)
  REDIS_DB=$((HASH % 16))
  export REDIS_URL="redis://localhost:6379/${REDIS_DB}"
fi

exec bin/dev

Make it executable with chmod +x script/server.

4. Update Rails Config Files

For each of the following files, if they exist and contain Redis configuration, update them to use ENV.fetch('REDIS_URL', ...) or ENV['REDIS_URL'] with a fallback:

config/initializers/sidekiq.rb

If this file exists and configures Redis, update it to use:

redis_url = ENV.fetch('REDIS_URL', 'redis://localhost:6379/0')

config/cable.yml

If this file exists, update the development adapter to use:

development:
  adapter: redis
  url: <%= ENV.fetch('REDIS_URL', 'redis://localhost:6379/1') %>

config/environments/development.rb

If this file configures Redis for caching, update to use:

config.cache_store = :redis_cache_store, { url: ENV.fetch('REDIS_URL', 'redis://localhost:6379/0') }

config/initializers/rack_attack.rb

If this file exists and configures a Redis cache store, update to use:

Rack::Attack.cache.store = ActiveSupport::Cache::RedisCacheStore.new(url: ENV.fetch('REDIS_URL', 'redis://localhost:6379/0'))

Implementation Notes

  • Don't overwrite existing files: Check if conductor.json, bin/conductor-setup, and script/server exist before creating them. If they exist, skip creation and inform the user.
  • Rails config updates: Only modify Redis-related configuration. If a file doesn't exist or doesn't use Redis, skip it gracefully.
  • Create directories as needed: Create script/ directory if it doesn't exist.

Verification

After creating the files:

  1. Confirm all Conductor files exist and scripts are executable
  2. Run script/server to verify it starts without errors
  3. Check that Rails configs properly reference ENV['REDIS_URL'] or ENV.fetch('REDIS_URL', ...)

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

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.