recipe-generate-report-from-sheet
Read data from a Google Sheet and create a formatted Google Docs report.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill recipe-generate-report-from-sheet65
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 identifies a specific workflow between two Google products but lacks the explicit trigger guidance required for Claude to reliably select it. It needs a 'Use when...' clause and more specific details about the types of reports or formatting capabilities supported.
Suggestions
Add a 'Use when...' clause with trigger terms like 'spreadsheet to report', 'Google Sheets report', 'convert sheet to document', 'generate report from data'
Specify what 'formatted report' means - e.g., 'tables, charts, summaries, or templated documents'
Include common term variations: 'Sheets', 'spreadsheet', 'Docs', '.gsheet', 'report generation'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Sheets, Google Docs) and describes two actions (read data, create report), but lacks comprehensive detail about what 'formatted report' means or what specific operations are supported. | 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. | 1 / 3 |
Trigger Term Quality | Includes 'Google Sheet' and 'Google Docs' which are natural terms, but misses common variations like 'spreadsheet', 'Sheets', 'Docs', 'report generation', or file extensions. | 2 / 3 |
Distinctiveness Conflict Risk | The Google Sheets to Google Docs pipeline is somewhat specific, but 'formatted report' is vague and could overlap with other reporting or document generation 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 well-crafted recipe skill that efficiently demonstrates a multi-service workflow with concrete, executable commands. The main weakness is the lack of validation steps between operations—there's no verification that each step succeeded before proceeding to the next, which is important for a multi-step workflow involving external services.
Suggestions
Add validation checkpoints between steps, e.g., 'Verify the read returned data before proceeding' or capture and check the document ID from the create response before writing
Consider adding a brief error handling note for common failures (e.g., permission denied on sheet read, invalid document ID)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only the essential commands without explaining what Google Sheets or Docs are. Every line serves a purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable CLI commands with concrete examples including actual JSON payloads, placeholder IDs, and realistic sample data. Commands are copy-paste ready with minimal modification needed. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced logically (read → create → write → share), but lacks validation checkpoints. No verification that the sheet read succeeded before creating the doc, or that the doc was created successfully before writing. | 2 / 3 |
Progressive Disclosure | For a simple recipe skill under 50 lines, the structure is appropriate. The prerequisite clearly signals dependencies on other skills, and the content is well-organized without needing 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.