gog

Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.

Quality

68%

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

Quality

Content

65%

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 highly actionable command catalog with excellent copy-paste-ready examples, but it carries a non-essential migration note, lacks explicit validate-retry loops for destructive operations, and is a monolithic file that could offload reference material. It is strong on doing, weaker on structure and feedback.

Suggestions

Remove or relocate the 'PilotDeck Migration Note' section; it is review metadata that does not help Claude use the skill and adds noise to the context window.

Add an explicit validation/feedback step for destructive operations, e.g. after `gog gmail send` or `gog calendar create`, instruct Claude to confirm recipients/details first and verify success from the command output before proceeding.

Move the 11-row Calendar Colors hex table and the multi-line email examples into a `references/` file (e.g. `references/formatting.md`) referenced one level deep, keeping SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is a dense, mostly-efficient command reference where most tokens earn their place, but it is padded with the 'PilotDeck Migration Note' section — review/migration metadata irrelevant to using the skill — and an 11-row hex color table that is borderline bulk. It is tighter than verbose explanatory prose yet carries unnecessary context.	2 / 3
Actionability	It provides dozens of concrete, executable commands with real flags and two complete worked examples (a stdin heredoc send and an HTML list send), making the guidance copy-paste ready with specific details like --values-json shapes and --event-color IDs.	3 / 3
Workflow Clarity	Setup is clearly sequenced (auth credentials → add account → list) and the Notes add a 'Confirm before sending mail or creating events' checkpoint, but destructive/batch operations (sending mail, creating events, Sheets updates) lack an explicit validate→fix→retry feedback loop, which caps the score at 2.	2 / 3
Progressive Disclosure	The skill is a single monolithic ~100-line file with clear section headers but no external reference files; content that could be split out (the Calendar Colors table and the Email Formatting examples) is kept inline, so it is organized yet not appropriately divided.	2 / 3
	Total	9 / 12 Passed

Description

72%

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 specific and distinctive, naming a clear niche and the exact product names users would invoke, but it omits any explicit 'when to use' trigger guidance and lists no concrete actions. Adding a 'Use when...' clause with verb-based triggers would lift completeness and specificity.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to send or search Gmail, manage Calendar events, search Drive, list Contacts, or read/write Google Sheets/Docs.'

Replace the static product list with concrete actions (e.g. 'send and search email, create and update calendar events, search Drive, read and write Sheets, export Docs') to raise specificity from 2 to 3.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Google Workspace CLI') and enumerates six products (Gmail, Calendar, Drive, Contacts, Sheets, Docs), but states no concrete actions — there are no verbs like send, search, or create. It is more specific than vague ('Helps with documents') but stops short of the comprehensive action list required for a 3.	2 / 3
Completeness	It answers 'what' (a CLI for the Google Workspace services) but provides no 'Use when...' clause or equivalent explicit trigger guidance, which the rubric caps at 2. The 'when' is entirely implied.	2 / 3
Trigger Term Quality	It lists the exact product names (Gmail, Calendar, Drive, Contacts, Sheets, Docs) that users naturally mention when requesting these tasks, giving good coverage of natural trigger terms.	3 / 3
Distinctiveness Conflict Risk	'Google Workspace CLI' is a clear, distinct niche tied to a specific tool and product family, making it unlikely to trigger for the wrong skill.	3 / 3
	Total	10 / 12 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: OpenBMB/PilotDeck
Path: skills/gog/SKILL.md
Commit: c88d7d1

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