Set up a Google Sheets spreadsheet for tracking expenses with headers and initial entries.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill recipe-create-expense-tracker65
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
Full expense tracker setup workflow
Uses gws drive files create
0%
100%
Correct spreadsheet name
0%
100%
Correct mimeType
0%
100%
Uses gws sheets +append for headers
0%
100%
Correct header columns
0%
100%
Sheet1 range used
0%
100%
Sample entry added
50%
100%
Date format YYYY-MM-DD
100%
100%
Amount as decimal string
100%
100%
Uses gws drive permissions create
100%
100%
fileId in --params
0%
100%
Role is reader
100%
100%
Type is user
0%
100%
Without context: $0.5419 · 2m 16s · 33 turns · 66 in / 7,042 out tokens
With context: $0.4002 · 1m 21s · 26 turns · 326 in / 4,469 out tokens
Spreadsheet data append with correct format
Uses gws sheets +append
0%
100%
Specifies --spreadsheet-id
0%
100%
Range is Sheet1
60%
100%
Header columns Date Category Description Amount
0%
100%
Date format YYYY-MM-DD
100%
100%
Amount as decimal string
41%
41%
Each row appended separately
80%
100%
Uses --values flag
0%
100%
Values as JSON array
0%
100%
Without context: $0.5385 · 2m · 35 turns · 136 in / 6,425 out tokens
With context: $0.3876 · 1m 24s · 22 turns · 27 in / 4,794 out tokens
Spreadsheet creation and sharing permissions
Uses gws drive files create
0%
100%
Passes --json to files create
0%
100%
Correct mimeType
0%
100%
Spreadsheet named Expense Tracker 2025
0%
0%
Uses gws drive permissions create
100%
100%
fileId in --params not --json
100%
100%
Role is reader
100%
100%
Type is user
100%
100%
emailAddress included
100%
100%
Sheet ID reused
100%
100%
Without context: $0.4704 · 1m 55s · 32 turns · 32 in / 5,259 out tokens
With context: $0.1705 · 35s · 12 turns · 267 in / 1,901 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.