gcloud-secrets

Manage Google Cloud Secret Manager secrets for deployment and runtime environments.

Updated Nov 21, 2025
One-click install
npx skills add https://github.com/ColdstartLabs-ca/myimageupscaler.com --skill gcloud-secrets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gcloud-secrets
Source: https://github.com/ColdstartLabs-ca/myimageupscaler.com/tree/main/.claude/skills/gcloud-secrets
Command: npx skills add https://github.com/ColdstartLabs-ca/myimageupscaler.com --skill gcloud-secrets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Securely manage environment secrets in Google Cloud Secret Manager to avoid embedding sensitive values in code or config files.

Core Features & Use Cases

  • Secret creation, versioning, and retrieval from Google Cloud Secret Manager for deployment and runtime configurations.
  • Automatic mapping of secrets to environment files (e.g., .env.*) to prevent credential leakage.
  • Use cases include deploying applications across GCP, rotating credentials, and securely sharing secrets across services.

Quick Start

Set your gcloud account and project, then fetch the latest secrets into your environment files.

Frequently Asked Questions about gcloud-secrets

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

FAQPage Schema
How do I securely retrieve Google Cloud Secret Manager values for environment files?

Map Google Cloud Secret Manager values to environment files by fetching the latest secret versions and writing them into .env.* files. This prevents credential leakage and avoids embedding sensitive values in code or configuration.

Can I use gcloud CLI to rotate environment secrets across GCP projects?

Yes, you can use gcloud CLI to rotate environment secrets across GCP projects. The process manages secret versioning and retrieval for runtime environments, requiring correct project and account configuration alongside permission to access or rotate secrets.

Do I need specific gcloud permissions to fetch secrets for a CI/CD deployment pipeline?

Fetching secrets for a CI/CD deployment pipeline requires gcloud CLI access, correct project and account configuration, and explicit permission to access or rotate secrets within the target GCP project's Secret Manager.

What is the best way to prevent credential leakage when deploying applications across GCP?

The best way to prevent credential leakage when deploying across GCP is to use Secret Manager for environment-specific secret provisioning. This securely stores and automatically maps sensitive values to environment files rather than embedding them in code.