recipe-log-deal-update
Append a deal status update to a Google Sheets sales tracking spreadsheet.
74
68%
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-log-deal-update/SKILL.mdQuality
Discovery
50%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 highly specific about what it does and occupies a clear niche, making it distinctive. However, it completely lacks a 'Use when...' clause, which is critical for Claude to know when to select this skill from a large pool. Adding explicit trigger guidance and a few more natural keyword variations would significantly improve it.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user wants to log a deal update, record a sales status change, or append to a sales tracking sheet in Google Sheets.'
Include additional natural trigger terms users might say, such as 'pipeline update', 'deal log', 'CRM entry', 'sales progress', or 'deal tracker'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a concrete action ('Append a deal status update'), a specific tool ('Google Sheets'), and a specific domain artifact ('sales tracking spreadsheet'). This is a well-defined, specific capability. | 3 / 3 |
Completeness | The description answers 'what does this do' clearly but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'when' is entirely absent, this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes good natural terms like 'deal status update', 'Google Sheets', 'sales tracking', and 'spreadsheet', but misses common variations users might say such as 'CRM update', 'pipeline', 'deal log', 'sales update', or 'deal tracker'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Google Sheets', 'deal status update', and 'sales tracking spreadsheet' creates a very specific niche that is unlikely to conflict with other skills. It is clearly distinguishable from general spreadsheet or document skills. | 3 / 3 |
Total | 9 / 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 skill that provides clear CLI commands for a straightforward 3-step workflow. Its main weakness is the lack of validation checkpoints—there's no verification that the sheet was found in step 1 or that the append succeeded in step 3, which is a gap for a data-writing operation.
Suggestions
Add a validation step after the append (e.g., re-read the last row to confirm it was written correctly)
Add error handling guidance for when the 'Sales Pipeline' sheet is not found in step 1 (e.g., 'If no results, check the sheet name or create one')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. No unnecessary explanations of what Google Sheets is or how APIs work. Every line serves a purpose, and the prerequisite is stated concisely. | 3 / 3 |
Actionability | Provides fully concrete, copy-paste ready CLI commands with specific flags, parameters, and example values. The example row data with realistic field values makes it immediately executable. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (find → read → append), but there's no validation step to confirm the append succeeded (e.g., re-reading the sheet to verify the row was added) or error handling if the sheet isn't found in step 1. | 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.