recipe-create-expense-tracker
Set up a Google Sheets spreadsheet for tracking expenses with headers and initial entries.
67
60%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/recipe-create-expense-tracker/SKILL.mdQuality
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 communicates a narrow, specific task (setting up an expense tracking spreadsheet in Google Sheets) but lacks a 'Use when...' clause, which significantly hurts completeness. It has decent but incomplete trigger terms and could be more distinctive by clarifying its niche relative to other spreadsheet or financial skills.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to create an expense tracker, budget spreadsheet, or set up a Google Sheets template for tracking spending.'
Include additional natural trigger terms users might say, such as 'budget', 'expense tracker', 'financial tracking', 'spending log', or 'Google Sheets template'.
Broaden or clarify the scope of capabilities — does it only set up the sheet, or can it also format, add formulas, or categorize expenses? Listing these would improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Google Sheets) and describes some actions (set up spreadsheet, tracking expenses, headers, initial entries), but the actions are narrow and not comprehensive — it only covers setup, not ongoing manipulation or analysis. | 2 / 3 |
Completeness | It describes what the skill does but has no explicit 'Use when...' clause or equivalent trigger guidance, and per the rubric a missing 'Use when' clause caps completeness at 2 — but here the 'when' is entirely absent, not just implied, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Google Sheets', 'spreadsheet', 'tracking expenses', and 'headers', but misses common variations users might say such as 'budget', 'expense tracker', 'financial tracking', or 'Google Sheets template'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Google Sheets' and 'expense tracking' provides some specificity, but it could overlap with general spreadsheet skills or broader financial/budgeting skills. | 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 concise, actionable recipe-style skill that provides executable commands for each step. Its main weakness is the lack of a validation step or guidance on capturing the SHEET_ID from the creation response, which could cause confusion in practice. Otherwise, it's well-structured and efficient.
Suggestions
Add a note after step 1 explaining how to capture the SHEET_ID from the creation response (e.g., 'Save the `id` field from the response as SHEET_ID for subsequent steps').
Add a verification step such as reading back the sheet contents after appending to confirm the data was written correctly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. No unnecessary explanations of what Google Sheets is or how spreadsheets work. Every line serves a purpose with concrete commands. | 3 / 3 |
Actionability | Each step provides a specific, copy-paste ready command with exact flags, JSON payloads, and parameters. The commands are fully executable given the prerequisite tools. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and logical, but there's no validation checkpoint—e.g., verifying the spreadsheet was created successfully before appending data, or confirming the SHEET_ID is captured from step 1's output. The SHEET_ID placeholder is used without explaining how to obtain it from the creation response. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized with a clear prerequisite callout and numbered steps. No need for external references given the scope. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
- Repository
- googleworkspace/cli
- Commit
c7c6646
- 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.