{
  "schemaVersion": "1.0",
  "item": {
    "slug": "gcp",
    "name": "Google Cloud",
    "source": "tencent",
    "type": "skill",
    "category": "开发工具",
    "sourceUrl": "https://clawhub.ai/ivangdavila/gcp",
    "canonicalUrl": "https://clawhub.ai/ivangdavila/gcp",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/gcp",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=gcp",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "SKILL.md"
    ],
    "primaryDoc": "SKILL.md",
    "quickSetup": [
      "Download the package from Yavira.",
      "Extract the archive and review SKILL.md first.",
      "Import or place the package into your OpenClaw setup."
    ],
    "agentAssist": {
      "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
      "steps": [
        "Download the package from Yavira.",
        "Extract it into a folder your agent can access.",
        "Paste one of the prompts below and point your agent at the extracted folder."
      ],
      "prompts": [
        {
          "label": "New install",
          "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
        },
        {
          "label": "Upgrade existing",
          "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
        }
      ]
    },
    "sourceHealth": {
      "source": "tencent",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-30T16:55:25.780Z",
      "expiresAt": "2026-05-07T16:55:25.780Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
        "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/gcp"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    },
    "downloadPageUrl": "https://openagent3.xyz/downloads/gcp",
    "agentPageUrl": "https://openagent3.xyz/skills/gcp/agent",
    "manifestUrl": "https://openagent3.xyz/skills/gcp/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/gcp/agent.md"
  },
  "agentAssist": {
    "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
    "steps": [
      "Download the package from Yavira.",
      "Extract it into a folder your agent can access.",
      "Paste one of the prompts below and point your agent at the extracted folder."
    ],
    "prompts": [
      {
        "label": "New install",
        "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
      },
      {
        "label": "Upgrade existing",
        "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "Cost Traps",
        "body": "Stopped Compute Engine VMs still pay for persistent disks and static IPs — delete disks or use snapshots for long-term storage\nCloud NAT charges per VM and per GB processed — use Private Google Access for GCP API traffic instead\nBigQuery on-demand pricing charges for bytes scanned, not rows returned — partition tables and use LIMIT in dev, but LIMIT doesn't reduce scan cost in prod\nPreemptible VMs save 80% but can be terminated anytime — only for fault-tolerant batch workloads\nEgress to internet costs, egress to same region is free — keep resources in same region, use Cloud CDN for global distribution"
      },
      {
        "title": "Security Rules",
        "body": "Service accounts are both identity and resource — one service account can impersonate another with roles/iam.serviceAccountTokenCreator\nIAM policy inheritance: Organization → Folder → Project → Resource — deny policies at org level override allows below\nVPC Service Controls protect against data exfiltration — but break Cloud Console access if not configured with access levels\nDefault Compute Engine service account has Editor role — create dedicated service accounts with least privilege\nWorkload Identity Federation eliminates service account keys — use for GitHub Actions, GitLab CI, external workloads"
      },
      {
        "title": "Networking",
        "body": "VPC is global, subnets are regional — unlike AWS, single VPC can span all regions\nFirewall rules are allow-only by default — implicit deny all ingress, allow all egress. Add explicit deny rules for egress control\nPrivate Google Access is per-subnet setting — enable on every subnet that needs to reach GCP APIs without public IP\nCloud Load Balancer global vs regional — global for multi-region, but regional is simpler and cheaper for single region\nShared VPC separates network admin from project admin — host project owns network, service projects consume it"
      },
      {
        "title": "Performance",
        "body": "Cloud Functions gen1 has 9-minute timeout — gen2 (Cloud Run based) allows 60 minutes\nCloud SQL connection limits vary by instance size — use connection pooling or Cloud SQL Auth Proxy\nFirestore/Datastore hotspotting on sequential IDs — use UUIDs or reverse timestamps for document IDs\nGKE Autopilot simplifies but limits — no DaemonSets, no privileged containers, no host network\nCloud Storage single object limit is 5TB — use compose for larger, parallel uploads for faster"
      },
      {
        "title": "Monitoring",
        "body": "Cloud Logging retention: 30 days default, _Required bucket is 400 days — create custom bucket with longer retention for compliance\nCloud Monitoring alert policies have 24-hour auto-close — incident disappears even if issue persists, configure notification channels for re-alert\nError Reporting groups by stack trace — same error with different messages creates duplicates\nCloud Trace sampling is automatic — may miss rare errors, increase sampling rate for debugging\nAudit logs: Admin Activity always on, Data Access off by default — enable Data Access logs for security compliance"
      },
      {
        "title": "Infrastructure as Code",
        "body": "Terraform google provider requires project ID everywhere — use google_project data source or variables, never hardcode\ngcloud commands are imperative — use Deployment Manager or Terraform for reproducible infra\nCloud Build triggers on push but IAM permissions on first run confusing — grant Cloud Build service account necessary roles before first deploy\nProject deletion has 30-day recovery period — but project ID is globally unique forever, can't reuse\nLabels propagate to billing — use consistent labeling for cost allocation: env, team, service"
      },
      {
        "title": "IAM Best Practices",
        "body": "Primitive roles (Owner/Editor/Viewer) are too broad — use predefined roles, create custom for least privilege\nService account keys are security liability — use Workload Identity, impersonation, or attached service accounts instead\nroles/iam.serviceAccountUser lets you run as that SA — equivalent to having its permissions, grant carefully\nOrganization policies restrict what projects can do — constraints/compute.vmExternalIpAccess blocks public VMs org-wide"
      }
    ],
    "body": "Google Cloud Production Rules\nCost Traps\nStopped Compute Engine VMs still pay for persistent disks and static IPs — delete disks or use snapshots for long-term storage\nCloud NAT charges per VM and per GB processed — use Private Google Access for GCP API traffic instead\nBigQuery on-demand pricing charges for bytes scanned, not rows returned — partition tables and use LIMIT in dev, but LIMIT doesn't reduce scan cost in prod\nPreemptible VMs save 80% but can be terminated anytime — only for fault-tolerant batch workloads\nEgress to internet costs, egress to same region is free — keep resources in same region, use Cloud CDN for global distribution\nSecurity Rules\nService accounts are both identity and resource — one service account can impersonate another with roles/iam.serviceAccountTokenCreator\nIAM policy inheritance: Organization → Folder → Project → Resource — deny policies at org level override allows below\nVPC Service Controls protect against data exfiltration — but break Cloud Console access if not configured with access levels\nDefault Compute Engine service account has Editor role — create dedicated service accounts with least privilege\nWorkload Identity Federation eliminates service account keys — use for GitHub Actions, GitLab CI, external workloads\nNetworking\nVPC is global, subnets are regional — unlike AWS, single VPC can span all regions\nFirewall rules are allow-only by default — implicit deny all ingress, allow all egress. Add explicit deny rules for egress control\nPrivate Google Access is per-subnet setting — enable on every subnet that needs to reach GCP APIs without public IP\nCloud Load Balancer global vs regional — global for multi-region, but regional is simpler and cheaper for single region\nShared VPC separates network admin from project admin — host project owns network, service projects consume it\nPerformance\nCloud Functions gen1 has 9-minute timeout — gen2 (Cloud Run based) allows 60 minutes\nCloud SQL connection limits vary by instance size — use connection pooling or Cloud SQL Auth Proxy\nFirestore/Datastore hotspotting on sequential IDs — use UUIDs or reverse timestamps for document IDs\nGKE Autopilot simplifies but limits — no DaemonSets, no privileged containers, no host network\nCloud Storage single object limit is 5TB — use compose for larger, parallel uploads for faster\nMonitoring\nCloud Logging retention: 30 days default, _Required bucket is 400 days — create custom bucket with longer retention for compliance\nCloud Monitoring alert policies have 24-hour auto-close — incident disappears even if issue persists, configure notification channels for re-alert\nError Reporting groups by stack trace — same error with different messages creates duplicates\nCloud Trace sampling is automatic — may miss rare errors, increase sampling rate for debugging\nAudit logs: Admin Activity always on, Data Access off by default — enable Data Access logs for security compliance\nInfrastructure as Code\nTerraform google provider requires project ID everywhere — use google_project data source or variables, never hardcode\ngcloud commands are imperative — use Deployment Manager or Terraform for reproducible infra\nCloud Build triggers on push but IAM permissions on first run confusing — grant Cloud Build service account necessary roles before first deploy\nProject deletion has 30-day recovery period — but project ID is globally unique forever, can't reuse\nLabels propagate to billing — use consistent labeling for cost allocation: env, team, service\nIAM Best Practices\nPrimitive roles (Owner/Editor/Viewer) are too broad — use predefined roles, create custom for least privilege\nService account keys are security liability — use Workload Identity, impersonation, or attached service accounts instead\nroles/iam.serviceAccountUser lets you run as that SA — equivalent to having its permissions, grant carefully\nOrganization policies restrict what projects can do — constraints/compute.vmExternalIpAccess blocks public VMs org-wide"
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/ivangdavila/gcp",
    "publisherUrl": "https://clawhub.ai/ivangdavila/gcp",
    "owner": "ivangdavila",
    "version": "1.0.0",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/gcp",
    "downloadUrl": "https://openagent3.xyz/downloads/gcp",
    "agentUrl": "https://openagent3.xyz/skills/gcp/agent",
    "manifestUrl": "https://openagent3.xyz/skills/gcp/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/gcp/agent.md"
  }
}