gws-shared

gws CLI: Shared patterns for authentication, global flags, and output formatting.

Quality

48%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/gws-shared/SKILL.md

Quality

Discovery

32%

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 identifies a specific tool (gws CLI) and names three capability areas, but remains at a high level without concrete actions or explicit trigger guidance. It lacks a 'Use when...' clause, making it difficult for Claude to know when to select this skill. The term 'shared patterns' suggests this is a reference/utility skill but doesn't clarify its relationship to other skills.

Suggestions

Add a 'Use when...' clause specifying triggers, e.g., 'Use when the user asks about gws CLI commands, authentication setup, passing global flags, or formatting gws output.'

Replace 'shared patterns' with specific concrete actions, e.g., 'Configures OAuth and API key authentication for gws CLI, applies global flags like --project and --format, and formats command output as JSON or tables.'

Include natural keyword variations users might use, such as 'gws auth', 'gws login', 'gws --format', 'gws credentials', or 'gws command-line'.

Dimension	Reasoning	Score
Specificity	Names the domain ('gws CLI') and mentions some areas (authentication, global flags, output formatting), but these are categories rather than concrete actions. It doesn't list specific things like 'authenticate with OAuth tokens', 'format output as JSON or table', etc.	2 / 3
Completeness	Describes what at a high level ('shared patterns for authentication, global flags, and output formatting') but completely lacks any 'Use when...' clause or explicit trigger guidance. Per rubric guidelines, missing 'Use when' should cap completeness at 2, and the 'what' is also weak, so this scores a 1.	1 / 3
Trigger Term Quality	Includes 'gws CLI', 'authentication', 'global flags', and 'output formatting' which are somewhat relevant but fairly technical. Missing natural user phrases like 'gws command', 'login', 'auth', 'format output', or specific flag names users might ask about.	2 / 3
Distinctiveness Conflict Risk	'gws CLI' is a specific tool which helps with distinctiveness, but 'authentication' and 'output formatting' are very broad concepts that could overlap with other CLI tools or authentication-related skills. The 'shared patterns' framing is ambiguous about scope.	2 / 3
	Total	7 / 12 Passed

Implementation

64%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid shared reference skill that provides concrete CLI syntax, useful flag tables, and practical shell tips. Its main weaknesses are the inclusion of unnecessary community etiquette content, lack of explicit workflow sequences with validation checkpoints for destructive operations, and missing cross-references to service-specific skill files that would complete the progressive disclosure pattern.

Suggestions

Remove or significantly trim the 'Community & Feedback Etiquette' section — this is not actionable CLI guidance and wastes tokens on social norms Claude already understands.

Add a brief workflow example for a common destructive operation showing the sequence: dry-run → confirm → execute → verify output.

Add cross-references to service-specific skill files (e.g., 'For Drive operations see [DRIVE.md](DRIVE.md)') to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with good use of tables and code blocks, but the 'Community & Feedback Etiquette' section is unnecessary filler that Claude doesn't need instruction on (encouraging users to star repos, issue etiquette). The shell tips section is valuable but slightly verbose.	2 / 3
Actionability	Provides concrete, executable commands for authentication, specific flag syntax with descriptions, and real shell examples showing correct vs incorrect usage patterns. The CLI syntax template and flag tables are copy-paste ready.	3 / 3
Workflow Clarity	Security rules mention confirming before write/delete and preferring --dry-run, which is good. However, there's no explicit workflow sequence for common operations (e.g., authenticate → dry-run → execute → verify), and no validation/feedback loop for destructive operations beyond a brief mention of --dry-run.	2 / 3
Progressive Disclosure	Content is reasonably organized with clear section headers, but everything is inline in one file. The description says this is a 'shared reference' suggesting service-specific skills exist, but there are no explicit cross-references to them. The file could benefit from linking to service-specific skill files.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning

	Total	10 / 11 Passed

Repository: googleworkspace/cli
Commit: c7c6646

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