google-workspace-setup

One-time setup for gws: install, OAuth, scopes, auto-approve.

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/google/google-workspace-setup/SKILL.md

Quality

Content

77%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 content is highly actionable with a rigorously sequenced, validation-gated workflow and concrete error recovery — a strong operational runbook. Its main weakness is conciseness (length and some restated rules) and a lack of progressive disclosure, since the entire ~370-line body lives inline with no external reference files.

Dimension	Reasoning	Score
Conciseness	The body is dense and mostly earns its tokens with operational detail, but it is long (~370 lines) and repeats guidance — e.g. the 'always request all seven services' rule appears substantively in both Step 6 and Rule #7 — so it could be tightened.	2 / 3
Actionability	It provides exact, copy-paste-ready commands and tool invocations (gcloud flags, request_connector, skill_run with full args) plus specific recovery actions per error, matching the 'fully executable, copy-paste ready' anchor.	3 / 3
Workflow Clarity	A clear Step 0 → Step 8 sequence with explicit validation checkpoints (gws --version/gcloud --version, gcloud projects describe as a cheap probe, the Step 8 smoke test) and feedback loops for error recovery (invalid_client, RATE_LIMIT_EXCEEDED, PERMISSION_DENIED), matching the top anchor.	3 / 3
Progressive Disclosure	Sections are well-organized with clear headers, but everything is inline in a single long SKILL.md with no bundle files; the services/scope reference table and some edge-case material could be split into a one-level-deep reference, matching 'some structure but content that should be separate is inline'.	2 / 3
	Total	10 / 12 Passed

Description

35%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 compact and action-oriented but leans entirely on technical jargon ('gws', 'OAuth', 'scopes', 'auto-approve') with no natural user-facing trigger terms or explicit 'Use when' guidance. It answers 'what' tersely but not 'when' explicitly.

Suggestions

Lead with the user-facing product name, e.g. 'Set up Google Workspace (Gmail, Calendar, Drive, Docs, Sheets, Meet, Forms) for the first time: install gws, OAuth, scopes, auto-approve.'

Add an explicit trigger clause: 'Use when the user first asks to read mail, check calendar, or share Drive files and Google Workspace isn't configured yet.'

Replace jargon-only triggers with natural phrases users actually say ('connect my Google account', 'set up Gmail/Calendar/Drive').

Dimension	Reasoning	Score
Specificity	Names the domain ('gws' setup) and lists several actions ('install, OAuth, scopes, auto-approve'), but they are terse abbreviations rather than fully concrete actions, matching the 'names domain and some actions but not comprehensive' anchor.	2 / 3
Completeness	It states what the skill does ('One-time setup for gws...') but offers no 'Use when...' trigger clause, so the 'when' is only implied — capping completeness at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	The terms present ('gws', 'OAuth', 'scopes', 'auto-approve') are technical jargon a user would not naturally say; notably 'Google Workspace' itself is absent, so natural keyword coverage is missing.	1 / 3
Distinctiveness Conflict Risk	The one-time setup niche is fairly specific, but because triggers rely on 'gws' jargon and never name Google Workspace/Gmail, it could still overlap with other setup skills.	2 / 3
	Total	7 / 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-workspace-setup/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.