Antigravity-awesome-skills conductor-setup
Configure a Rails project to work with Conductor (parallel coding agents)
install
source · Clone the upstream repo
git clone https://github.com/sickn33/antigravity-awesome-skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/sickn33/antigravity-awesome-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/plugins/antigravity-awesome-skills-claude/skills/conductor-setup" ~/.claude/skills/sickn33-antigravity-awesome-skills-conductor-setup && rm -rf "$T"
manifest:
plugins/antigravity-awesome-skills-claude/skills/conductor-setup/SKILL.mdsafety · automated scan (low risk)
This is a pattern-based risk scan, not a security review. Our crawler flagged:
- references .env files
Always read a skill's source content before installing. Patterns alone don't mean the skill is malicious — but they warrant attention.
source content
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
, andbin/conductor-setup
scaffolding for a Rails repo.script/server
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
directory if it doesn't exist.script/
Verification
After creating the files:
- Confirm all Conductor files exist and scripts are executable
- Run
to verify it starts without errorsscript/server - Check that Rails configs properly reference
orENV['REDIS_URL']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.