recipe-create-expense-tracker
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
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description provides a basic understanding of the skill's purpose but lacks the explicit trigger guidance essential for Claude to select it appropriately from a large skill library. It names the domain and core action but misses comprehensive capability details and natural keyword variations that users might employ.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks to create an expense tracker, budget spreadsheet, or wants to log spending in Google Sheets'
Expand trigger terms to include natural variations: 'budget', 'spending log', 'financial tracking', 'expense report', 'money tracker'
Add more specific capabilities: mention formula setup, category columns, date formatting, or summary calculations to distinguish from generic spreadsheet skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Sheets, expense tracking) and some actions (set up, headers, initial entries), but lacks comprehensive detail about specific capabilities like formulas, categories, or formatting options. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no 'when' component at all. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Google Sheets', 'spreadsheet', 'expenses', and 'tracking', but misses common variations users might say like 'budget', 'spending', 'expense tracker', or 'financial tracking'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to expense tracking in Google Sheets, but could overlap with general spreadsheet skills, budgeting tools, or other financial tracking skills without clearer boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, concise skill that provides actionable, executable commands for creating an expense tracker. The main weakness is the lack of validation steps between operations - there's no verification that the spreadsheet creation succeeded before attempting to append data, which could lead to silent failures.
Suggestions
Add a validation step after spreadsheet creation to capture and verify the returned SHEET_ID before proceeding with append operations
Consider adding a verification step after sharing to confirm the permission was applied correctly
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean and efficient with no unnecessary explanation. Every line serves a purpose - prerequisite note, brief description, and concrete commands. No padding or concepts Claude already knows. | 3 / 3 |
Actionability | Provides fully executable CLI commands with specific JSON payloads. Each step is copy-paste ready with clear placeholders (SHEET_ID) that are self-explanatory. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and logical, but lacks validation checkpoints. No verification that the spreadsheet was created successfully before appending, or confirmation that sharing succeeded. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the structure is appropriate. Clear prerequisite callout, brief description, and well-organized numbered steps. No need for external references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- Reviewed
Table of Contents
Is this your skill?
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.