google-workspace

Google Workspace CLI operations: setup diagnostics, security audit, recipe discovery, and output analysis. Usage: /google-workspace <setup|audit|recipe|analyze> [options]

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

76%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 concrete, executable commands and a clean sectioned structure, but it reads as a command catalog rather than a sequenced workflow and lacks validation checkpoints for batch/recipe-run operations. Repeated deeply nested paths add avoidable token cost.

Suggestions

Add a brief recommended workflow with validation checkpoints for 'recipe run' (e.g., 'describe -> dry-run -> verify output -> run') to lift workflow clarity above the destructive/batch cap.

Define the long script path once as a variable or short alias and reuse it, instead of repeating 'engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/...' on every line.

Convert the Scripts and Skill Reference entries into clean relative links to bundled files so progressive disclosure reaches a one-level-deep local reference structure.

Dimension	Reasoning	Score
Conciseness	The body is lean and free of concept over-explanation, relying on command listings and examples; not a 5 because the long nested path 'engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/...' is repeated verbatim many times and the Usage and Subcommands sections re-enumerate the same commands, adding token cost that could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready commands with full interpreter paths, flags, and a worked Examples block covering the common cases (e.g., '/google-workspace audit --services gmail,drive --json', 'recipe run standup-report --dry-run'); fully executable guidance.	5 / 5
Workflow Clarity	The body is a subcommand reference rather than a sequenced workflow, and operations like 'recipe run' (batch/possibly destructive) and 'audit' lack explicit validation checkpoints or feedback loops, so per the rubric cap workflow clarity stays at 3; not a 2 because the subcommands are individually well-defined and a --dry-run safety flag is surfaced.	3 / 5
Progressive Disclosure	Clear sectioned overview (Usage, Examples, Scripts, Subcommands) with one-level-deep, clearly signaled references to script paths and a linked SKILL.md; not a 5 because the referenced files are deeply nested external paths rather than a local bundle (no ./scripts, ./references present) and the Scripts section inlines raw paths instead of clean reference links.	4 / 5
	Total	16 / 20 Passed

Description

58%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 clearly states what the skill does and lists concrete capabilities, but it omits any "Use when..." trigger guidance, which caps completeness and limits trigger-term quality. It is distinctive but would benefit from explicit user-facing trigger phrases.

Suggestions

Add a 'Use when...' clause naming natural user phrases (e.g., 'Use when the user asks to audit Google Workspace security, run a gws recipe, or analyze gws JSON output').

Include common synonyms and product names users say (e.g., 'Gmail, Drive, Calendar admin', 'gws CLI') to improve trigger-term coverage.

Soften jargon like 'recipe discovery' with plain-language equivalents so non-expert users can trigger the skill naturally.

Dimension	Reasoning	Score
Specificity	Names the domain ("Google Workspace CLI operations") and lists four concrete actions — "setup diagnostics, security audit, recipe discovery, and output analysis" — giving several specific actions with only minor coverage gaps; not a 5 because the actions are terse and not fully comprehensive.	4 / 5
Completeness	A clear "what" is present (the four operation types) but there is no "Use when..." clause or equivalent trigger guidance, so per the rubric guideline completeness is capped at 3; not a 2 because the "what" is explicit rather than vague.	3 / 5
Trigger Term Quality	Relevant keywords appear ("Google Workspace", "security audit", "setup") but common user phrasings and synonyms are missing and "recipe discovery" is CLI-specific jargon rather than natural user speech; not a 4 because natural-term coverage is incomplete.	3 / 5
Distinctiveness Conflict Risk	"Google Workspace CLI operations" is a clearly scoped niche with distinct triggers and low overlap risk; not a 5 because the absence of explicit trigger phrases leaves minor ambiguity versus closely related admin skills.	4 / 5
	Total	14 / 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: alirezarezvani/claude-skills
Path: .gemini/skills/google-workspace/SKILL.md
Commit: 19392f7

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