Manage Google Keep notes.
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-first note operations workflow
Correct CLI syntax
100%
100%
Help inspection step
0%
0%
Schema inspection for create
0%
0%
Schema inspection for get
0%
0%
Schema inspection for delete
0%
0%
Schema drives params/json flags
20%
100%
OWNER role requirement noted
12%
100%
Delete irreversibility noted
100%
100%
Collaborator access note
0%
100%
Auth prerequisite acknowledged
75%
100%
Without context: $0.2689 · 1m 18s · 22 turns · 134 in / 3,886 out tokens
With context: $0.3509 · 1m 18s · 22 turns · 271 in / 4,269 out tokens
Paginated note listing
Correct CLI syntax
100%
100%
Schema inspection for list
0%
0%
Schema drives flags
0%
50%
page_size parameter used
0%
0%
next_page_token extraction
57%
100%
page_token passed to subsequent calls
66%
100%
Loop terminates correctly
100%
100%
Help or schema inspection before list
0%
0%
Auth prerequisite acknowledged
0%
0%
Without context: $0.4991 · 1m 50s · 33 turns · 1,221 in / 5,405 out tokens
With context: $0.3065 · 1m 12s · 19 turns · 305 in / 3,418 out tokens
Media attachment download with MIME type handling
Correct CLI syntax
0%
100%
Schema inspection for download
0%
0%
alt=media parameter
0%
100%
Schema drives flags
0%
100%
400 error handling
31%
50%
MIME type unavailability documented
100%
100%
Help inspection step
0%
0%
Continues on failure
100%
77%
Auth prerequisite acknowledged
100%
0%
Without context: $0.3086 · 1m 33s · 17 turns · 23 in / 4,875 out tokens
With context: $0.3991 · 1m 26s · 24 turns · 28 in / 4,947 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.