gws-admin-reports

Google Workspace Admin SDK: Audit logs and usage reports.

Quality

48%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/gws-admin-reports/SKILL.md

Quality

Content

57%

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

This skill provides a reasonable reference structure for the Admin Reports API with good progressive disclosure via the shared skill file. However, it suffers from verbose API descriptions that could be condensed, and critically lacks concrete executable examples showing common use cases like retrieving login audit logs or generating usage reports with specific parameters.

Suggestions

Add 2-3 concrete, copy-paste-ready examples showing common tasks (e.g., `gws admin-reports activities list --params '{"applicationName":"login","userKey":"all"}'`)

Trim the verbose API resource descriptions to single-line summaries (e.g., 'list — List activities for a customer account and application' instead of the current multi-sentence descriptions with repeated 'For more information' phrases)

Add a brief workflow for the watch/stop channel lifecycle, including validation that the watch was set up correctly

Dimension	Reasoning	Score
Conciseness	The API resource descriptions are verbose and repetitive, with phrases like 'For more information, see the guides for administrator and Google Drive activity reports. For more information about the activity report's parameters, see the activity parameters reference guides.' These could be significantly trimmed since Claude doesn't need the marketing-style descriptions.	2 / 3
Actionability	The skill provides the CLI syntax and the `gws schema` discovery pattern, but lacks concrete executable examples showing actual commands with real parameters (e.g., retrieving audit logs for a specific date range or application). The guidance is structural but not copy-paste ready for specific tasks.	2 / 3
Workflow Clarity	There's a basic two-step discovery workflow (browse help, then inspect schema), but no end-to-end workflow for common tasks like pulling audit logs or usage reports. No validation steps or error handling guidance is provided for operations like watch/stop channels.	2 / 3
Progressive Disclosure	The skill appropriately references the shared skill file (`../gws-shared/SKILL.md`) for auth and global flags, keeping this file focused on the admin-reports API. The structure is clean with clear sections and one-level-deep references.	3 / 3
	Total	9 / 12 Passed

Description

40%

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 clear domain niche (Google Workspace Admin SDK) which makes it distinctive, but it is too terse to be effective for skill selection. It lacks specific concrete actions, natural trigger term variations, and most critically, has no 'Use when...' clause to guide Claude on when to select this skill.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about Google Workspace admin tasks, audit logs, login activity, user usage reports, or G Suite administration.'

List specific concrete actions such as 'Query login events, retrieve email activity logs, generate user and device usage reports, monitor admin actions.'

Include common user-facing synonyms and variations like 'G Suite', 'Google admin', 'admin console', 'login activity', 'compliance logs'.

Dimension	Reasoning	Score
Specificity	Names the domain (Google Workspace Admin SDK) and mentions two capabilities (audit logs and usage reports), but doesn't list specific concrete actions like 'query login events', 'generate user activity reports', or 'export compliance data'.	2 / 3
Completeness	Describes what at a high level (audit logs and usage reports) but completely lacks a 'Use when...' clause or any explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also quite thin, warranting a 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Google Workspace', 'Admin SDK', 'audit logs', and 'usage reports', but misses common user variations like 'G Suite', 'admin console', 'login activity', 'user reports', or 'Google admin'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'Google Workspace Admin SDK' with 'audit logs and usage reports' is a clear, specific niche that is unlikely to conflict with other skills.	3 / 3
	Total	8 / 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: a3768d0

Reviewed: 3 months 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.