Google Slides: Read and write presentations.
58
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 — 56%
↑ 2.07xAgent success when using this skill
Validation for skill structure
Schema-driven API discovery workflow
Correct CLI invocation
33%
100%
Schema inspection present
0%
0%
Help discovery step
0%
0%
Flags from schema
0%
53%
Title-only creation
100%
100%
gws-shared prerequisite
23%
15%
generate-skills fallback
0%
0%
Without context: $0.3169 · 1m 22s · 22 turns · 26 in / 4,306 out tokens
With context: $0.4933 · 1m 21s · 27 turns · 72 in / 4,277 out tokens
Batch update atomicity and JSON flag construction
Correct CLI invocation
100%
100%
Schema inspection present
0%
0%
Help discovery step
0%
0%
--json flag used
0%
100%
All-or-nothing semantics
100%
100%
Presentation ID via params
0%
100%
Schema-derived payload
0%
0%
gws-shared prerequisite
0%
0%
generate-skills fallback
0%
0%
Without context: $1.0909 · 3m 53s · 35 turns · 33 in / 12,863 out tokens
With context: $0.6117 · 2m 42s · 31 turns · 87 in / 9,171 out tokens
Presentation and page retrieval commands
Get method invocation
100%
100%
Pages method invocation
100%
100%
Schema inspection for get
0%
100%
Schema inspection for pages
0%
100%
Help discovery step
100%
100%
--params flag usage
0%
100%
Discovery documented
0%
100%
gws-shared prerequisite
0%
0%
generate-skills fallback
0%
0%
Without context: $0.6577 · 2m 52s · 32 turns · 35 in / 9,787 out tokens
With context: $0.4253 · 1m 41s · 23 turns · 25 in / 6,084 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.