Google Workspace Events: Renew/reactivate Workspace Events subscriptions.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill gws-events-renew78
Quality
70%
Does it follow best practices?
Impact
100%
2.77xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/gws-events-renew/SKILL.mdDiscovery
40%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a clear, narrow capability (renewing Workspace Events subscriptions) which makes it distinctive, but it lacks explicit trigger guidance and could benefit from more natural user keywords. The missing 'Use when...' clause significantly limits Claude's ability to know when to select this skill.
Suggestions
Add a 'Use when...' clause with trigger scenarios like 'Use when the user needs to renew an expiring Google Workspace subscription, reactivate a stopped subscription, or mentions subscription lifecycle management.'
Include natural user phrases like 'subscription expired', 'subscription expiring soon', 'reactivate events', or 'Google Workspace API subscription' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Workspace Events) and specific actions (renew/reactivate subscriptions), but only lists two related actions rather than a comprehensive set of capabilities. | 2 / 3 |
Completeness | Describes what it does (renew/reactivate subscriptions) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'Workspace Events', 'subscriptions', 'renew', 'reactivate', but missing common variations users might say like 'expired subscription', 'subscription expiring', or 'Google events API'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche focusing on Google Workspace Events subscriptions renewal - unlikely to conflict with other skills due to the narrow, well-defined scope. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, focused skill that efficiently documents a single CLI command. It provides all necessary information (flags, examples, tips) without verbosity, and properly references related documentation for context that doesn't need to be repeated.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, with no unnecessary explanations. Every section serves a purpose - usage, flags, examples, and tips are all concise and assume Claude's competence. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready commands with clear flag documentation. The examples show exact usage patterns for both single subscription and batch renewal scenarios. | 3 / 3 |
Workflow Clarity | This is a simple, single-purpose skill (renew subscriptions). The single action is unambiguous with clear flag options. The tip about cron jobs provides practical workflow guidance without overcomplicating. | 3 / 3 |
Progressive Disclosure | Appropriately structured with clear one-level-deep references to shared auth documentation and related events commands. The prerequisite callout and See Also section provide good navigation without nesting. | 3 / 3 |
Total | 12 / 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 | |
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.