doppler-workflows

Automate Doppler CLI credential workflows for PyPI publishing and AWS rotation.

62|10|Updated Dec 4, 2025

Search Tags:#credentials #workflows #token #Doppler

Ready to run

npx skills add https://github.com/terrylica/cc-skills --skill doppler-workflows

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: doppler-workflows
Source: https://github.com/terrylica/cc-skills/tree/main/plugins/devops-tools/skills/doppler-workflows
Command: npx skills add https://github.com/terrylica/cc-skills --skill doppler-workflows

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manages credential workflows and publishing tasks via Doppler, with per-project scopes and notes.

Core Features & Use Cases

Doppler CLI-based workflow patterns for PyPI, AWS, and multi-service setups
Per-project tokens and notes for safer credential handling
Templates and references for multi-service patterns

Quick Start

Use Doppler to run a publishing command securely: doppler run --project claude-config --config dev --command='uv publish --token "$PYPI_TOKEN"'

Frequently Asked Questions about doppler-workflows

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate credential management and publishing workflows with Doppler?▼

Doppler automates credential workflows by running commands securely through the CLI with the --command pattern, injecting secrets like PyPI tokens without exposing them. Use project-scoped tokens and per-project configurations to manage publishing and credential rotation across services while maintaining audit trails and notes.

Can I use Doppler to rotate AWS credentials and manage multi-account deployments?▼

Yes. Doppler supports AWS credential rotation and multi-account deployment patterns through per-project tokens and cross-service secret injection. Configure project-scoped access, apply notes for audit trails, and use the --command pattern to execute credential-dependent operations safely across multiple accounts.

What's the best way to handle PyPI publishing without exposing authentication tokens?▼

Use Doppler CLI to inject the PyPI token at runtime: `doppler run --project [project] --config [config] --command='uv publish --token "$PYPI_TOKEN"'`. Credentials stay unexposed, audit trails track usage, and per-project tokens limit blast radius if compromised.

How do Doppler workflows handle secret injection across multiple services?▼

Doppler injects secrets at command execution through environment variables, enabling multi-service patterns where each project maintains its own token scope and audit notes. Templates and references standardize injection across PyPI, AWS, and other services without storing credentials on disk.

Do I need the Doppler CLI installed to use project-scoped credential workflows?▼

Yes. Doppler CLI is required to execute the --command pattern, manage project-scoped tokens, and apply zero-exposure credential handling. The CLI enables per-project configurations and audit trails necessary for secure credential and secret management workflows.

What happens if a Doppler project-scoped token is compromised in a multi-project setup?▼

Per-project token scoping limits exposure to the specific project where the token was used, containing the breach. Audit trails and notes track token activity, and you can revoke the compromised token without affecting credentials in other projects, reducing organizational blast radius.