google-account-login

Sign a Google account into its own gws config dir and register it (tagged). Used by google-workspace-setup; runs the OAuth login + records the account.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/google/google-account-login/SKILL.md

Quality

Content

87%Weight 40%Scale 1-3

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

The body is concise, highly actionable, and well-structured with a real one-level-deep script reference. The main gap is workflow clarity: the multi-step login flow is described narratively without explicit validation checkpoints in the body.

Suggestions

Convert the login flow into an explicit numbered sequence with a validation checkpoint (e.g. confirm session validity before registering) so workflow_clarity can reach 3.

Make the fail-fast expectedEmail check an explicit workflow step rather than only an argument description.

Add a short retry/recovery note for the listed failure reasons (e.g. what to do when "Login did not produce a valid session").

Dimension	Reasoning	Score
Conciseness	The body is lean and operational — it skips concepts Claude already knows (no "what is OAuth" padding) and every section (invocation, args, result, failures) earns its tokens, matching the "lean and efficient; assumes Claude's competence" anchor.	3 / 3
Actionability	It provides a concrete, copy-paste-ready skill_run invocation block, a complete result JSON example, and exact failure error strings, so Claude knows precisely how to call it and what to expect back.	3 / 3
Workflow Clarity	The login flow is sequenced as prose (mint dir → gws auth login → confirm → register) but there are no explicit validation/retry checkpoints in the body itself; fail-fast behavior is noted only as an argument, leaving checkpoints implicit.	2 / 3
Progressive Disclosure	A concise ~40-line overview is cleanly split into sections and offloads implementation to scripts/account-login.ts (a confirmed real bundle file), a single well-signaled one-level-deep reference with no nested indirection.	3 / 3
	Total	11 / 12 Passed

Description

67%Weight 40%Scale 1-3

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

The description is specific and occupies a clear, low-conflict niche, but it lacks an explicit user-facing "Use when..." trigger and leans on technical jargon (gws) over natural keywords. Adding a natural trigger clause and softer terminology would lift completeness and trigger_term_quality.

Suggestions

Add an explicit "Use when..." clause stating the user intent that triggers this skill, so completeness can reach 3.

Replace or gloss the jargon "gws config dir" with natural phrasing a user would say (e.g. "sign a Google account in") to improve trigger term quality.

Mention common trigger variations users actually say ("log in a Google account", "add a Google account") alongside the technical terms.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions in a specific domain — "Sign a Google account into its own gws config dir and register it (tagged)" and "runs the OAuth login + records the account" — matching the anchor that lists several specific concrete actions rather than vague language.	3 / 3
Completeness	The what is explicit, but the when is only implied via "Used by google-workspace-setup" (who calls it) with no user-facing "Use when..." trigger, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Relevant terms appear ("Google account", "OAuth login") but "gws config dir" is technical jargon and common user phrasings like "log in to my Google account" are only partially covered, so it sits at "some relevant keywords but missing common variations".	2 / 3
Distinctiveness Conflict Risk	The niche is very specific — signing a Google account into its own gws config dir as part of a multi-account model — making it clearly distinguishable and unlikely to trigger the wrong skill.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: Open-Curiosity/gini-agent
Path: skills/google/google-account-login/SKILL.md
Commit: 6c5d85e

Reviewed: 12 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.