gws-licensing
Google Workspace Enterprise License Manager: Manage product licenses.
55
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is too minimal to be effective for skill selection. While it identifies the specific Google product, it fails to describe concrete actions, lacks trigger terms users would naturally say, and provides no guidance on when Claude should select this skill over others.
Suggestions
Add specific actions like 'Assign, revoke, list, and audit Google Workspace licenses for users and organizational units'
Add a 'Use when...' clause with trigger terms like 'assign license', 'remove license', 'user seats', 'Google Workspace subscription', 'licensing audit'
Include common user scenarios such as 'onboarding new employees', 'offboarding', or 'license compliance reporting'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'Manage product licenses' which is extremely vague. It doesn't specify what actions can be performed (assign, revoke, list, audit, etc.) - just uses the generic verb 'manage'. | 1 / 3 |
Completeness | Only partially addresses 'what' (manage licenses) with no specificity, and completely lacks any 'when' guidance or 'Use when...' clause to help Claude know when to select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'Google Workspace', 'Enterprise License Manager', and 'licenses' which are relevant domain terms, but misses natural user phrases like 'assign license', 'user licensing', 'seat management', or 'subscription'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Google Workspace Enterprise License Manager' is a specific product name which helps distinguish it, but 'manage product licenses' is generic enough to potentially conflict with other licensing-related skills. | 2 / 3 |
Total | 6 / 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 skill is well-structured and token-efficient, properly leveraging the shared GWS skill for common concerns. However, it lacks concrete executable examples showing actual license operations with parameters, and missing validation/verification steps for what could be impactful operations (revoking licenses). The discovery workflow is helpful but incomplete without showing the full path to execution.
Suggestions
Add at least one complete executable example showing a license assignment or listing with actual --params values (e.g., `gws licensing licenseAssignments insert --params productId=... userId=...`)
Include a verification step after license operations (e.g., 'After assigning, verify with `gws licensing licenseAssignments get`')
Add brief error handling guidance for common failure cases like 'user already has license' or 'invalid SKU'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what licensing is or how APIs work. Every line serves a purpose - prerequisite reference, command syntax, resource listing, and discovery commands. | 3 / 3 |
Actionability | Provides concrete CLI commands for discovery and lists available methods, but lacks executable examples showing actual license assignment/revocation with real parameters. Users must figure out the --params syntax themselves. | 2 / 3 |
Workflow Clarity | Shows a discovery workflow (help -> schema -> build command) but lacks validation steps for license operations. No guidance on verifying license assignment succeeded or handling errors when revoking licenses. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear prerequisite reference to shared skill, concise overview, and well-organized sections. Appropriately delegates auth/security to the shared skill file rather than duplicating content. | 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 | |
- 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.