Subscribe to Google Workspace events.
55
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
Schema discovery before API calls
Help discovery step
40%
100%
Schema inspection — create
33%
100%
Schema inspection — get
0%
100%
Correct create syntax
41%
100%
Correct get syntax
40%
100%
Flags from schema
0%
100%
Correct resource format
50%
100%
Target space referenced
100%
100%
Discovery notes
90%
100%
No raw HTTP calls
100%
100%
Without context: $0.4919 · 2m 35s · 27 turns · 83 in / 8,117 out tokens
With context: $0.2793 · 1m 13s · 17 turns · 267 in / 3,777 out tokens
Subscribe helper for event streaming
Uses +subscribe helper
100%
100%
NDJSON output format
100%
100%
Stream to file
50%
60%
Correct command syntax
100%
87%
Schema inspection used
0%
0%
Target space referenced
100%
100%
Streaming design explained
100%
100%
Subscribe vs subscriptions distinction
100%
66%
No raw polling loop
100%
100%
Without context: $0.5622 · 2m 23s · 28 turns · 31 in / 6,732 out tokens
With context: $0.3207 · 1m 32s · 18 turns · 179 in / 4,775 out tokens
Renew and reactivate subscription lifecycle
Uses +renew helper
0%
0%
Uses subscriptions reactivate
33%
100%
Uses subscriptions list
40%
100%
Schema inspection
0%
0%
Help discovery
0%
0%
Correct command syntax
0%
100%
Renew vs reactivate distinction
100%
100%
Report output
100%
100%
Health verification
75%
100%
Flags from schema
40%
100%
Without context: $0.4888 · 2m 19s · 26 turns · 29 in / 7,532 out tokens
With context: $0.5488 · 2m 18s · 26 turns · 28 in / 8,852 out tokens
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.