Generate setup scripts and instructions for development environments across platforms. Use when: (1) Setting up new development machines (Python, Node.js, Docker, databases), (2) Creating automated setup scripts for team onboarding, (3) Need cross-platform setup instructions (macOS, Linux, Windows), (4) Installing development tools and dependencies, (5) Configuring version managers and package managers. Provides executable setup scripts, platform-specific guides, and tool installation instructions.
93
92%
Does it follow best practices?
Impact
90%
1.15xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Generate automated setup scripts and detailed instructions for development environments across multiple platforms.
Specify your requirements and get an automated setup script:
# Example: Python development environment
bash scripts/setup_python.sh
# Example: Node.js development environment
bash scripts/setup_nodejs.sh
# Example: Docker environment
bash scripts/setup_docker.shFor manual setup or understanding what the scripts do, see platform_instructions.md.
Goal: Set up complete development environment for a new developer
Approach:
Example Request: "Set up a Python and Node.js development environment on macOS"
Generated Output:
#!/usr/bin/env bash
# Complete Development Environment Setup
# Install Homebrew
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
# Install Git
brew install git
# Install Python via pyenv
brew install pyenv
pyenv install 3.11.0
pyenv global 3.11.0
# Install Node.js via nvm
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash
nvm install --lts
# Install Docker Desktop
echo "Please download Docker Desktop from https://www.docker.com/products/docker-desktop"
# Install VS Code
brew install --cask visual-studio-code
# Verify installations
git --version
python --version
node --versionGoal: Set up environment for a specific project with exact dependencies
Approach:
Example Request: "Create setup script for a Django project requiring Python 3.11 and PostgreSQL"
Generated Output:
#!/usr/bin/env bash
# Django Project Environment Setup
# Install Python 3.11
if ! command -v python3.11 &> /dev/null; then
# macOS
brew install python@3.11
# Linux: sudo apt-get install python3.11
fi
# Install PostgreSQL
brew install postgresql@15
brew services start postgresql@15
# Create virtual environment
python3.11 -m venv venv
source venv/bin/activate
# Install Django and dependencies
pip install django psycopg2-binary
# Create database
createdb myproject_dev
# Initialize Django project
django-admin startproject myproject .
echo "Setup complete! Activate venv: source venv/bin/activate"Goal: Replicate CI/CD environment locally
Approach:
Example Request: "Match my GitHub Actions environment locally (Ubuntu, Python 3.10, Node 18)"
Goal: Set up polyglot development environment
Approach:
Example Request: "Set up Python, Node.js, and Go development on Linux"
Use scripts/setup_python.sh:
Use scripts/setup_nodejs.sh:
Use scripts/setup_docker.sh:
See platform_instructions.md for:
See platform_instructions.md for:
See platform_instructions.md for:
See tool_guides.md for:
See tool_guides.md for:
See tool_guides.md for:
See tool_guides.md for:
Determine what needs to be installed:
Questions to ask:
- What programming languages? (Python, Node.js, Java, Go, etc.)
- What databases? (PostgreSQL, MySQL, MongoDB, Redis, etc.)
- What tools? (Docker, Git, editor, etc.)
- What platform? (macOS, Linux, Windows)
- Team-wide or personal setup?Option A: Automated Script
Option B: Manual Instructions
Option C: Hybrid
Based on requirements, generate:
Always include verification steps:
# Verify installations
echo "Verifying setup..."
git --version || echo "❌ Git not installed"
python3 --version || echo "❌ Python not installed"
node --version || echo "❌ Node.js not installed"
docker --version || echo "❌ Docker not installed"
echo "✅ Setup verification complete"Provide cleanup/uninstall steps if needed:
# Uninstall (if needed)
brew uninstall python@3.11
rm -rf venvScripts should be safe to run multiple times:
# Check before installing
if ! command -v python3 &> /dev/null; then
brew install python@3.11
else
echo "✅ Python already installed"
fiDetect OS and adapt:
detect_os() {
if [[ "$OSTYPE" == "darwin"* ]]; then
echo "macos"
elif [[ "$OSTYPE" == "linux-gnu"* ]]; then
echo "linux"
else
echo "unknown"
fi
}
OS=$(detect_os)Show what's happening:
echo "📦 Installing Python..."
brew install python@3.11
echo "✅ Python installed"set -e # Exit on error
# Or handle specific errors
if ! brew install python@3.11; then
echo "❌ Failed to install Python"
echo "Try installing manually from python.org"
exit 1
fiAdd comments explaining each step:
# Install Node.js via nvm (Node Version Manager)
# This allows managing multiple Node.js versions
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash# Python
python3 -m venv venv
source venv/bin/activate # macOS/Linux
# venv\Scripts\activate # Windows
# Node.js (using nvm)
nvm use 18check_installed() {
if command -v $1 &> /dev/null; then
echo "✅ $1 is installed"
return 0
else
echo "❌ $1 is not installed"
return 1
fi
}
check_installed git
check_installed python3
check_installed node# Add to ~/.bashrc or ~/.zshrc
cat >> ~/.bashrc << 'EOF'
export PATH="$HOME/.local/bin:$PATH"
export EDITOR=vim
EOF
source ~/.bashrc# macOS/Linux: Use sudo for system installations
sudo apt-get install package
# Avoid sudo for user-level tools
pip install --user package# Check PATH
echo $PATH
# Add to PATH (temporary)
export PATH="/usr/local/bin:$PATH"
# Add to PATH (permanent, in ~/.bashrc)
echo 'export PATH="/usr/local/bin:$PATH"' >> ~/.bashrc# Use version managers to avoid conflicts
pyenv install 3.11.0 # Python
nvm install 18.16.0 # Node.jsRequest: "Set up a full-stack JavaScript development environment on macOS"
Generated Script:
#!/usr/bin/env bash
# Full-Stack JavaScript Development Environment
# Platform: macOS
set -e
echo "🚀 Full-Stack JavaScript Setup"
echo "=============================="
# Install Homebrew
if ! command -v brew &> /dev/null; then
echo "📦 Installing Homebrew..."
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
fi
# Install Git
echo "📦 Installing Git..."
brew install git
# Install Node.js via nvm
echo "📦 Installing Node.js..."
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"
nvm install --lts
nvm use --lts
# Install global packages
echo "📦 Installing global packages..."
npm install -g pnpm typescript ts-node nodemon
# Install PostgreSQL
echo "📦 Installing PostgreSQL..."
brew install postgresql@15
brew services start postgresql@15
# Install Redis
echo "📦 Installing Redis..."
brew install redis
brew services start redis
# Install Docker Desktop
echo "📦 Docker Desktop..."
echo "Please download from https://www.docker.com/products/docker-desktop"
# Install VS Code
echo "📦 Installing VS Code..."
brew install --cask visual-studio-code
# Verify setup
echo ""
echo "✅ Setup Complete!"
echo ""
echo "Installed:"
echo " - Git: $(git --version)"
echo " - Node.js: $(node --version)"
echo " - npm: $(npm --version)"
echo " - pnpm: $(pnpm --version)"
echo " - TypeScript: $(tsc --version)"
echo " - PostgreSQL: $(postgres --version)"
echo " - Redis: $(redis-server --version)"0f00a4f
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.