CtrlK
BlogDocsLog inGet started
Tessl Logo

google-cloud-recipe-onboarding

Guides a developer's first steps on Google Cloud, covering account creation, billing setup, project management, and deploying a first resource. Use when a new developer wants to initialize their first Google Cloud project, configure billing, and verify deployment. Don't use for enterprise organization setup (use Google Cloud Setup guided flow for that instead). Don't use for complex multi-project architectures.

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A thorough, highly actionable onboarding workflow with strong sequencing and validation feedback loops. Its main weakness is verbosity from restated guidance and explanation of Google Cloud concepts Claude already knows.

Suggestions

Remove the duplicated authentication/preamble guidance between the opening IMPORTANT block and Section 2 — state it once.

Trim conceptual explanations Claude already knows (Free Trial credit amount, what a Project is, what disabling billing does) down to the operational essentials.

Consider extracting the enterprise-organization routing logic into a short reference section or linked doc so the main happy path stays lean.

DimensionReasoningScore

Conciseness

Mostly actionable but noticeably verbose in places — the auth/preamble guidance is restated in both the opening IMPORTANT block and Section 2, and concepts like the $300 Free Trial, the Projects resource model, and Self-Owned vs enterprise organizations are explained at length Claude largely already knows.

3 / 5

Actionability

Provides real, copy-paste-ready gcloud commands with deterministic flags throughout ('which gcloud', 'gcloud auth login', 'gcloud projects create {PROJECT_ID} --name=... --quiet --format="json"', 'gcloud billing projects link ...'), covering the common onboarding cases.

5 / 5

Workflow Clarity

Five clearly sequenced sections plus a Validation Logic block, with explicit pre-mutation audits, a mandatory consent gate, and a collision→append-suffix→re-solicit-consent feedback loop for error recovery.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections (Overview, Prerequisites, Steps 1-5, Validation Logic, Additional Resources) with clearly signaled external doc links, but all content is inline in a single ~215-line file with no one-level-deep reference split.

4 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states both what the skill does and when to use it, with helpful negative boundary guidance. It could be improved by adding the most natural conversational trigger phrasing such as 'get started with Google Cloud'.

Suggestions

Add natural conversational trigger phrasing users would actually say, e.g. 'Use when someone says they want to get started with Google Cloud or sign up for their first project'.

Consider including the term 'gcloud' as a trigger keyword to match users who reference the CLI directly.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'account creation, billing setup, project management, and deploying a first resource' and 'initialize their first Google Cloud project, configure billing, and verify deployment' — giving comprehensive coverage of the onboarding scope.

5 / 5

Completeness

Explicitly answers both 'what' (account creation, billing setup, project management, deploying a first resource) and 'when' ('Use when a new developer wants to initialize their first Google Cloud project, configure billing, and verify deployment'), with concrete trigger phrases and negative boundaries.

5 / 5

Trigger Term Quality

Good keyword coverage ('Google Cloud', 'first steps', 'billing', 'project', 'deploy', 'onboarding') but misses common natural phrasings a user would actually say like 'get started with Google Cloud' or 'sign up'.

4 / 5

Distinctiveness Conflict Risk

Clear onboarding niche with explicit negative boundary guidance ('Don't use for enterprise organization setup', 'Don't use for complex multi-project architectures') routing overlaps elsewhere, minimizing conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
google/skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.