Name: google-workspace
Rating: 62.4 (1 reviews)
Author: membranedev

google-workspace

Google Workspace integration. Manage Users, Groups, Calendars, Drives, Mailboxs, Contacts. Use when the user wants to interact with Google Workspace data.

Quality

74%

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-workspace/SKILL.md

Quality

Content

75%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 highly actionable with executable commands and a clear connection-state workflow; its main weaknesses are a padded introductory paragraph and a broken step-numbering scheme.

Suggestions

Remove the 'Google Workspace is a suite of online productivity tools...' intro paragraph that restates common knowledge.

Fix the step labeling: rename '1b' to a properly numbered step and add the missing 'Step 2' anchor the text references.

Dimension	Reasoning	Score
Conciseness	The bulk is efficient (command blocks, flag tables), but the opening 'Google Workspace is a suite of online productivity tools...' paragraph and lines like 'so you can focus on the integration logic rather than auth plumbing' explain context Claude already knows and could be trimmed.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure, action search/run, and proxy requests, plus a flag table and a populated actions table covering the common cases.	5 / 5
Workflow Clarity	The connect-to-run sequence is clear with a strong state-machine (READY/BUILDING/CLIENT_ACTION_REQUIRED) and polling feedback loop, but the 'skip to Step 2' reference and '1b' heading have no matching 'Step 1'/'1a' labels, leaving a minor gap.	4 / 5
Progressive Disclosure	The body is well organized with clear section headers and no nested references, but the ~20-row Popular actions table is inlined rather than split into a reference file, which is a minor organization gap for a skill of this length.	4 / 5
	Total	16 / 20 Passed

Description

73%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 clear, distinct, and provides both a what and a when, but the action verb is generic and a typo ('Mailboxs') plus missing common synonyms (Gmail, email) keep it from the top tier.

Suggestions

Replace the single generic verb 'Manage' with 2-3 distinct concrete actions (e.g., 'Create and update users, manage groups, list calendar events').

Add common natural synonyms such as 'Gmail' or 'email' and correct 'Mailboxs' to 'Mailboxes'.

Tighten the 'when' clause with concrete triggers (e.g., 'Use when creating users, managing groups, or reading Google Workspace data').

Dimension	Reasoning	Score
Specificity	It names the domain plus multiple concrete entities ('Manage Users, Groups, Calendars, Drives, Mailboxs, Contacts') but relies on a single generic verb ('Manage') rather than enumerating distinct actions, so it sits at the 'names domain and 1-2 concrete actions' level rather than the 'several specific actions' level.	3 / 5
Completeness	It answers both 'what' ('Manage Users, Groups...') and 'when' ('Use when the user wants to interact with Google Workspace data'), but the trigger clause is generic and could name concrete scenarios like creating users or managing groups.	4 / 5
Trigger Term Quality	It includes natural terms users would say ('Users, Groups, Calendars, Drives, Contacts', 'Google Workspace') but misses common variations like 'Gmail', 'email', and 'sheets/docs', placing it just below comprehensive synonym coverage.	4 / 5
Distinctiveness Conflict Risk	'Google Workspace integration' is a clearly bounded niche with product-specific triggers, making overlap with unrelated skills minimal.	5 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/google-workspace/SKILL.md
Commit: f484c82

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