Google Workspace Enterprise License Manager: Manage product licenses.
58
47%
Does it follow best practices?
Impact
72%
2.88xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/gws-licensing/SKILL.mdQuality
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 use, 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 natural variations users might say such as 'add user to Google Workspace', 'check license usage', 'manage Google seats'
| 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 concise, appropriately delegating shared concerns to a parent skill file. However, it lacks concrete executable examples showing actual license operations with real parameters, and missing validation steps for what could be impactful license changes (revoking access).
Suggestions
Add at least one complete executable example showing a license assignment or revocation with actual --params and --json flags
Include a verification step showing how to confirm a license change was applied successfully (e.g., using the 'get' method after insert/delete)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean content that assumes Claude's competence. No unnecessary explanations of what licensing is or how APIs work. Every line serves a purpose. | 3 / 3 |
Actionability | Provides command structure and method discovery patterns, but lacks concrete executable examples showing actual license assignment/revocation with real parameters and JSON payloads. | 2 / 3 |
Workflow Clarity | Shows discovery workflow (help -> schema -> build command) but lacks validation steps for license operations. No guidance on verifying license changes succeeded or handling errors. | 2 / 3 |
Progressive Disclosure | Appropriately references shared skill file for common patterns, keeps this file focused on licensing-specific resources and methods. Clear one-level-deep reference structure. | 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 | |
6ed836c
Table of Contents
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.