agentleFS
jamesblackwelljamesblackwell/falcondeck/.agents/skills/doppler/SKILL.md

doppler

Skill7 starsChanged 8 days agoMITView on GitHub

Manage secrets with Doppler: CLI operations, project/config/environment management, secrets injection, CI/CD integrations, and security best practices.

  • Pipes a download into a shell
  • Reads credentials
  • Installs packages

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. About 0 are common, 7 are distinctive, and 9 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 9

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user mentions: "doppler", "secrets management", "doppler cli", "doppler secrets", "doppler run", "doppler setup", …

    line 19
  2. Very specific:

    Run doppler me to check current auth status

    line 204
  3. Very specific:

    Run doppler configure debug to see active configuration

    line 205
  4. Very specific:

    Check which project/config is active: doppler configure debug

    line 211
  5. Very specific:

    Verify scope: doppler setup in the project directory

    line 212
  6. Very specific:

    Use explicit flags: doppler secrets -p project -c config

    line 213
  7. Very specific:

    Check for environment variable overrides: doppler run --preserve-env=false

    line 214
  8. Distinctive:

    Ensure fallback path is writable

    line 218
  9. Distinctive:

    Check passphrase hasn't changed (config-dependent by default)

    line 219
  10. Very specific:

    Use doppler run clean to remove old fallback files

    line 220
  11. Distinctive:

    Verify token is for the correct project and config

    line 225
  12. Distinctive:

    Check token hasn't been revoked in the dashboard

    line 227
  13. Very specific:

    Ensure DOPPLER_TOKEN env var is set correctly

    line 228
  14. Distinctive:

    When helping with Doppler:

    line 232
  15. Distinctive:

    Consult references: Use reference docs for detailed CLI flags and integration patterns

    line 237
  16. Very specific:

    Security first: Never output secret values in logs.

    line 238

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Doppler Secrets Management

Comprehensive assistance for the Doppler secrets management platform: CLI operations, project and config management, secrets injection, integration syncs, and security best practices.

Triggers

Use this skill when the user mentions: "doppler", "secrets management", "doppler cli", "doppler secrets", "doppler run", "doppler setup", "doppler configs", "doppler projects", "secret injection", "doppler environments", "service tokens".

Quick Start

Install CLI

# macOS
brew install gnupg && brew install dopplerhq/cli/doppler

# Linux (Debian/Ubuntu)
apt-get update && apt-get install -y apt-transport-https ca-certificates curl gnupg
curl -sLf --retry 3 --tlsv1.2 --proto "=https" \
  'https://packages.doppler.com/public/cli/gpg.DE2A7741A397C129.key' | \
  gpg --dearmor -o /usr/share/keyrings/doppler-archive-keyring.gpg
echo "deb [signed-by=/usr/share/keyrings/doppler-archive-keyring.gpg] https://packages.doppler.com/public/cli/deb/debian any-version main" | \
  tee /etc/apt/sources.list.d/doppler-cli.list
apt-get update && apt-get install doppler

# Shell script (any OS)
curl -sLf --retry 3 --tlsv1.2 --proto "=https" https://get.doppler.com | sh

Authenticate & Setup

# Login (opens browser for auth)
doppler login

# Setup project in current directory (interactive)
doppler setup

# Non-interactive setup
doppler setup --project my-app --config dev --no-interactive

Common Tasks by Intent

Developer wants to...Action
List all secretsdoppler secrets -p <project> -c <config>
Get a single secretdoppler secrets get SECRET_NAME -p <project> -c <config>
Set a secretdoppler secrets set KEY=value -p <project> -c <config>
Set multiple secretsdoppler secrets set KEY1=val1 KEY2=val2
Delete a secretdoppler secrets delete SECRET_NAME
Run command with secretsdoppler run -- your-command --flags
Run with specific configdoppler run -p backend -c dev -- npm start
Download secrets as filedoppler secrets download --format env --no-file
List projectsdoppler projects
List configsdoppler configs -p <project>
List environmentsdoppler environments -p <project>
Clone a configdoppler configs clone -p <project> -c <source> --name <new>
View activity logsdoppler activity
Check current setupdoppler configure debug
Open dashboarddoppler open
View who is authenticateddoppler me

Secrets Injection Patterns

Environment Variable Injection

# Inject secrets as env vars for any command
doppler run -- node server.js
doppler run -- docker compose up
doppler run -- terraform apply

# Run a shell command string
doppler run --command "echo $DATABASE_URL && npm start"

# Only inject specific secrets
doppler run --only-secrets DATABASE_URL,API_KEY -- node server.js

