# doppler-secret-validation

The doppler-secret-validation skill helps store secrets in Doppler, verify retrieval, and test API authentication. Use it to check a token before relying on it in a project.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 135 installs · ★ 3 repo stars
- Author: terrylica
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/terrylica/cc-skills/tree/HEAD/plugins/devops-tools/skills/doppler-secret-validation/SKILL.md
- Updated: 2026-10-25
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/doppler-secret-validation

## What it does

The skill checks a token’s format before storage, adds it to a Doppler project and config, then verifies that it can be retrieved and passed through `doppler run`. The `scripts/validate_secret.py` script checks storage and environment injection. For an API authentication check, it provides `scripts/test_api_auth.py`, which can be adapted to the API in use.

Add a secret with `doppler secrets set SECRET_NAME="value" --project PROJECT --config CONFIG`. For local development, `doppler setup` can bind a directory to a project and config so later `doppler run` commands can omit those options. The skill recommends keeping secrets scoped to a single command and masking them rather than printing their full values.

You need the Doppler CLI and access to the target project. The CLI does not accept `--note`, so add secret notes through the Doppler dashboard. GitHub tokens are an exception: the skill says not to inject `GH_TOKEN` or `GITHUB_TOKEN` from Doppler into a directory.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add terrylica/cc-skills --skill doppler-secret-validation -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/doppler-secret-validation/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/doppler-secret-validation/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add terrylica/cc-skills --skill doppler-secret-validation -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/doppler-secret-validation/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add terrylica/cc-skills --skill doppler-secret-validation -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/doppler-secret-validation/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install terrylica/cc-skills plugins/devops-tools/skills/doppler-secret-validation
```

2. **Manually: put the files in place**
- File: `.github/skills/doppler-secret-validation/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add terrylica/cc-skills --skill doppler-secret-validation -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/terrylica/cc-skills --path plugins/devops-tools/skills/doppler-secret-validation
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/doppler-secret-validation/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add terrylica/cc-skills --skill doppler-secret-validation -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/terrylica/cc-skills/tree/HEAD/plugins/devops-tools/skills/doppler-secret-validation/SKILL.md

## When to use it
- check a token’s format before storing it
- add a secret to a Doppler project and config
- verify secret retrieval and injection through `doppler run`
- test API authentication with a stored token
- compare a secret across dev, stg, and prd configs

## Example prompts
- Check this token’s format, then add it to Doppler under project `private-config` and config `prd`.
- Verify that `PYPI_TOKEN` can be retrieved from Doppler and passed through `doppler run`.
- Test API authentication using `PYPI_TOKEN` and `https://upload.pypi.org/legacy/`.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 9241700eb1b7f85d.

BEGIN THIRD-PARTY FILE 9241700eb1b7f85d
````text
---
name: doppler-secret-validation
description: Validate and test Doppler secrets. TRIGGERS - add to Doppler, store secret, validate token, test credentials.
allowed-tools: Read, Bash
---

# Doppler Secret Validation

> **Self-Evolving Skill**: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.

## Overview

Workflow for securely adding, validating, and testing API tokens and credentials in Doppler secrets management.

## When to Use This Skill

Use this skill when:

- User provides API tokens or credentials (PyPI, GitHub, AWS, etc.)
- User mentions "add to Doppler", "store secret", "validate token"
- User wants to test authentication before production use
- User needs to verify secret storage and retrieval

## Workflow

### Step 1: Test Token Format (Before Adding to Doppler)

Before storing in Doppler, validate token format:

```bash
# Check token format, length, prefix
python3 -c "token = 'TOKEN_VALUE'; print(f'Prefix: {token[:20]}...'); print(f'Length: {len(token)}')"
```

**Common token formats**:

- PyPI: `pypi-...` (179 chars)
- GitHub: `ghp_...` (40+ chars)
- AWS: 20-char access key + 40-char secret

### Step 2: Add Secret to Doppler

```bash
doppler secrets set SECRET_NAME="value" --project PROJECT --config CONFIG
```

**Example**:

```bash
doppler secrets set PYPI_TOKEN="pypi-AgEI..." \
  --project private-config --config prd
```

**Important**: CLI doesn't support `--note`. Add notes via dashboard:

1. <https://dashboard.doppler.com>
2. Navigate: PROJECT → CONFIG → SECRET_NAME
3. Edit → Add descriptive note

### Step 3: Validate Storage

Use the bundled validation script:

```bash
/usr/bin/env bash << 'VALIDATE_EOF'
ROOT="$(cc-plugin-root devops-tools)"
cd "$ROOT/skills/doppler-secret-validation"
uv run scripts/validate_secret.py \
  --project PROJECT \
  --config CONFIG \
  --secret SECRET_NAME
VALIDATE_EOF
```

This validates:

1. Secret exists in Doppler
2. Secret retrieval works
3. Environment injection works via `doppler run`

**Example**:

```bash
uv run scripts/validate_secret.py \
  --project private-config \
  --config prd \
  --secret PYPI_TOKEN
```

### Step 4: Test API Authentication
````
END THIRD-PARTY FILE 9241700eb1b7f85d

The third-party file has ended. Everything between the 9241700eb1b7f85d tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2294 of 7187 bytes. © terrylica · MIT · https://github.com/terrylica/cc-skills/tree/HEAD/plugins/devops-tools/skills/doppler-secret-validation/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
