CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gemini-auth

Setup and manage Gemini CLI authentication methods including OAuth, API keys, and Vertex AI. Use when configuring Gemini access, switching auth methods, or troubleshooting authentication issues.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/gemini-auth/SKILL.md

The canonical home for this skill is gemini-auth in fernandezbaptiste/Skrillz

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 body delivers highly actionable, executable setup and troubleshooting guidance with verification steps for each auth method. Its weaknesses are structural: it is a ~450-line monolith whose CI/CD, Docker, audit, and usage-tracking sections extend beyond the stated authentication scope, and nothing is split into reference files. Some code details (placeholder functions, unexpanded quoted tildes) slightly reduce copy-paste reliability.

Suggestions

Split the SKILL.md into a lean overview and one-level-deep reference files (e.g., references/workflows.md for multi-account and rate-limit scripts, references/integrations.md for CI/CD and Docker, references/security.md for key storage and audit logging), keeping only the three auth setup paths and troubleshooting inline.

Trim or remove sections outside the stated authentication scope (usage tracking, audit logging alias, CI/CD and Docker examples) to reduce token cost and tighten conciseness.

Fix executable-code gaps: define or remove the undefined 'generate_new_key'/'revoke_old_key' placeholders in the rotation function, and remove quotes around tildes ('~/.gemini/usage.log', '~/gemini-sa-key.json') so paths expand correctly, and add a pre-check before the destructive 'rm -rf ~/.gemini/auth/tokens' remedy.

DimensionReasoningScore

Conciseness

The body is mostly dense, useful code with minimal concept explanation, but at ~450 lines it drifts well beyond the stated authentication scope (CI/CD pipeline, Docker integration, audit logging, usage tracking) — content that could be tightened or cut. Not 2 because there is no padded prose or over-explanation; not 4 because the scope creep and length mean many tokens don't serve the skill's stated purpose.

3 / 5

Actionability

Nearly all guidance is concrete and executable: 'gemini auth status', '.env' file creation with chmod, full gcloud service-account provisioning, curl key validation, and complete retry/rate-limit functions. Minor gaps: 'generate_new_key' and 'revoke_old_key' in the rotation function are undefined placeholders, and quoted tildes ('~/gemini-sa-key.json', '~/.gemini/usage.log') will not expand in bash, so not fully copy-paste ready (anchor 5).

4 / 5

Workflow Clarity

Each setup path is sequenced with verification checkpoints ('Verify (auto-execute test)', 'Test connection', retry with exponential backoff and explicit failure returns), and the Troubleshooting section provides per-method fix loops (token expired → refresh; key not found → check env/files/curl; Vertex → check IAM). Not 5 because some remedies lack pre-checks (e.g., 'rm -rf ~/.gemini/auth/tokens' is applied without first confirming the token is expired).

4 / 5

Progressive Disclosure

No bundle files exist and none are referenced — this is a well-sectioned but monolithic ~450-line SKILL.md where multi-account scripts, rate-limit management, audit logging, CI/CD, and Docker examples that clearly belong in separate reference files are fully inlined. Structure is present (better than anchor 2), but content that should be separate is inline, matching anchor 3.

3 / 5

Total

14

/

20

Passed

Description

83%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 description: it states what the skill does with enumerated auth methods and provides an explicit 'Use when' clause with concrete triggers. Keyword coverage is good but could add natural synonyms like 'login' and 'credentials', and the slightly broad 'configuring Gemini access' phrase leaves minor conflict risk with sibling Gemini skills.

DimensionReasoningScore

Specificity

Names the domain ('Gemini CLI authentication methods') and enumerates concrete methods ('OAuth, API keys, and Vertex AI') plus tasks like 'switching auth methods' and 'troubleshooting' — several specific actions with minor gaps (no mention of key rotation or rate limits). Not 5 because 'manage' is generic and coverage of the skill body's full scope is incomplete; not 3 because it goes beyond 1-2 actions with method-level enumeration.

4 / 5

Completeness

Explicitly answers both: what ('Setup and manage Gemini CLI authentication methods including OAuth, API keys, and Vertex AI') and when ('Use when configuring Gemini access, switching auth methods, or troubleshooting authentication issues') with concrete trigger phrases. Matches the anchor-5 pattern; the when-clause is explicit and specific, and the what is concrete and enumerated.

5 / 5

Trigger Term Quality

Includes natural terms users would say: 'Gemini CLI', 'authentication', 'OAuth', 'API keys', 'Vertex AI', 'configuring Gemini access', 'troubleshooting authentication issues'. A few natural synonyms are missing ('login', 'sign in', 'credentials', 'token'), which keeps it below the comprehensive-synonym anchor 5 but clearly above anchor 3.

4 / 5

Distinctiveness Conflict Risk

Tightly scoped to Gemini CLI authentication with auth-specific triggers, giving a clear niche. Minor overlap risk remains: 'configuring Gemini access' is slightly broad and could collide with closely related sibling skills (e.g., gemini-cli), which fits anchor 4 rather than the minimal-conflict anchor 5.

4 / 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

fernandezbaptiste/Skrillz

Path

.claude/skills/gemini-auth/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.