google-workspace

Gmail, Calendar, Drive, Docs, Sheets via gws CLI or Python.

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

77%

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

The body is a well-structured, highly actionable guide with executable commands, explicit JSON output contracts, and a sequenced OAuth workflow with validation and error-recovery loops. Its main weaknesses are a large inline API reference that could be split out and some sections that could be tightened.

Suggestions

Move the per-service Usage command reference into a separate references file (e.g. references/api-reference.md) and keep SKILL.md as an overview pointing to it, improving progressive disclosure.

Trim the Cloud Console walkthrough and the slash-command note to the essential steps to improve conciseness.

Consider splitting the OAuth setup into its own reference file so the main body leads with quick-start usage.

Dimension	Reasoning	Score
Conciseness	The body is dense with executable commands and JSON schemas and avoids explaining concepts Claude already knows, but the inline per-service API reference and the Cloud Console walkthrough could be tightened, fitting the 'mostly efficient but could be tightened' anchor.	2 / 3
Actionability	Every section provides fully executable `$GAPI`/`$GSETUP` commands with concrete flags, copy-paste examples, and an explicit per-command JSON output schema, matching the 'fully executable code/commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	OAuth setup is a clearly sequenced Steps 0–5 process with an explicit validation checkpoint (`--check` → AUTHENTICATED) and error-recovery feedback loops (expired code returns fresh_auth_url; 403 routes to the audience page), matching the score-3 anchor.	3 / 3
Progressive Disclosure	There is one well-signaled, one-level-deep reference (gmail-search-syntax.md, listed in References and invoked via skill_view), but the large inline per-service usage reference that could be a separate file fits the 'content that should be separate is inline' anchor.	2 / 3
	Total	10 / 12 Passed

Description

40%

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 identifies the target Google Workspace services and access method but omits any concrete actions or a 'Use when' trigger clause, capping completeness and specificity. It is a service list rather than a capability description.

Suggestions

Add concrete action verbs, e.g. 'Search and send Gmail, create/edit Calendar events, manage Drive files, read/write Sheets and Docs'.

Append an explicit trigger clause such as 'Use when the user needs to work with Gmail, Google Calendar, Drive, Sheets, or Docs.'

Include common synonyms (email, spreadsheet, documents) alongside the brand names to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description lists five Google products and an access mechanism ("via gws CLI or Python") but contains no concrete action verbs describing what the skill does, matching the 'vague or no actions' anchor rather than the score-2 anchor which requires 'some actions'.	1 / 3
Completeness	It answers 'what' (Google Workspace services via gws CLI/Python) but has no 'Use when...' trigger clause, and the guidelines explicitly cap completeness at 2 when explicit trigger guidance is missing.	2 / 3
Trigger Term Quality	It includes natural brand terms users say (Gmail, Calendar, Drive, Docs, Sheets) but lacks common synonym variations a user might say ("email", "spreadsheet", "documents"), fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	Naming specific Google products gives it a clear niche, but Gmail/email handling overlaps with the related himalaya skill, fitting the 'somewhat specific but could still overlap with similar skills' anchor rather than the distinct score-3 anchor.	2 / 3
	Total	7 / 12 Passed

Validation

81%

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 — 13 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: NousResearch/hermes-agent
Path: skills/productivity/google-workspace/SKILL.md
Commit: d0d116b

Reviewed: about 13 hours 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.