Stats
Actions
Tags
From foundation
**Purpose:** Complete Doppler secret management setup with scripts, templates, and GitHub integration
How this skill is triggered — by the user, by Claude, or both
Slash command
/foundation:doppler-managementThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Purpose:** Complete Doppler secret management setup with scripts, templates, and GitHub integration
Purpose: Complete Doppler secret management setup with scripts, templates, and GitHub integration
Category: Secret Management / DevOps
This skill provides comprehensive Doppler setup for centralized secret management:
skills/doppler-management/scripts/)migrate-to-doppler.sh - Migration script template
run-with-doppler.sh - Command wrapper template
setup-doppler-github.sh - Interactive GitHub integration wizard
skills/doppler-management/templates/docs/)README.md - Main documentation index
integration-guide.md - Complete integration guide
github-integration.md - GitHub App setup guide
environment-setup.md - Multi-environment configuration
PLUGIN-DESIGN.md - Plugin architecture documentation
skills/doppler-management/templates/workflows/)test-doppler-secrets.yml - GitHub Actions test workflow
Use when setting up Doppler for the first time:
# Command: /foundation:doppler-setup [project-name]
Steps executed:
1. Check Doppler CLI installation
2. Detect project name and GitHub repo
3. Create Doppler project and environments
4. Generate scripts in scripts/doppler/
5. Generate documentation in docs/doppler/
6. Create GitHub Actions workflow
7. Update .gitignore
8. Display setup summary
Use when you need to regenerate scripts:
Invoke skill: doppler-management
Context: "Generate Doppler scripts for [project-name]"
Output:
- scripts/doppler/migrate-to-doppler.sh
- scripts/doppler/run-with-doppler.sh
- scripts/doppler/setup-doppler-github.sh
Use when you need fresh documentation:
Invoke skill: doppler-management
Context: "Generate Doppler documentation for [project-name]"
Output:
- docs/doppler/README.md
- docs/doppler/integration-guide.md
- docs/doppler/github-integration.md
- docs/doppler/environment-setup.md
When invoked, this skill automatically detects:
From .claude/project.json:
{{PROJECT_NAME}} - Project name{{TECH_STACK}} - Framework information{{ENVIRONMENT_VARS}} - List of environment variablesFrom git remote:
{{GITHUB_REPO}} - Repository owner/nameFrom environment:
{{GENERATION_DATE}} - Current dateScans these sources in order:
.env* filesspecs/ directory (service requirements).claude/project.json (declared variables)Automatically categorizes detected variables:
CRITICAL: All generated files follow security rules:
@~/.claude/plugins/marketplaces/dev-lifecycle-marketplace/docs/security/SECURITY-RULES.md
✅ All scripts use placeholders:
# CORRECT - Always generated this way
GOOGLE_API_KEY=your_google_api_key_here
SUPABASE_URL=https://your-project.supabase.co
✅ Never hardcodes secrets:
✅ Documentation includes acquisition guides:
✅ Protects sensitive files:
.doppler.env, doppler.yaml, .doppler/.env.* except .env.exampleDetected patterns:
os.getenv(), os.environ.get(), os.environ[]pydantic.BaseSettingsGenerated code:
import os
api_key = os.getenv("GOOGLE_API_KEY")
Run command:
./run-with-doppler.sh uvicorn api.main:app --reload
Detected patterns:
process.env.NEXT_PUBLIC_*process.env.* in API routesGenerated code:
// Client-side
const url = process.env.NEXT_PUBLIC_SUPABASE_URL
// Server-side
const key = process.env.SUPABASE_SERVICE_KEY
Run command:
./run-with-doppler.sh npm run dev
Works with any tech stack that uses environment variables.
/foundation:doppler-setupPrimary command that orchestrates complete Doppler setup:
**Arguments**: [project-name]
Process:
1. Invoke doppler-management skill for detection
2. Create Doppler project via CLI
3. Generate all scripts from templates
4. Generate all documentation from templates
5. Create GitHub Actions workflow
6. Update .gitignore
7. Display summary and next steps
/foundation:env-varsComplementary command for environment variable management:
Integration:
- Detects vars → Provides to doppler-management skill
- Generates .env files → Used by migration script
- Multi-environment support → Matches Doppler configs
project/
├── scripts/
│ └── doppler/
│ ├── migrate-to-doppler.sh # Migration script
│ ├── run-with-doppler.sh # Run wrapper
│ └── setup-doppler-github.sh # GitHub setup wizard
├── docs/
│ └── doppler/
│ ├── README.md # Documentation index
│ ├── integration-guide.md # Integration guide
│ ├── github-integration.md # GitHub setup
│ ├── environment-setup.md # Environment guide
│ └── PLUGIN-DESIGN.md # Architecture docs
├── .github/
│ └── workflows/
│ └── test-doppler-secrets.yml # Test workflow
└── DOPPLER-SETUP-SUMMARY.md # Quick reference
✅ Scripts in scripts/doppler/
✅ Docs in docs/doppler/
✅ Workflows in .github/workflows/
Scenario: Fresh project, never used Doppler
# User runs:
/foundation:doppler-setup my-saas-app
# Skill detects:
- Project name: my-saas-app
- GitHub repo: username/my-saas-app (from git remote)
- Tech stack: FastAPI + Next.js (from project.json)
- Environment vars: 12 detected
# Skill generates:
✓ scripts/doppler/migrate-to-doppler.sh (with 12 vars)
✓ scripts/doppler/run-with-doppler.sh
✓ scripts/doppler/setup-doppler-github.sh
✓ docs/doppler/ (all 4 guides)
✓ .github/workflows/test-doppler-secrets.yml
✓ DOPPLER-SETUP-SUMMARY.md
# User next steps:
1. Edit scripts/doppler/migrate-to-doppler.sh (add real secrets)
2. Run: scripts/doppler/migrate-to-doppler.sh
3. Run: scripts/doppler/setup-doppler-github.sh
4. Test: scripts/doppler/run-with-doppler.sh uvicorn api.main:app
Scenario: Added Stripe, need updated scripts
# User adds to project.json:
"environment_variables": {
"stripe": ["STRIPE_SECRET_KEY", "STRIPE_PUBLISHABLE_KEY"]
}
# User runs:
/foundation:doppler-setup # Detects existing setup
# Skill detects:
- Existing Doppler project
- New variables: STRIPE_SECRET_KEY, STRIPE_PUBLISHABLE_KEY
- Existing migration script
# Skill offers:
"Detected existing Doppler setup. Options:"
1. Regenerate migration script (includes new Stripe vars)
2. Update documentation
3. Both
# User selects: Both
# Skill updates:
✓ scripts/doppler/migrate-to-doppler.sh (now includes Stripe)
✓ docs/doppler/environment-setup.md (Stripe section added)
Fix:
chmod +x scripts/doppler/*.sh
Causes:
Fix: Manually add to migration script or declare in project.json:
"environment_variables": {
"custom": ["MY_CUSTOM_VAR"]
}
Fix:
See docs/doppler/github-integration.md troubleshooting section
Skill: doppler-management
Context: "Setup Doppler for [project-name]"
The skill will:
1. Detect project context
2. Generate all scripts and docs
3. Provide next steps
/foundation:doppler-setup [project-name]
The command internally invokes this skill.
Templates are in skills/doppler-management/templates/
To update:
To add support for a new service:
v1.0.0 (2025-11-12)
Maintained by: Foundation Plugin Team Category: Secret Management Tags: doppler, secrets, environment, github, ci-cd, deployment
npx claudepluginhub vanman2024/dev-lifecycle-marketplace --plugin foundationManages full lifecycle of secrets and environment variables: decides placement (constant, .env, CI secret, env var), scaffolds .env.example/.gitignore, add/update/rotate/remove/migrate/audit/provision across envs. Language-agnostic.
Interactively sets up GCP Cloud Build + Cloud Run infrastructure. Provisions APIs, Artifact Registry, service accounts, IAM, secrets, and triggers with security best practices.
Scans projects for exposed secrets, recommends management providers, sets up secret storage and injection into CI/CD/deployments, audits configurations for infrastructure.