CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gcloud-auth-verification

Guidelines for identifying and resolving missing Google Cloud authentication and Application Default Credentials (ADC). Use this skill if `gcloud`, `bq`, `dataform`, or Python libraries return authentication errors.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary lean, action-oriented skill body: exact error strings, ready-to-run commands, an explicit credential-handling policy, and validation checkpoints on both ends of the login flow. The only notable defect is a formatting flaw — the Verification Step's decision branches collapsed into a single paragraph with literal asterisk bullets, which slightly muddies the workflow's branch logic.

Suggestions

Fix the Verification Step's broken bullet formatting: restore line breaks so 'If the output contains No credentialed accounts...' and 'If an account is listed but the user still receives a 403...' render as two distinct bullets rather than an inline asterisk-laden paragraph.

Clarify what to do when the active account is authenticated but lacks IAM roles, e.g., a concrete check like 'gcloud projects get-iam-policy' or a pointer to the IAM investigation step, to close the loop on the 403/IAM branch.

DimensionReasoningScore

Conciseness

The ~37-line body is pure operational guidance — exact error strings, three commands, and decision branches — with no concept explanations or padding, matching the lean/every-token-earns-its-place anchor rather than the 4 anchor which requires over-explanation to trim.

5 / 5

Actionability

Guidance is fully concrete and executable: copy-paste ready commands ('gcloud auth list', 'gcloud auth login', 'gcloud auth application-default login'), exact error messages to match against, and explicit directives like 'DO NOT attempt to fix the credentials via code. Credentials must be established by the user.'

5 / 5

Workflow Clarity

The verify -> branch -> correct -> re-verify sequence is present with validation checkpoints ('Before asking the user to log in, independently verify...', 'After the user confirms they have logged in, verify with: gcloud auth list'), but the Verification Step's bullet list lost its line breaks (literal '*' bullets run inline in one paragraph), obscuring the two decision branches and keeping it below a 5.

4 / 5

Progressive Disclosure

This is a simple single-purpose skill under 50 lines with no need for external references; per the rubric's simple-skill guideline, its well-organized sections (Common Error Messages, Verification Step, Corrective Action, Post-Login Verification) qualify for the top anchor.

5 / 5

Total

19

/

20

Passed

Description

82%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 well-formed description with an explicit and specific trigger clause, good natural tool-name keywords, and a distinct GCP-authentication niche. Its main weakness is specificity: it states only the two generic actions 'identifying and resolving' rather than enumerating the concrete capabilities the skill provides.

Suggestions

Enumerate the concrete actions the skill performs (e.g., verifying auth status with 'gcloud auth list', distinguishing IAM 403 errors from missing credentials, instructing users to run 'gcloud auth login' and 'gcloud auth application-default login') to raise specificity.

Add common error-phrase variations users would naturally say, such as '403 Access Denied', 'permission denied', or 'No credentialed accounts', to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('Google Cloud authentication and Application Default Credentials (ADC)') with two actions ('identifying and resolving'), matching the anchor for 1-2 concrete actions without comprehensive coverage; it does not list the several specific actions required for a 4.

3 / 5

Completeness

Both parts are explicit: the what ('identifying and resolving missing Google Cloud authentication and Application Default Credentials') and a concrete when clause naming specific tools and the error condition, matching the anchor that requires both with concrete trigger phrases rather than the 4 anchor where the when is less specific.

5 / 5

Trigger Term Quality

'Use this skill if gcloud, bq, dataform, or Python libraries return authentication errors' plus 'Application Default Credentials (ADC)' gives good natural keyword coverage including the ADC acronym, though common variations like '403', 'Access Denied', or 'permission denied' are absent, keeping it below a 5.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche (Google Cloud auth errors for gcloud/bq/dataform/Python libraries) with distinct tool-name triggers and minimal conflict risk against unrelated skills.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

saski/arnesto

Path

.agents/skills/gcloud-auth-verification/SKILL.md

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.