gcloud

Guide for implementing Google Cloud SDK (gcloud CLI) - a command-line tool for managing Google Cloud resources. Use when installing/configuring gcloud, authenticating with Google Cloud, managing projects/configurations, deploying applications, working with Compute Engine/GKE/App Engine/Cloud Storage, scripting gcloud operations, implementing CI/CD pipelines, or troubleshooting Google Cloud deployments.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./claude/skills/gcloud/SKILL.md

Quality

Content

55%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.

The skill is highly actionable with comprehensive executable examples, but it is far too verbose for a SKILL.md, over-explains familiar concepts, inlines material that belongs in reference files, and the one provided reference file is never linked from the body. Batch/destructive workflows also lack explicit validation checkpoints.

Suggestions

Move the bulk command catalogs and quick-reference tables into reference files under ./references/ and link them from a concise SKILL.md overview, keeping only the highest-signal quick-start inline.

Remove concept primers Claude already knows (what authentication vs authorization means, command-structure anatomy) and keep only gcloud-specific gotchas.

Add explicit validation/feedback-loop steps to destructive and batch workflows (e.g. verify an instance is gone before recreating, confirm operations.wait before declaring bulk-create success).

Dimension	Reasoning	Score
Conciseness	The ~900-line body is noticeably verbose: it explains concepts Claude already knows (e.g. 'Authentication (Who you are)', 'Authorization (What you can do)', command-structure primers) and reproduces large command catalogs and quick-reference tables that mostly duplicate official docs.	2 / 5
Actionability	Provides extensive copy-paste-ready bash/yaml examples across install, auth, compute, GKE, storage, App Engine, Cloud Run, scripting, and CI/CD, with real flags and concrete values covering the common cases.	5 / 5
Workflow Clarity	Commands are organized into topical sections with some sequences (e.g. the idempotent validate-before-create pattern, retry loop), but batch and destructive operations (bulk instance creation, cluster deletion, key deletion) lack explicit validation checkpoints and feedback loops, capping the score per the destructive/batch guidance.	3 / 5
Progressive Disclosure	A single references/detailed-guides.md file exists and is not linked from the body, while ~900 lines of inlined command reference and quick-reference tables that belong in separate files stay in SKILL.md; structure is present but bulk content is not split out and references are not signaled.	3 / 5
	Total	13 / 20 Passed

Description

80%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, well-structured description that names the tool, its domain, and an explicit set of trigger conditions in third person. It is comprehensive and largely free of fluff, though the long enumeration could be tightened and a few natural trigger synonyms added.

Suggestions

Trim the 'Use when' enumeration to the highest-signal triggers and group the rest, reducing the list-of-11 feel without losing coverage.

Add common synonyms and shorthand users say (e.g. 'gcloud CLI', 'GCP CLI', 'Google Cloud commands') alongside 'gcloud'.

Lead the description with the core 'what' before the long trigger list so the capability is graspable in the first clause.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions (installing/configuring, authenticating, managing projects/configurations, deploying, scripting, CI/CD, troubleshooting), though they are delivered as a high-level enumeration rather than fully granular operations, leaving minor coverage gaps.	4 / 5
Completeness	Clearly states what the skill does and provides an explicit 'Use when ...' clause enumerating trigger scenarios; the 'when' is comprehensive but somewhat list-like rather than sharply targeted.	4 / 5
Trigger Term Quality	Includes many natural user-facing phrases ('installing/configuring gcloud', 'authenticating with Google Cloud', 'deploying applications', 'CI/CD pipelines'), but lacks some common synonyms and the literal product shorthand users might say.	4 / 5
Distinctiveness Conflict Risk	Scoped to the gcloud CLI for Google Cloud with specific service names, making it largely distinct from other skills; only minor overlap risk with broader cloud-devops skills.	4 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (900 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: einverne/dotfiles
Path: claude/skills/gcloud/SKILL.md
Commit: 651d4ea

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.