$npx -y skills add rudderlabs/rudder-agent-skills --skill rudder-environment-checkChecks RudderStack tool prerequisites and reports status. Use when checking prerequisites, setup status, what tools are missing, or before running RudderStack workflows for the first time
| 1 | # RudderStack Environment Check |
| 2 | |
| 3 | Quick diagnostic that checks all RudderStack tool prerequisites and provides actionable guidance. |
| 4 | |
| 5 | ## When to Use |
| 6 | |
| 7 | - Before starting with RudderStack workflows |
| 8 | - When troubleshooting "command not found" errors |
| 9 | - To verify your development environment is ready |
| 10 | |
| 11 | ## Check Process |
| 12 | |
| 13 | Run these checks in sequence: |
| 14 | |
| 15 | ### 1. Check rudder-cli |
| 16 | |
| 17 | ```bash |
| 18 | # Check if installed |
| 19 | which rudder-cli |
| 20 | |
| 21 | # If installed, check authentication |
| 22 | rudder-cli workspace info |
| 23 | ``` |
| 24 | |
| 25 | ### 2. Check Terraform (if using terraform workflows) |
| 26 | |
| 27 | ```bash |
| 28 | # Check if installed |
| 29 | which terraform |
| 30 | |
| 31 | # If installed, check version |
| 32 | terraform version |
| 33 | |
| 34 | # Check if provider is configured (run in project directory) |
| 35 | terraform providers |
| 36 | ``` |
| 37 | |
| 38 | ### 3. Check MCP Server Connectivity |
| 39 | |
| 40 | ```bash |
| 41 | # Check if hosted MCP server is reachable |
| 42 | curl -s -o /dev/null -w "%{http_code}" https://mcp.rudderstack.com/health |
| 43 | ``` |
| 44 | |
| 45 | ## Output Format |
| 46 | |
| 47 | Present results as a status table: |
| 48 | |
| 49 | ``` |
| 50 | RudderStack Environment Check |
| 51 | ───────────────────────────────────────────────────── |
| 52 | Tool Status Action |
| 53 | ───────────────────────────────────────────────────── |
| 54 | rudder-cli ✓ Ready |
| 55 | └─ authenticated ✓ Ready Workspace: <name> |
| 56 | terraform ✗ Missing Run: /rudder-terraform-setup |
| 57 | └─ provider ─ Skipped (terraform required first) |
| 58 | mcp.rudderstack.com ✓ Reachable |
| 59 | ───────────────────────────────────────────────────── |
| 60 | ``` |
| 61 | |
| 62 | ## Status Indicators |
| 63 | |
| 64 | | Status | Meaning | |
| 65 | |--------|---------| |
| 66 | | ✓ Ready | Tool installed and configured | |
| 67 | | ✗ Missing | Tool not found, needs installation | |
| 68 | | ─ Skipped | Dependency not met, check parent first | |
| 69 | | ⚠ Issue | Tool found but configuration problem | |
| 70 | |
| 71 | ## Next Steps by Status |
| 72 | |
| 73 | | Tool Missing | Action | |
| 74 | |--------------|--------| |
| 75 | | rudder-cli | Run `/rudder-cli-setup` or ask "help me install rudder-cli" | |
| 76 | | terraform | Run `/rudder-terraform-setup` or ask "help me setup terraform for rudderstack" | |
| 77 | | MCP unreachable | Run `/rudder-mcp-setup` or check network connectivity | |
| 78 | |
| 79 | ## Credential Security |
| 80 | |
| 81 | - This skill only checks tool availability and authentication status |
| 82 | - Never logs or displays access tokens |
| 83 | - Workspace info shows only workspace name/ID, not credentials |