Google Workspace Reseller: Manage Workspace subscriptions.
56
40%
Does it follow best practices?
Impact
85%
2.12xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/gws-reseller/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 brief and vague to effectively guide skill selection. It lacks specific actions, natural trigger terms users would say, and completely omits guidance on when Claude should select this skill. The description would benefit significantly from listing concrete reseller operations and adding explicit trigger conditions.
Suggestions
Add specific concrete actions like 'create customer accounts, provision licenses, transfer subscriptions, modify seat counts, manage billing'
Add a 'Use when...' clause with trigger terms like 'reseller', 'customer subscription', 'provision Workspace', 'license management', 'GSuite reseller'
Include common user terminology variations such as 'GSuite', 'Google apps licenses', 'Workspace seats', 'reseller console'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only mentions 'Manage Workspace subscriptions' which is vague and abstract. It doesn't list concrete actions like 'create subscriptions', 'transfer licenses', 'modify seat counts', or other specific operations. | 1 / 3 |
Completeness | The description only weakly addresses 'what' (manage subscriptions) and completely lacks any 'when' guidance. There is no 'Use when...' clause or explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('Google Workspace', 'Reseller', 'subscriptions') but misses common variations users might say like 'GSuite', 'Google apps', 'licenses', 'seats', 'billing', or 'customer accounts'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'Google Workspace Reseller' prefix provides some distinctiveness, but 'manage subscriptions' is generic enough to potentially conflict with other subscription management or Google-related skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
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 Reseller API with good organization and appropriate cross-referencing to shared documentation. However, it lacks concrete executable examples and relies heavily on API documentation descriptions rather than actionable guidance. The skill would benefit from practical examples showing common workflows.
Suggestions
Add 2-3 concrete executable examples showing common operations (e.g., getting a customer, listing subscriptions) with actual --params usage
Include a workflow example for a multi-step operation like 'create customer then add subscription' with validation steps
Trim the verbose method descriptions to essential information - the gws schema command already provides detailed parameter info
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes lengthy method descriptions that could be trimmed. The API documentation excerpts add bulk without providing actionable guidance beyond what the help commands would show. | 2 / 3 |
Actionability | Provides the basic command structure and discovery commands, but lacks concrete executable examples showing actual usage with parameters. No copy-paste ready examples for common operations like creating a customer or managing subscriptions. | 2 / 3 |
Workflow Clarity | The 'Discovering Commands' section provides a basic two-step workflow for exploration, but there's no guidance on multi-step operations like creating a customer then adding a subscription, and no validation checkpoints for potentially destructive operations like delete or suspend. | 2 / 3 |
Progressive Disclosure | Good structure with clear prerequisite reference to shared skill, organized API resources section, and appropriate use of the discovery commands section. The content is well-organized and references are one level deep. | 3 / 3 |
Total | 9 / 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.