Read and write Google Forms.
59
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
Two-step form creation workflow
Separate create call
66%
100%
Create uses only title fields
80%
100%
Separate batchUpdate call
0%
100%
Items added after creation
80%
100%
Schema inspection present
0%
0%
Correct CLI syntax
20%
100%
README explains two-step order
40%
100%
Form ID captured and reused
100%
100%
document_title included
100%
100%
Without context: $1.2652 · 3m 56s · 53 turns · 50 in / 11,251 out tokens
With context: $0.4955 · 1m 53s · 29 turns · 279 in / 6,437 out tokens
Schema-driven API discovery and flag construction
Schema command in script
100%
100%
Schema precedes API call
100%
100%
DISCOVERY_LOG documents schema commands
100%
100%
DISCOVERY_LOG records key parameters
100%
100%
Correct responses method syntax
100%
100%
--params flag usage
0%
100%
Form ID as argument
100%
100%
Output saved to file
100%
100%
Correct CLI syntax overall
100%
100%
Without context: $1.0028 · 3m 32s · 56 turns · 63 in / 10,284 out tokens
With context: $0.5422 · 2m 15s · 32 turns · 191 in / 7,375 out tokens
Help discovery and publish settings automation
Help command used
100%
100%
Schema inspection for setPublishSettings
26%
100%
Schema before API call
70%
100%
Correct setPublishSettings syntax
0%
100%
WORKFLOW.md documents discovery
100%
100%
Schema-derived flags
0%
100%
Form ID as argument
100%
100%
Output saved
100%
100%
Correct CLI syntax overall
60%
100%
Without context: $0.3371 · 1m 29s · 22 turns · 820 in / 4,571 out tokens
With context: $0.3023 · 1m 18s · 19 turns · 21 in / 4,301 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.