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

Low

Low-risk findings worth noting

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 content is a high-quality, executable skill body with strong command coverage, output contracts, and well-sequenced OAuth setup with validation and feedback loops; the main gap is that the large per-service CLI reference is inlined rather than split into a separate reference file.

Suggestions

Move the per-service command catalog (Gmail/Calendar/Drive/Sheets/Docs Usage sections) into a `references/cli-reference.md` and summarize the common cases inline, improving token efficiency on load.

Surface the daily-brief reference more prominently with an explicit "Use when..." trigger in the body, since it is currently a single bullet.

Add a brief "When gws is present vs absent" note linking the google_api.py fallback behavior so the two backend paths are discoverable rather than implied.

Dimension	Reasoning	Score
Conciseness	The body is largely executable commands with no padding of concepts Claude already knows; the only minor verbosity is the step-by-step setup prose, which earns its place for a non-interactive OAuth flow.	4 / 5
Actionability	Copy-paste ready `$GAPI` / `$GSETUP` commands cover every service with real flags, and a full "Output Format" section documents the JSON each command returns for the common cases.	5 / 5
Workflow Clarity	Setup is sequenced as Steps 0-5 with explicit `--check` validation checkpoints, error-recovery branches (403 access_denied, expired auth code, partial scopes), and a troubleshooting table providing validate-fix-retry feedback loops for destructive and batch operations.	5 / 5
Progressive Disclosure	References and scripts are listed with real one-level-deep files (verified: gmail-search-syntax.md, daily-brief.md, setup.py, google_api.py), but the bulk Gmail/Calendar/Drive CLI reference is inlined rather than split into a separate file, leaving minor organization gaps.	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 concisely names the covered services and implementation path, but it lists no concrete actions and lacks any "Use when" trigger guidance, which limits completeness and specificity.

Suggestions

Add concrete verbs to the description (e.g., "search and send Gmail, create Calendar events, manage Drive files, edit Sheets and Docs").

Append a "Use when..." trigger clause naming common user phrasings like email, calendar, spreadsheets, or shared Drive files.

Drop or de-emphasize "via gws CLI or Python" in favor of user-facing capabilities, since the implementation detail adds no trigger value.

Dimension	Reasoning	Score
Specificity	Names the Google Workspace domain ("Gmail, Calendar, Drive, Docs, Sheets") but states no concrete actions like search, send, create, or share; it only names the services and an implementation route ("via gws CLI or Python").	2 / 5
Completeness	Gives a clear "what" (the services and tooling) but has no "Use when..." trigger clause, so per the rubric guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	Includes natural product names users say (Gmail, Calendar, Drive, Docs, Sheets) but omits common phrasings and verbs like "email", "send mail", "my calendar", or file extensions.	4 / 5
Distinctiveness Conflict Risk	Targets a clear Google Workspace niche distinct from the email-only himalaya skill, with minor overlap risk only against other mail/calendar skills.	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: 6327930

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