Mount Secrets to File

# Mount as JSON file (ephemeral, cleaned up after process exits)
doppler run --mount secrets.json -- cat secrets.json

# Mount as .env file
doppler run --mount .env --mount-format env -- your-command

# Mount with template
doppler run --mount config.yaml --mount-template template.yaml -- your-command

Template Substitution

# Substitute secrets into a template file
doppler secrets substitute template.env.tpl > .env

Fallback for Offline/Resilience

# Run with fallback file (writes encrypted secrets on success, reads on failure)
doppler run --fallback ./fallback.encrypted -- npm start

# Read-only fallback (never update the fallback file)
doppler run --fallback ./fallback.encrypted --fallback-readonly -- npm start

# Offline mode (read directly from fallback, no API contact)
doppler run --fallback-only --fallback ./fallback.encrypted -- npm start

Project & Config Hierarchy

Doppler organizes secrets in a hierarchy:

Workplace
 └── Project (e.g. "backend", "frontend")
      └── Environment (e.g. "development", "staging", "production")
           └── Config (e.g. "dev", "stg", "prd")
                └── Branch Config (e.g. "dev_feature-x")

Config Inheritance

  • Root configs (dev, stg, prd) inherit from their environment
  • Branch configs inherit from their parent config
  • Overrides cascade: Environment → Config → Branch Config
  • Personal configs allow individual developer overrides without affecting the team

Integration Syncs

Doppler can automatically sync secrets to external platforms:

PlatformUse Case
AWS Secrets Manager / SSMECS, Lambda, EC2 deployments
GCP Secret ManagerGKE, Cloud Run, Cloud Functions
Azure Key VaultAKS, App Service, Functions
Cloudflare Pages / WorkersEdge & Jamstack deployments
VercelFrontend/fullstack deployments
Firebase Functions / HostingFunctions config & build-time secrets
Serverless FrameworkLambda/serverless function secrets
GitHub ActionsCI/CD secrets
Docker / Docker ComposeContainer environment injection
KubernetesSecret objects via Doppler Operator
TerraformInfrastructure as Code
Webapp.ioCI/CD Layerfile secrets
HerokuPaaS deployments

Service Tokens

For CI/CD and production, use service tokens (read-only, scoped to a single config):

# Generate a service token via dashboard or API
# Use in CI/CD:
DOPPLER_TOKEN=dp.st.xxx doppler run -- your-command

# Or set as environment variable
export DOPPLER_TOKEN=dp.st.xxx
doppler secrets

Security Best Practices

  • Never commit secrets to version control — use Doppler as the single source of truth
  • Use service tokens in production (read-only, config-scoped)
  • Use personal configs for local development overrides
  • Enable change requests for production configs (requires approval before changes)
  • Rotate secrets regularly — use Doppler's rotation reminders
  • Use OIDC authentication where possible for short-lived tokens
  • Audit access via doppler activity and dashboard audit logs
  • Use branch configs to isolate feature branch secrets
  • Never use --no-verify-tls in production

Reference Documents

For deep dives, consult these references:

ReferenceContent
CLI.mdComplete CLI command reference with all subcommands and flags
INTEGRATIONS.mdCI/CD, Docker, Kubernetes, cloud platform integration patterns

Troubleshooting

Authentication Issues

  1. Run doppler me to check current auth status
  2. Run doppler configure debug to see active configuration
  3. Re-authenticate with doppler login
  4. Check scope: doppler configure get token --scope /path/to/project

Wrong Secrets Loaded

  1. Check which project/config is active: doppler configure debug
  2. Verify scope: doppler setup in the project directory
  3. Use explicit flags: doppler secrets -p project -c config
  4. Check for environment variable overrides: doppler run --preserve-env=false

Fallback File Issues

  1. Ensure fallback path is writable
  2. Check passphrase hasn't changed (config-dependent by default)
  3. Use doppler run clean to remove old fallback files
  4. Regenerate with a fresh doppler run --fallback ./path -- echo ok

Service Token Not Working

  1. Verify token is for the correct project and config
  2. Service tokens are read-only — cannot set/delete secrets
  3. Check token hasn't been revoked in the dashboard
  4. Ensure DOPPLER_TOKEN env var is set correctly

Workflow

When helping with Doppler:

  1. Identify the task: Setup, secret management, injection, integration, or debugging
  2. Check prerequisites: Is doppler CLI installed? Is user authenticated?
  3. Determine scope: Which project and config are we working with?
  4. Consult references: Use reference docs for detailed CLI flags and integration patterns
  5. Security first: Never output secret values in logs; use --only-names for listing

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.