Skip to main content
skill CX Codex

secrets-env-manager — Claude Code skill: what it does, how to install

secrets-env-manager validates environment variables in CI workflows, enforces secret masking, and catches leaked keys early.

MIT 276 installs ★ 64 updated 2026-01-12

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add patricio0312rev/skills --skill secrets-env-manager -a claude-code
Open on GitHub

What secrets-env-manager does

This skill provides setup templates for handling application credentials within GitHub Actions pipelines. It features bash logic to halt jobs immediately when required keys like DATABASE_URL or STRIPE_SECRET_KEY are unset, logs masking via ::add-mask::, and automated secret scanning steps.

It also includes a Node.js TypeScript validation helper in scripts/validate-env.ts, an organized .env.example structure, and variable documentation templates for development setups.

All preconfigured examples directly target GitHub Actions and bash scripting. Teams using different continuous integration runners must rewrite the workflow syntax and masking tokens.

What it helps with

  • fail CI jobs early when required environment variables are missing
  • mask database credentials and API keys in pipeline console logs
  • integrate TruffleHog and reviewdog into git workflows to spot leaks
  • generate structured .env.example files with field documentation

Example prompts for the agent

  • Add environment variable validation to my GitHub Actions workflow
  • Write scripts/validate-env.ts to check required credentials on startup
  • Configure secret masking for sensitive deployment commands

How to install secrets-env-manager

1Skills CLI (Vercel)

npx skills add patricio0312rev/skills --skill secrets-env-manager -a claude-code

2Manually: put the files in place

~/.claude/skills/secrets-env-manager/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/secrets-env-manager/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about secrets-env-manager

How to install secrets-env-manager in Claude Code?

Run npx skills add patricio0312rev/skills --skill secrets-env-manager -a claude-code.

What does secrets-env-manager do?

It equips the agent with guidelines and scripts to validate environment configurations, obscure console outputs, and stop secret leaks.

Which scanners does the skill configure for leak prevention?

It provides configurations using trufflesecurity/trufflehog and reviewdog/action-detect-secrets.

Source text

SKILL.md · MIT
---
name: secrets-env-manager
description: Validates environment variables in CI, prevents secret leaks, enforces masking, and provides fail-fast validation with clear documentation. Use for "secrets management", "env var validation", "credential security", or "secret masking".
---

# Secrets & Env Manager

Secure secrets handling and environment variable validation in CI/CD.

## Environment Variable Validation

```yaml
validate-env:
  runs-on: ubuntu-latest
  steps:
    - uses: actions/checkout@v4

    - name: Validate required environment variables
      run: |
        REQUIRED_VARS=(
          "DATABASE_URL"
          "API_KEY"
          "AWS_REGION"
          "STRIPE_SECRET_KEY"
        )

        MISSING=()
        for var in "${REQUIRED_VARS[@]}"; do
          if [ -z "${!var}" ]; then
            MISSING+=("$var")
          fi
        done

        if [ ${#MISSING[@]} -ne 0 ]; then
          echo "❌ Missing required environment variables:"
          printf '%s\n' "${MISSING[@]}"
          exit 1
        fi

        echo "✅ All required environment variables are set"
      env:
        DATABASE_URL: ${{ secrets.DATABASE_URL }}
        API_KEY: ${{ secrets.API_KEY }}
        AWS_REGION: ${{ secrets.AWS_REGION }}
        STRIPE_SECRET_KEY: ${{ secrets.STRIPE_SECRET_KEY }}
```

## Secret Masking

```yaml
- name: Mask sensitive values
  run: |
    # Automatically masked in GitHub Actions
    echo "::add-mask::${{ secrets.API_KEY }}"
    echo "::add-mask::${{ secrets.DATABASE_PASSWORD }}"

    # Safe to use in commands
    curl -H "Authorization: Bearer ${{ secrets.API_KEY }}" https://api.example.com
```

## Leak Prevention

```yaml
- name: Check for leaked secrets
  uses: trufflesecurity/trufflehog@main
  with:
    path: ./
    base: ${{ github.event.repository.default_branch }}
    head: HEAD

- name: Detect hardcoded secrets
  uses: reviewdog/action-detect-secrets@master
  with:
    github_token: ${{ secrets.GITHUB_TOKEN }}
    reporter: github-pr-review
```

## Environment-specific Secrets

```yaml
deploy:
  runs-on: ubuntu-latest
  environment:
    name: ${{ github.event.inputs.environment }}
  steps:
    - name: Deploy
      run: |
        # Environment-specific secrets are automatically scoped
        echo "Deploying to ${{ github.event.inputs.environment }}"
      env:
        DATABASE_URL: ${{ secrets.DATABASE_URL }}
        API_KEY: ${{ secrets.API_KEY }}
```

## Secret Validation Script

