gws-reseller
Google Workspace Reseller: Manage Workspace subscriptions.
49
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 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 'Google Workspace Reseller' prefix provides minimal distinctiveness but the rest is insufficient.
Suggestions
Add a 'Use when...' clause with trigger terms like 'reseller', 'customer subscriptions', 'license management', 'seat allocation', 'Workspace billing'
List specific concrete actions such as 'create customer accounts, provision licenses, transfer subscriptions, modify seat counts, manage billing'
Include common term variations users might say: 'GSuite reseller', 'Workspace partner', 'customer licenses', 'subscription management'
| 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's 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', 'licenses', 'seats', 'billing', 'customer accounts', or 'partner'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'Google Workspace Reseller' prefix provides some distinctiveness from general Workspace skills, but 'manage subscriptions' is generic enough to potentially conflict with billing or admin 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 progressive disclosure through the shared skill reference and discovery commands. However, it lacks concrete executable examples and workflow guidance for common reseller operations, making it more of a documentation index than actionable guidance.
Suggestions
Add 2-3 concrete executable examples showing common operations like getting a customer, listing subscriptions, or creating a new customer with actual --params usage
Include a workflow example for a multi-step operation (e.g., create customer → add subscription) with validation checkpoints
Trim the verbose method descriptions to brief summaries since users can get full details via gws schema commands
| 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 | Appropriately structured with a clear prerequisite reference to shared skills, organized by API resources, and uses the discovery commands to defer detailed schema information. The single-level reference to the shared skill file is well-signaled. | 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 | |
- 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.