Use the gcloud CLI to manage Google Cloud Platform resources and services.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongcloudExecute the skills CLI command in your project's root directory to begin installation:
Fetches gcloud from dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate gcloud. Access via /gcloud in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
62
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
62
stars
Use the gcloud CLI to manage Google Cloud Platform resources and services.
Check current auth:
gcloud auth list
Login interactively:
gcloud auth login
Login with service account:
gcloud auth activate-service-account --key-file=key.json
Application default credentials:
gcloud auth application-default login
List projects:
gcloud projects list
Set default project:
gcloud config set project PROJECT_ID
Show current config:
gcloud config list
Create named configuration:
gcloud config configurations create my-config
gcloud config configurations activate my-config
Set default region/zone:
gcloud config set compute/region us-central1
gcloud config set compute/zone us-central1-a
List instances:
gcloud compute instances list
Create instance:
gcloud compute instances create my-vm \
--zone=us-central1-a \
--machine-type=e2-medium \
--image-family=debian-12 \
--image-project=debian-cloud
SSH to instance:
gcloud compute ssh my-vm --zone=us-central1-a
Stop/start instance:
gcloud compute instances stop my-vm --zone=us-central1-a
gcloud compute instances start my-vm --zone=us-central1-a
Delete instance:
gcloud compute instances delete my-vm --zone=us-central1-a
List services:
gcloud run services list
Deploy from source:
gcloud run deploy my-service --source . --region=us-central1
Deploy container:
gcloud run deploy my-service \
--image=gcr.io/PROJECT/IMAGE \
--region=us-central1 \
--allow-unauthenticated
View logs:
gcloud run services logs read my-service --region=us-central1
Update traffic split:
gcloud run services update-traffic my-service \
--to-revisions=LATEST=100 \
--region=us-central1
List functions:
gcloud functions list
Deploy function (2nd gen):
gcloud functions deploy my-function \
--gen2 \
--runtime=nodejs20 \
--region=us-central1 \
--trigger-http \
--entry-point=handler \
--source=.
View logs:
gcloud functions logs read my-function --region=us-central1
Delete function:
gcloud functions delete my-function --region=us-central1
List clusters:
gcloud container clusters list
Get credentials for kubectl:
gcloud container clusters get-credentials my-cluster \
--zone=us-central1-a
Create cluster:
gcloud container clusters create my-cluster \
--zone=us-central1-a \
--num-nodes=3
Resize node pool:
gcloud container clusters resize my-cluster \
--node-pool=default-pool \
--num-nodes=5 \
--zone=us-central1-a
List buckets:
gcloud storage buckets list
Create bucket:
gcloud storage buckets create gs://my-bucket --location=us-central1
List objects:
gcloud storage ls gs://my-bucket/
Copy files:
# Upload
gcloud storage cp local-file.txt gs://my-bucket/
# Download
gcloud storage cp gs://my-bucket/file.txt ./
# Recursive
gcloud storage cp -r ./local-dir gs://my-bucket/
Sync directory:
gcloud storage rsync -r ./local-dir gs://my-bucket/remote-dir
List instances:
gcloud sql instances list
Create instance:
gcloud sql instances create my-instance \
--database-version=POSTGRES_15 \
--tier=db-f1-micro \
--region=us-central1
Connect via proxy:
gcloud sql connect my-instance --user=postgres
Create database:
gcloud sql databases create mydb --instance=my-instance
List datasets:
bq ls
Run query:
bq query --use_legacy_sql=false 'SELECT * FROM dataset.table LIMIT 10'
Create dataset:
bq mk --dataset my_dataset
Load data:
bq load --source_format=CSV my_dataset.my_table gs://bucket/data.csv
List topics:
gcloud pubsub topics list
Create topic:
gcloud pubsub topics create my-topic
Publish message:
gcloud pubsub topics publish my-topic --message="Hello"
Create subscription:
gcloud pubsub subscriptions create my-sub --topic=my-topic
Pull messages:
gcloud pubsub subscriptions pull my-sub --auto-ack
List secrets:
gcloud secrets list
Create secret:
echo -n "my-secret-value" | gcloud secrets create my-secret --data-file=-
Access secret:
gcloud secrets versions access latest --secret=my-secret
Add new version:
echo -n "new-value" | gcloud secrets versions add my-secret --data-file=-
List service accounts:
gcloud iam service-accounts list
Create service account:
gcloud iam service-accounts create my-sa \
--display-name="My Service Account"
Create key:
gcloud iam service-accounts keys create key.json \
--iam-account=[email protected]
Add IAM binding:
gcloud projects add-iam-policy-binding PROJECT_ID \
--member="serviceAccount:[email protected]" \
--role="roles/storage.admin"
Submit build:
gcloud builds submit --tag gcr.io/PROJECT/IMAGE
List builds:
gcloud builds list
View build logs:
gcloud builds log BUILD_ID
List repositories:
gcloud artifacts repositories list
Configure Docker:
gcloud auth configure-docker us-central1-docker.pkg.dev
Read logs:
gcloud logging read "resource.type=cloud_run_revision" --limit=50
Tail logs:
gcloud logging tail "resource.type=gce_instance"
Deploy app:
gcloud app deploy
View logs:
gcloud app logs tail
Browse app:
gcloud app browse
Format as JSON:
gcloud compute instances list --format=json
Format as table with specific columns:
gcloud compute instances list --format="table(name,zone,status)"
Filter results:
gcloud compute instances list --filter="status=RUNNING"
Quiet mode (no prompts):
gcloud compute instances delete my-vm --quiet
Quick reference:
gcloud cheat-sheet
Interactive shell:
gcloud interactive
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations
dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations
davila7/claude-code-templates
wshobson/agents
dpearson2699/swift-ios-skills
jeffallan/claude-skills
gcloud is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
gcloud has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in gcloud — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend gcloud for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: gcloud is focused, and the summary matches what you get after install.
Solid pick for teams standardizing on skills: gcloud is focused, and the summary matches what you get after install.
I recommend gcloud for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in gcloud — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
gcloud has been reliable in day-to-day use. Documentation quality is above average for community skills.
gcloud fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 26