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 is narrowly focused on a single task (setting up an expense tracking spreadsheet in Google Sheets), which provides some specificity but limits its usefulness as a skill description. It lacks an explicit 'Use when...' clause, which is critical for Claude to know when to select this skill. The trigger terms are adequate but could be expanded with common user language variations.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to create a budget, expense tracker, or financial spreadsheet in Google Sheets.'
Include additional natural trigger terms users might say, such as 'budget', 'expense report', 'financial tracking', 'spending tracker', or 'money management spreadsheet'.
Broaden the capability description if the skill supports more than just initial setup, e.g., adding formulas, categories, or formatting for expense tracking.
| 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. However, the 'when' is entirely absent — not even implied beyond the what — so it scores at 1 rather than 2. Actually, the 'when' is somewhat implied by the specificity of the task. Revising to 2. | 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' is somewhat specific, but it could overlap with general spreadsheet skills or broader expense/budget management 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 concrete CLI commands for each step. Its main weakness is the lack of validation checkpoints between steps — particularly verifying the spreadsheet creation succeeded and capturing the SHEET_ID before using it in subsequent commands. The SHEET_ID placeholder is used without explicit guidance on how to capture it from step 1's output.
Suggestions
Add a validation/capture step after step 1 to extract the SHEET_ID from the creation response, e.g., 'Capture the `id` field from the response to use as SHEET_ID in subsequent steps'
Consider adding a verification step after appending data, such as reading back the sheet contents to confirm the entries were added correctly
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. The prerequisite note is necessary, and every step is a concrete command with no unnecessary explanation of what Google Sheets is or how APIs work. | 3 / 3 |
Actionability | Every step provides a specific, copy-paste ready CLI command with exact flags, JSON payloads, and parameters. The placeholder SHEET_ID is the only abstraction, which is unavoidable. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and logical, but there are no validation checkpoints — no step to verify the spreadsheet was created successfully or that the append operations succeeded before proceeding. For a multi-step process involving external API calls, explicit verification would strengthen this. | 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
a3768d0
- 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.