clay-multi-env-setup

Name: clay-multi-env-setup - Agent Skill
Rating: 5.0 (1046 reviews)
Author: jeremylongshore

1,046

MIT

Configure Clay across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment secrets, or implementing environment-specific Clay configurations. Trigger with phrases like "clay environments", "clay staging", "clay dev prod", "clay environment setup", "clay config by env".

Download Folder View on GitHub

CLI Install

Recommended

Use the skills CLI to install this skill with one command. Auto-detects all installed AI assistants.

Method 1 - skills CLI

npx skills i jeremylongshore/claude-code-plugins-plus-skills/plugins/saas-packs/clay-pack/skills/clay-multi-env-setup

Method 2 - openskills (supports sync & update)

npx openskills install jeremylongshore/claude-code-plugins-plus-skills

Auto-detects Claude Code, Cursor, Codex CLI, Gemini CLI, and more. One install, works everywhere.

Installation Path

Download and extract to one of the following locations:

~/.claude/skills/clay-multi-env-setup/

SKILL.md

Skill Instructions

Back

Run with Cloud Agent

No setup needed. Let our cloud agents run this skill for you.

Select Provider

Select Model

Claude Sonnet 4.5

$0.20/task

Best for coding tasks

No setup required

Clay Multi-Environment Setup

Overview

Configure Clay across development, staging, and production environments.

Prerequisites

Separate Clay accounts or API keys per environment
Secret management solution (Vault, AWS Secrets Manager, etc.)
CI/CD pipeline with environment variables
Environment detection in application

Environment Strategy

Environment	Purpose	API Keys	Data
Development	Local dev	Test keys	Sandbox
Staging	Pre-prod validation	Staging keys	Test data
Production	Live traffic	Production keys	Real data

Configuration Structure

config/
├── clay/
│   ├── base.json           # Shared config
│   ├── development.json    # Dev overrides
│   ├── staging.json        # Staging overrides
│   └── production.json     # Prod overrides

base.json

{
  "timeout": 30000,
  "retries": 3,
  "cache": {
    "enabled": true,
    "ttlSeconds": 60
  }
}

development.json

{
  "apiKey": "${CLAY_API_KEY}",
  "baseUrl": "https://api-sandbox.clay.com",
  "debug": true,
  "cache": {
    "enabled": false
  }
}

staging.json

{
  "apiKey": "${CLAY_API_KEY_STAGING}",
  "baseUrl": "https://api-staging.clay.com",
  "debug": false
}

production.json

{
  "apiKey": "${CLAY_API_KEY_PROD}",
  "baseUrl": "https://api.clay.com",
  "debug": false,
  "retries": 5
}

Environment Detection

// src/clay/config.ts
import baseConfig from '../../config/clay/base.json';
 
type Environment = 'development' | 'staging' | 'production';
 
function detectEnvironment(): Environment {
  const env = process.env.NODE_ENV || 'development';

Secret Management by Environment

Local Development

# .env.local (git-ignored)
CLAY_API_KEY=sk_test_dev_***

CI/CD (GitHub Actions)

env:
  CLAY_API_KEY: ${{ secrets.CLAY_API_KEY_${{ matrix.environment }} }}

Production (Vault/Secrets Manager)

# AWS Secrets Manager
aws secretsmanager get-secret-value --secret-id clay/production/api-key
 
# GCP Secret Manager
gcloud secrets versions access latest --secret=clay-api-key
 
# HashiCorp Vault
vault kv get -field=api_key secret/clay/production

Environment Isolation

// Prevent production operations in non-prod
function guardProductionOperation(operation: string): void {
  const config = getClayConfig();
 
  if (config.environment !== 'production') {
    console.warn(`[clay] ${operation} blocked in ${config.environment}`);

Feature Flags by Environment

const featureFlags: Record<Environment, Record<string, boolean>> = {
  development: {
    newFeature: true,
    betaApi: true,
  },
  staging: {
    newFeature: true,
    betaApi: false,
  },
  production: {
    newFeature:

Instructions

Step 1: Create Config Structure

Set up the base and per-environment configuration files.

Step 2: Implement Environment Detection

Add logic to detect and load environment-specific config.

Step 3: Configure Secrets

Store API keys securely using your secret management solution.

Step 4: Add Environment Guards

Implement safeguards for production-only operations.

Output

Multi-environment config structure
Environment detection logic
Secure secret management
Production safeguards enabled

Error Handling

Issue	Cause	Solution
Wrong environment	Missing NODE_ENV	Set environment variable
Secret not found	Wrong secret path	Verify secret manager config
Config merge fails	Invalid JSON	Validate config files
Production guard triggered	Wrong environment	Check NODE_ENV value

Examples

Quick Environment Check

const env = getClayConfig();
console.log(`Running in ${env.environment} with ${env.baseUrl}`);

Resources

Next Steps

For observability setup, see clay-observability.