gcloud skill
✓ VerifiedOperate Google Cloud and Firebase CLIs to manage accounts, projects, IAM, APIs, billing, and logs.
- GitHub stars
- 13
- Files
- 2
- Last commit
- Nov 11, 2026
- License
- MIT
- Allowed tools
- —
What does the gcloud skill do?
gcloud is an agent skill. Operate Google Cloud and Firebase CLIs to manage accounts, projects, IAM, APIs, billing, and logs.
Summary generated from the skill's SKILL.md.
About the gcloud skill
Managing Google Cloud and Firebase environments through command line interfaces is the primary function of this skill. Developers use it to control accounts, projects, IAM permissions, APIs, billing, and logs. An agent should load this tool when it needs to perform infrastructure tasks, audit configurations, or query logs using the gcloud and firebase commands.
The skill prioritizes safety by requiring explicit approval for mutations like API enablement, IAM changes, or production edits. It emphasizes read-only operations using filters and limits to scope queries. When performing actions, the tool relies on specific flags such as --configuration, --account, and --project to ensure commands are pinned to the correct context. It also includes the ability to search Google developer documentation and vendor skills via the google-developer guide.
What an agent can do with it
- 1Audit cloud configurationsVerify the active identity, scope, and project details to ensure the correct environment is being accessed.
- 2Search technical documentationFind specific Google developer documentation or vendor skills across Cloud, Ads, Analytics, and Identity.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the gcloud skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the gcloud skill in Claude Code
~/.claude/skills/gcloud/SKILL.md
$ npx degit fmind/dot/skills/gcloud ~/.claude/skills/gcloudInstall the gcloud skill in Claude Code (project)
.claude/skills/gcloud/SKILL.md
$ npx degit fmind/dot/skills/gcloud .claude/skills/gcloudInstall the gcloud skill in Codex
~/.agents/skills/gcloud/SKILL.md
$ npx degit fmind/dot/skills/gcloud ~/.agents/skills/gcloudInstall the gcloud skill in Gemini CLI
~/.gemini/skills/gcloud/SKILL.md
$ npx degit fmind/dot/skills/gcloud ~/.gemini/skills/gcloudInstall the gcloud skill in Claude.ai
npx degit fmind/dot/skills/gcloud gcloud && zip -r gcloud.zip gcloud # claude.ai → Customize → Skills → + → Create skill → Upload a skill → gcloud.zip
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work · What to fix for more points
- Source repository linked and reachablefmind/dot/skills/gcloud is public and reachablegithub.com/fmind/dot/tree/HEAD/skills/gcloud ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-11github.com/fmind/dot/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/fmind/dot/blob/HEAD/skills/gcloud/SKILL.md ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/fmind/dot/blob/HEAD/skills/gcloud/SKILL.md ↗Pass
- SKILL.md follows the Agent Skills formatthe description does not say when to use the skillgithub.com/fmind/dot/blob/HEAD/skills/gcloud/SKILL.md ↗Finding
SKILL.md
View on GitHubGoogle Cloud CLI
Operate Google Cloud accounts, projects, IAM, APIs, billing, and logs with gcloud and firebase.
Defaults
Google Cloud is the default cloud for Fmind work (existing project choices win). Resolve project and region from explicit config or ask; prefer Cloud Run over GKE unless Kubernetes is explicitly adopted.
Workflow
-
Verify active identity and scope (never switch configurations silently to force a command through):
gcloud config configurations list --format='table(name,is_active)' gcloud config configurations describe <configuration> --format=json gcloud config get auth/impersonate_service_account --configuration <configuration> gcloud config get auth/access_token_file --configuration <configuration> gcloud projects describe <project-id> --format='json(projectId,projectNumber,lifecycleState)' -
Pin consequential calls: pass
--configuration,--account,--project, and--billing-project(plus--impersonate-service-accountwhen approved). -
Start read-only and bounded: combine
--filter,--limit, and field-projected--format, scoping log queries by time and resource first (retain full IAM/config payloads when auditing completeness). -
Authorize mutations: API enablement, IAM, billing, deletions, and production edits require explicit approval.
Gotchas
--quietonly suppresses prompts: never treats an unapproved mutation as safe.- Check principal overrides:
CLOUDSDK_AUTH_IMPERSONATE_SERVICE_ACCOUNT,CLOUDSDK_AUTH_ACCESS_TOKEN_FILE, and--impersonate-service-accountreplace the active account. - Firebase reuses ADC: skip
firebase login, pass--project <id>and--json, and gatefirebase deploylike any mutation. - Linked BigQuery datasets (
type = "LINKED") inheritprojectReaders:google_logging_linked_datasetcarriesspecialGroup: projectReadersand rejects dataset-level IAM (HTTP 400); projectroles/bigquery.dataViewerorroles/viewergrants BigQuery reads regardless ofroles/logging.viewAccessor. - Failures are findings: report missing principals, denied permissions, or quota errors directly—never switch configs, widen IAM, mint keys, or shift billing projects unasked.
Task guides
- google-developer: Find Google developer docs and vendor skills (google/skills) across Cloud, Ads, Analytics, and Identity.
Official Skills
Upstream: google/skills (skills/cloud) via google-developer. Preview—never install—its colliding gcloud guardrail skill (name collisions).
Documentation
- gcloud reference · Authenticate for the gcloud CLI
- Releases: gcloud release notes
- Companion skills: cloud-run (deployment), infra-as-code (provisioned infrastructure).
Files in this skill
2gcloud skill questions
How do I install the gcloud skill in Claude Code?
Run npx degit fmind/dot/skills/gcloud ~/.claude/skills/gcloud. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the gcloud skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
How should I handle mutations like API enablement or IAM changes?
API enablement, IAM, billing, deletions, and production edits require explicit approval.