gws-groupssettings
Manage Google Groups settings.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill gws-groupssettings64
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/skillEvaluation — 100%
↑ 4.54xAgent success when using this skill
Validation 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 effectively guide skill selection. It lacks specific actions, explicit trigger conditions, and natural keyword variations. The only strength is mentioning 'Google Groups' which provides some domain specificity.
Suggestions
Add specific concrete actions like 'Add/remove members, configure group permissions, manage email delivery settings, update group metadata'
Include a 'Use when...' clause with trigger terms like 'Google Groups', 'group membership', 'mailing list settings', 'group permissions', 'group administration'
Add common variations users might say: 'Google group', 'mailing list', 'distribution list', 'group members'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('Manage...settings') without listing any concrete actions. It doesn't specify what settings can be managed (e.g., add members, change permissions, configure email delivery). | 1 / 3 |
Completeness | The description only vaguely addresses 'what' (manage settings) and completely lacks any 'when' clause or explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | 'Google Groups' is a relevant keyword users might say, but the description lacks variations or related terms like 'group membership', 'mailing list', 'group permissions', or 'group administration'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Google Groups' provides some specificity that distinguishes it from generic document or code skills, but 'settings' is vague enough that it could overlap with other Google Workspace administration 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 is a concise, well-structured skill that effectively leverages a shared skill file for common patterns. However, it lacks concrete examples showing actual API calls with parameters, and the workflow for modifying group settings (patch/update) would benefit from validation checkpoints to verify changes were applied correctly.
Suggestions
Add at least one complete executable example showing a real API call, e.g., `gws groupssettings groups get --params groupUniqueId=mygroup@domain.com`
Include a brief validation step for update/patch operations, such as calling 'get' after modification to confirm changes
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean content that assumes Claude's competence. No unnecessary explanations of what Google Groups is or how APIs work. Every line serves a purpose. | 3 / 3 |
Actionability | Provides concrete CLI commands and method names, but lacks executable examples showing actual usage with parameters. The 'get', 'patch', 'update' methods are listed without showing how to actually call them with real data. | 2 / 3 |
Workflow Clarity | Shows a discovery workflow (help -> schema -> build command) but lacks validation steps for operations. For 'patch' and 'update' which modify group settings, there's no guidance on verifying changes or handling errors. | 2 / 3 |
Progressive Disclosure | Appropriately structured with clear reference to shared skill file for common concerns. Single-level reference to '../gws-shared/SKILL.md' is well-signaled. Content is appropriately scoped for this simple API wrapper. | 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.