gws-admin
Google Workspace Admin SDK: Manage users, groups, and devices.
66
52%
Does it follow best practices?
Impact
94%
1.59xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/gws-admin/SKILL.mdQuality
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 provides a basic understanding of the skill's domain and high-level capabilities but lacks the depth needed for effective skill selection. The absence of explicit trigger guidance ('Use when...') is a significant weakness, and the action verbs are too generic to distinguish this from other administrative tools.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when managing Google Workspace accounts, provisioning users, handling G Suite administration, or working with organizational units'
Expand specific actions beyond 'manage' to include concrete operations like 'create/delete users, assign licenses, configure groups, manage mobile devices, set organizational policies'
Include common user terminology variations such as 'G Suite', 'Google admin console', 'user provisioning', 'directory management'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Workspace Admin SDK) and lists some actions (manage users, groups, devices), but lacks comprehensive detail about specific operations like creating users, assigning roles, or configuring policies. | 2 / 3 |
Completeness | Describes what it does (manage users, groups, devices) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Google Workspace', 'Admin', 'users', 'groups', 'devices', but misses common variations users might say like 'G Suite', 'Google admin', 'directory', 'organization units', or 'user provisioning'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'Google Workspace Admin SDK' prefix provides some distinctiveness, but 'manage users, groups, and devices' is generic enough to potentially overlap with other identity management or admin skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-organized API reference skill that efficiently catalogs the Admin SDK resources and methods. Its main weakness is the lack of concrete usage examples showing actual commands with parameters, and missing validation guidance for destructive operations like user deletion or device deprovisioning.
Suggestions
Add 2-3 concrete executable examples showing common operations (e.g., creating a user, listing group members) with actual --params usage
Include validation/confirmation guidance for destructive operations like `users delete`, `mobiledevices action` (wipe), and `chromeosdevices action` (deprovision)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient - it's essentially a reference card listing available API resources and methods without explaining what an API is or how admin SDKs work. Every section serves a clear purpose. | 3 / 3 |
Actionability | Provides the command structure and lists all available methods, but lacks concrete executable examples showing actual usage with parameters. The 'Discovering Commands' section shows how to explore but not how to execute real operations. | 2 / 3 |
Workflow Clarity | The discovery workflow (help -> schema -> build command) is present but implicit. For destructive operations like device deprovisioning or user deletion, there are no validation checkpoints or confirmation steps mentioned. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear prerequisite reference to shared skill, organized resource sections, and appropriate use of the schema command for deeper exploration. One-level-deep reference to the shared skill file. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- Repository
- googleworkspace/cli
- Commit
6ed836c
- Reviewed
Table of Contents
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.