Google Cloud Developer Onboarding
Prepares an individual developer’s first Google Cloud project, billing setup, authentication, and initial deployment path.
The skill includes preflight audits, a project-creation consent gate, and enterprise-account routing, showing awareness of permissions and external effects. Points are deducted because least-privilege IAM scope, sensitive payment-data handling, data-flow disclosure, and complete rollback are not specified; billing linkage for an existing project lacks an equally explicit final confirmation gate.
The command sequence and abnormal routing are mostly specified, with JSON diagnostics and validation commands. Points are deducted because the non-interactive positioning conflicts with gcloud auth login and the single-question interaction policy, the billing-link command omits the mandated --quiet flag, random project-ID recovery is not reproducible, and no committed tests or standardized failure messages are provided.
The intended audience, first-time individual-developer scenario, and exclusions for enterprise or complex multi-project setups are reasonably clear. Points are deducted because coverage is limited to a singleton happy path, account classification relies on assumptions, Chinese-language guidance is absent, and core functionality depends on Google Cloud services without discussing mainland-China network reachability.
The document is well layered across preflight, authentication, project, billing, and validation sections; the repository provides Apache-2.0 licensing, installation instructions, maintenance status, and an issue path. Points are deducted because the skill has no skill-level version, changelog, named maintenance owner, FAQ, dependency versions, or systematic troubleshooting guidance.
The skill offers an actionable path from gcloud checks through project selection, billing verification, and downstream routing, covering most core onboarding steps. Points are deducted because the stated first-resource deployment is delegated rather than completed here, billing and cost-control details are incomplete, and static source material cannot verify directly usable results.
Commands, validation steps, and links to official documentation make the core process somewhat auditable. Points are deducted because there is no committed test suite, CI coverage, real execution record, or cross-source corroboration, so higher static verifiability scores are not justified.
- Add explicit confirmation of the project, billing account, and cost impact before linking billing to an existing project.
- Project creation and billing linkage change external state and may incur charges; no complete rollback procedure is provided, and disabling billing may terminate project services and usage.
- The core flow depends on Google Cloud Console, authentication, and gcloud services; confirm service reachability in the user's network environment first.
- Resolve the contradictions between the non-interactive requirement, gcloud auth login, the interaction policy, and the missing --quiet flag.
What does this skill do, and when should you use it?
This skill provides a streamlined onboarding path for a singleton developer starting with Google Cloud. It checks the gcloud CLI and authentication state, distinguishes personal accounts from enterprise organizations, and guides project selection or creation. It then audits billing linkage and points toward cost controls and first-workload deployment. Enterprise organization setup and complex multi-project architectures are explicitly out of scope.
Runs commands including which gcloud, gcloud auth list, gcloud config get-value account, gcloud organizations list, gcloud projects list, gcloud billing projects describe, and gcloud billing accounts list. When needed, it directs the user to run gcloud auth login, sets or creates a project, and links an available Cloud Billing account. It finishes with diagnostic checks for CLI installation, identity, project existence, and billing linkage, while requiring audits before mutations and explicit consent before creating a new project.
- An individual developer is using Google Cloud for the first time and needs to verify local tooling and sign in.
- A developer has an existing trial or personal project and wants to reuse it as the default working project.
- A developer has no usable project and needs to create a personal workspace and connect billing.
- A developer is preparing to deploy a first Cloud Run or other Google Cloud workload and needs project and billing prerequisites checked.
What are this skill's strengths and limitations?
- Covers the individual developer path from authentication through project, billing, and deployment-readiness checks.
- Specifies pre-mutation audits, one-question-at-a-time interaction, and machine-parseable command output.
- Separates personal free-trial onboarding from enterprise organization scenarios.
- Limited to a singleton developer’s onboarding path; it does not cover enterprise organization setup or complex multi-project architectures.
- It can perform project and billing operations, so the user needs suitable account permissions and a valid payment method.
- The source does not document a test suite, platform validation scope, or client-specific compatibility testing.
How do you install this skill?
Run: npx skills add google/skills. The installer allows selection of individual skills from the repository; select skills/cloud/google-cloud-recipe-onboarding. The source does not document a specific destination folder or additional client configuration.
How do you use this skill?
Give a compatible Agent Skills client a request such as “I want to get started with Google Cloud.” The skill audits gcloud availability and authentication before handling project and billing steps. If gcloud is missing, it stops and directs the user to the gcloud skill or the official Google Cloud CLI installation guide.
How does this skill compare with similar options?
For a domain-verified enterprise organization, corporate landing zone, or multi-tenant project structure, the source directs users to the official Google Cloud Setup guided flow. If gcloud is missing, it directs users to the gcloud skill or the official Google Cloud CLI installation guide.