google-workspace

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

Quality

72%

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

88%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 is a strong, executable reference: copy-paste commands across all six services, a sequenced OAuth setup with validation and retry loops, and clear rules plus a troubleshooting table. The only gaps are minor setup-prose verbosity and a large inline command section that borders on belonging in its own reference file.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's competence throughout (no explanations of what Gmail or OAuth are) and is dominated by executable commands, with only minor prose in the triage and setup narrative that could be trimmed; it is not 5 because the Setup section's Q&A framing runs a little long.	4 / 5
Actionability	Every service section provides copy-paste-ready bash commands with realistic arguments covering the common cases (search, get, send, reply, create, upload, download, share), matching the fully-executable anchor.	5 / 5
Workflow Clarity	Setup is a clearly sequenced Step 0–5 flow with an explicit `--check` validation checkpoint, a retry feedback loop when `--auth-code` fails (fresh_auth_url), and Rule 1 requiring user confirmation before any destructive or batch operation, satisfying the validation requirement.	5 / 5
Progressive Disclosure	SKILL.md is an overview with well-signaled one-level-deep references (references/gmail-search-syntax.md, references/daily-brief.md) and a Scripts section; it is not 5 because the large inline per-service command reference in Usage could arguably live in a separate reference file.	4 / 5
	Total	18 / 20 Passed

Description

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

The description cleanly names the covered Google Workspace services and the execution backend, but it omits any concrete actions and any explicit "Use when" trigger guidance. Adding a verb list and a trigger clause would lift the capped completeness and specificity scores.

Suggestions

Add concrete action verbs, e.g. "Send and search Gmail, create and list Calendar events, upload and share Drive files, read and write Sheets, and create Docs"

Append an explicit trigger clause such as "Use when the user asks to manage Gmail, Calendar, Drive, Sheets, or Docs."

Mention natural synonyms (email, spreadsheets, files) alongside the product names to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The phrase "Gmail, Calendar, Drive, Docs, Sheets via gws CLI or Python" names five service domains and the execution mechanism, but includes no concrete action verbs (no send/read/create/upload), matching the score-2 anchor of naming the domain with minimal or generic actions.	2 / 5
Completeness	It gives a clear "what" (the five services via gws CLI or Python) but has no "Use when..." clause or explicit trigger guidance, so per the judging guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	The product names Gmail, Calendar, Drive, Docs, and Sheets are exactly the natural terms users say, giving good keyword coverage; it falls short of 5 because synonyms like "email", "spreadsheets", or file extensions are absent.	4 / 5
Distinctiveness Conflict Risk	The specific Google product names create a clear niche with distinct triggers and minimal conflict risk; it is not 5 because email-only needs could overlap with the related himalaya skill.	4 / 5
	Total	13 / 20 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: 6680afb

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