CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

google-workspace

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

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

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

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.

This is a strong, highly operational skill body: complete executable commands for every service, expected JSON outputs, a validated multi-step OAuth workflow with error-recovery loops, and real well-signaled bundle references. Its only weaknesses are mild verbosity in the setup prose and an inline API reference that could be partially split into reference files. The safety rules around destructive operations are a notable strength.

DimensionReasoningScore

Conciseness

The body is dense with executable commands, exact flags, expected outputs, and error strings, with essentially no explanation of concepts Claude already knows. Minor instances of over-explanation could be trimmed — the Step 1 triage questions and the Step 3 agent rules are wordier than needed — fitting anchor 4 ('Efficient; minor instances of over-explanation that could be trimmed') rather than anchor 5's 'every token earns its place'.

4 / 5

Actionability

Every section provides copy-paste-ready commands: '$GAPI gmail search "is:unread" --max 10', '$GSETUP --client-secret /path/to/client_secret.json', full create/update/share examples per service, plus a JSON output schema section and a troubleshooting table keyed to exact error strings. This matches anchor 5 ('Fully executable; copy-paste ready code or commands; specific examples cover the common cases').

5 / 5

Workflow Clarity

The setup is a clearly sequenced Steps 0-5 workflow with explicit validation checkpoints ('$GSETUP --check' → 'AUTHENTICATED' at both entry and completion) and genuine feedback loops for error recovery ('Error 403: access_denied' → add test user; expired auth code → 'fresh_auth_url' retry). Destructive operations are guarded by Rule 1 confirmation and the trash-default over '--permanent'. This matches anchor 5 ('Clear sequence with explicit validation steps; feedback loops for error recovery').

5 / 5

Progressive Disclosure

The bundle structure is well used: two real one-level-deep reference files (references/gmail-search-syntax.md, references/daily-brief.md) are listed with descriptions and explicit load triggers ('Load it when the user asks for a morning brief...'), and scripts are inventoried with roles. However, the ~150-line inline Usage/Output Format API reference for six services is substantial content that could partly live in reference files, fitting anchor 4 ('most content is appropriately placed; minor organization gaps') rather than anchor 5's 'content appropriately split'.

4 / 5

Total

18

/

20

Passed

Description

36%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 is a bare service list: it names the right Google products but gives no capabilities, no actions, and no usage triggers. Its main value is the five natural product-name keywords; everything else a description should communicate is missing. It would rarely trigger incorrectly, but it would also rarely trigger at all without explicit 'use when' guidance.

Suggestions

Add concrete actions to the description, e.g. 'Search, read, send, and reply to Gmail; create and list Calendar events; upload, download, search, and share Drive files; read and write Sheets and Docs.'

Add an explicit trigger clause, e.g. 'Use when the user asks to check or send email, manage calendar events or meetings, or work with files in Google Drive, Sheets, or Docs.'

Include common synonyms users say — 'email', 'meetings', 'spreadsheets', 'Google Workspace' — and a differentiator from the himalaya skill (e.g. note this is the full Google Workspace skill, not the lightweight email-only one).

DimensionReasoningScore

Specificity

The description names five concrete service domains ("Gmail, Calendar, Drive, Docs, Sheets") but states no actions at all — it never says what it does with them (read, send, create, share). This matches anchor 2 ('Names the domain but actions are minimal or generic'); it is below anchor 3, which requires 1-2 concrete actions, and above anchor 1 because the product names are concrete rather than abstract.

2 / 5

Completeness

There is no 'when to use' guidance at all, which caps completeness at 3, and the 'what' is itself vague — it is a list of service names plus an implementation detail ("via gws CLI or Python") rather than a statement of capabilities. It is weaker than anchor 3's clear action-based 'what', matching anchor 2 ('Has a vague what and no when').

2 / 5

Trigger Term Quality

"Gmail", "Calendar", "Drive", "Docs", and "Sheets" are natural terms users would actually say, but common variations and synonyms are missing ("email", "meetings", "spreadsheets", "files", "Google Workspace"), and "gws CLI" is technical jargon users would not say. This sits between anchors 3 and 4; the number of missing variations is more than 'a few', so it fits anchor 3 ('missing common variations or synonyms') better than anchor 4.

3 / 5

Distinctiveness Conflict Risk

The Google-suite focus gives it a recognizable niche, but the skill body itself reveals a direct overlap: a sibling email skill ('himalaya') also handles Gmail, and nothing in the description differentiates when to trigger this skill versus that one. This fits anchor 3 ('Somewhat specific but could still overlap with similar skills') rather than anchor 4, which requires only minor overlap with closely related skills.

3 / 5

Total

10

/

20

Passed

Validation

81%

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

CriteriaDescriptionResult

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

Reviewed

Table of Contents

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.