Skip to content
Back to skills

Rudder Environment Check

ASecurity

Checks 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

  • 18 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added August 31, 2026
ai-agentsbashterraformsecurity

Works with

  • cli
  • mcp

Security analysis

A100/100

Scanned August 31, 2026

npx -y skills add rudderlabs/rudder-agent-skills --skill rudder-environment-check --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Rudder Environment Check?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Rudder Environment Check
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rudderlabs-rudder-environment-check/badge)](https://www.skillsdirectory.com/skills/rudderlabs-rudder-environment-check)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: rudder-environment-check
description: Checks 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
allowed-tools: "Bash(which, curl, rudder-cli *, terraform *), Read"
---

# RudderStack Environment Check

Quick diagnostic that checks all RudderStack tool prerequisites and provides actionable guidance.

## When to Use

- Before starting with RudderStack workflows
- When troubleshooting "command not found" errors
- To verify your development environment is ready

## Check Process

Run these checks in sequence:

### 1. Check rudder-cli

```bash
# Check if installed
which rudder-cli

# If installed, check authentication
rudder-cli workspace info
```

### 2. Check Terraform (if using terraform workflows)

```bash
# Check if installed
which terraform

# If installed, check version
terraform version

# Check if provider is configured (run in project directory)
terraform providers
```

### 3. Check MCP Server Connectivity

```bash
# Check if hosted MCP server is reachable
curl -s -o /dev/null -w "%{http_code}" https://mcp.rudderstack.com/health
```

## Output Format

Present results as a status table:

```
RudderStack Environment Check
─────────────────────────────────────────────────────
Tool                    Status      Action
─────────────────────────────────────────────────────
rudder-cli              ✓ Ready
  └─ authenticated      ✓ Ready     Workspace: <name>
terraform               ✗ Missing   Run: /rudder-terraform-setup
  └─ provider           ─ Skipped   (terraform required first)
mcp.rudderstack.com     ✓ Reachable
─────────────────────────────────────────────────────
```

## Status Indicators

| Status | Meaning |
|--------|---------|
| ✓ Ready | Tool installed and configured |
| ✗ Missing | Tool not found, needs installation |
| ─ Skipped | Dependency not met, check parent first |
| ⚠ Issue | Tool found but configuration problem |

## Next Steps by Status

| Tool Missing | Action |
|--------------|--------|
| rudder-cli | Run `/rudder-cli-setup` or ask "help me install rudder-cli" |
| terraform | Run `/rudder-terraform-setup` or ask "help me setup terraform for rudderstack" |
| MCP unreachable | Run `/rudder-mcp-setup` or check network connectivity |

## Credential Security

- This skill only checks tool availability and authentication status
- Never logs or displays access tokens
- Workspace info shows only workspace name/ID, not credentials

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.