Skill

Cloud Ops & Credential Guard

Guides secure cloud ops including Firebase/Gemini credential setup, .env secrets management, deployment config, and auth incident triage without exposing keys.

Firebase

GCP

Bash

security

devops

npx claudepluginhub joshuarweaver/cascade-code-general-misc-2 --plugin jleechanorg-claude-commands

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Guide Claude in helping teammates configure and troubleshoot cloud integrations securely without exposing sensitive data.

SKILL.md

Similar Skills

gcp-setup

Interactively sets up GCP Cloud Build + Cloud Run infrastructure. Provisions APIs, Artifact Registry, service accounts, IAM, secrets, and triggers with security best practices.

20 files7 tools

ac-tools

cred-omega

36.4k

Discovers, classifies, protects, and governs API keys, tokens, secrets across code, git history, CI/CD, containers, VPS, logs; enforces least privilege, rotation, zero-exposure for providers like OpenAI, AWS, GCP.

antigravity-awesome-skills

secrets-management

Guides secure secrets management using Vault, AWS Secrets Manager, Azure Key Vault, environment variables, rotation, scanning tools, and CI/CD security. For implementing storage, rotation, leak prevention, credentials review.

2 files5 tools

security

Stats

Stars26

Forks4

Last CommitMay 2, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Cloud Ops & Credential Guard

Purpose

Guide Claude in helping teammates configure and troubleshoot cloud integrations securely without exposing sensitive data.

Trigger phrases

Questions about Firebase, Gemini, or other API credentials.
Requests for deployment environment setup or .env configuration.
Incident triage involving auth failures or clock drift.

Configuration checklist

Secrets handling
- Never commit real keys; store them in .env or platform secret managers.
- Reference .env.example for required variables; add new ones there before documenting publicly.
Firebase setup
- Place serviceAccountKey.json under a secure, ignored path (see .gitignore).
- Confirm Firestore project ID matches FIREBASE_PROJECT_ID in .env.
- Validate clock sync with ntpstat or timedatectl when auth tokens fail.
Gemini API
- Export GEMINI_API_KEY locally and in deployment secrets.
- For local tests, prefer mock adapters enabled via TEST_MODE=mock.
MCP/Claude bots
- Run ./claude_mcp.sh or ./start_game_mcp.sh after confirming .env values.
- Use ./kill_dev_server.sh to reset stale sockets before re-authenticating.

Troubleshooting flow

Collect error logs from latest_ci_logs.txt or service console.
Identify whether failures stem from missing env vars, expired tokens, or network restrictions.

Suggest verification commands:

grep KEY_NAME .env
ls -al ~/.config/gcloud
firebase login:list

Recommend safe remediation (reissue keys, rotate secrets, update .env), emphasizing not to paste secrets into chat.

Security reminders

Offer redacted examples when showing .env entries.
Encourage using mock services or feature flags during demos.
Verify .gitignore contains credential files before advising users to create them.
Point teammates to docs/security/ and README.md#configuration for full policies.

Response structure

Restate the issue in security-aware language.
Outline the checklist items relevant to the scenario.
Provide commands or file paths for verification.
Close with preventative tips (secret rotation cadence, access controls, etc.).