doppler-secret-validation

# 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 claude-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 ### ...