```typescript
// scripts/validate-env.ts
import * as fs from "fs";

interface EnvConfig {
  required: string[];
  optional: string[];
}

const config: EnvConfig = {
  required: ["DATABASE_URL", "JWT_SECRET", "STRIPE_SECRET_KEY"],
  optional: ["SENTRY_DSN", "LOG_LEVEL"],
};

function validateEnv(): boolean {
  const missing: string[] = [];

  config.required.forEach((key) => {
    if (!process.env[key]) {
      missing.push(key);
    }
  });

  if (missing.length > 0) {
    console.error("❌ Missing required environment variables:");
    missing.forEach((key) => console.error(`  - ${key}`));
    return false;
  }

  console.log("✅ All required environment variables are set");
  return true;
}

if (!validateEnv()) {
  process.exit(1);
}
```

## .env.example Template

```bash
# .env.example - Check into git
# Copy to .env and fill in values

# Database
DATABASE_URL=postgresql://user:password@localhost:5432/mydb

# Authentication
JWT_SECRET=your-secret-here
JWT_EXPIRY=24h

# External APIs
STRIPE_SECRET_KEY=sk_test_...
SENDGRID_API_KEY=SG....

# AWS
AWS_ACCESS_KEY_ID=AKIA...
AWS_SECRET_ACCESS_KEY=...
AWS_REGION=us-east-1

# Optional
SENTRY_DSN=https://...
LOG_LEVEL=info
```

## Documentation Template

```markdown
# Environment Variables

## Required Variables

### DATABASE_URL

**Description:** PostgreSQL connection string
**Format:** `postgresql://user:password@host:5432/database`
**Example:** `postgresql://app:secret@localhost:5432/myapp`
**Where to get:** Create database on Heroku/RDS

### STRIPE_SECRET_KEY

**Description:** Stripe API secret key
**Format:** `sk_test_...` or `sk_live_...`
**Example:** `sk_test_51abc123...`
**Where to get:** Stripe Dashboard → Developers → API Keys
**⚠️ Never commit to git**

## Optional Variables

### LOG_LEVEL

**Description:** Logging verbosity
**Format:** `error | warn | info | debug`
**Default:** `info`
```

## Fail-Fast Validation

```yaml
jobs:
  validate:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Validate secrets exist
        run: |
          if [ -z "${{ secrets.DATABASE_URL }}" ]; then
            echo "::error::DATABASE_URL secret not set"
            exit 1
          fi

          if [ -z "${{ secrets.API_KEY }}" ]; then
            echo "::error::API_KEY secret not set"
            exit 1
          fi

  deploy:
    needs: validate
    runs-on: ubuntu-latest
    steps:
      - name: Deploy
        run: echo "Deploying..."
```

## Best Practices

1. **Never log secrets**: Always mask sensitive values
2. **Validate early**: Check secrets before deployment
3. **Use GitHub Secrets**: Never hardcode in workflows
4. **Environment separation**: Dev/staging/prod secrets
5. **Rotate regularly**: Update secrets periodically
6. **Principle of least privilege**: Minimal permissions
7. **Document clearly**: Where to get each secret
8. **Scan for leaks**: Automated detection

## Output Checklist

- [ ] Required env vars validated
- [ ] Secret masking configured
- [ ] Leak detection enabled
- [ ] .env.example template
- [ ] Environment variables documented
- [ ] Fail-fast validation
- [ ] Environment-specific secrets
- [ ] Rotation policy documented

© patricio0312rev · MIT · patricio0312rev/skills

Similar skills

All skills for Security →

From the same set148

The whole set →
rest-to-graphql-migrator rest-to-graphql-migrator — a skill that walks a REST API over to GraphQL one endpoint at a time, wrapping existing routes instead of rebuilding the backend. CX Codex +1 277installs insomnia-collection-generator insomnia-collection-generator scans Express, Fastify, and Next.js routes to generate an Insomnia v4 collection export file with organized workspaces, folders, and environments. CX Codex +1 277installs security-pr-checklist-skill security-pr-checklist-skill builds a repeatable security checklist for pull requests. Use it to structure code reviews, required checks, and CI security gates. CX Codex +1 276installs design-to-component-translator The design-to-component-translator skill turns Figma specs into React components with design tokens, responsive rules, and interaction states for implementing designs in code. CX Codex +1 276installs evaluation-harness evaluation-harness — a skill for Claude Code and five other agent platforms that sets up repeatable LLM evaluation: golden datasets, scoring rubrics, pass/fail thresholds, and regression reports. CX Codex +1 275installs backend-latency-profiler-helper backend-latency-profiler-helper tracks down slow API endpoints, lists likely causes, and puts the fixes in priority order. CX Codex +1 275installs rbac-policy-tester rbac-policy-tester generates role permission matrices and automated authorization test suites to catch RBAC regressions in CI. CX Codex +1 274installs etl-sync-job-builder etl-sync-job-builder generates TypeScript ETL pipelines with incremental watermark tracking, idempotent batch upserts, and retry backoff logic. CX Codex +1 274installs

Project sponsors

Companies that keep this analytics open