recipe-create-presentation
Create a new Google Slides presentation and add initial slides.
61
52%
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-presentation/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 brief and identifies the core domain (Google Slides) and primary action (creating presentations), but it lacks a 'Use when...' clause, misses common trigger term variations, and provides limited detail on specific capabilities. It would benefit significantly from explicit trigger guidance and more concrete action descriptions.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to create a new Google Slides presentation, slide deck, or slideshow from scratch.'
Include additional natural trigger terms such as 'slide deck', 'slideshow', 'Google presentation', and 'new slides'.
Expand the capability description with more specific actions, e.g., 'Create a new Google Slides presentation with title slides, content slides, and custom layouts.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Slides) and two actions (create presentation, add initial slides), but lacks detail on what kinds of slides, layouts, or content can be added. | 2 / 3 |
Completeness | Describes what the skill does but has no explicit 'Use when...' clause or trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also fairly thin, bringing this closer to a 1. | 1 / 3 |
Trigger Term Quality | Includes 'Google Slides' and 'presentation' which are natural terms, but misses common variations like 'slide deck', 'slideshow', '.gslides', or 'Google presentation'. | 2 / 3 |
Distinctiveness Conflict Risk | Specifying 'Google Slides' helps distinguish it from generic presentation skills, but it could still overlap with broader presentation creation or editing skills since it doesn't clearly delineate its scope (e.g., only creation, not editing existing ones). | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is concise and well-structured but falls short on its stated purpose—it claims to 'add initial slides' but only covers creation and sharing. The workflow lacks validation checkpoints and the ID extraction step is vague rather than concrete.
Suggestions
Add a step showing how to add initial slides using a concrete command (e.g., batchUpdate with slide creation requests), since this is part of the stated purpose.
Make step 2 actionable by showing how to extract the presentation ID from the JSON response (e.g., using jq or referencing the specific field).
Add a validation step after creation, such as verifying the presentation exists with a get command before sharing.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. No unnecessary explanations of what Google Slides is or how APIs work. Every line serves a purpose. | 3 / 3 |
Actionability | Provides concrete CLI commands which is good, but the description says 'add initial slides' yet no step shows how to actually add slides to the presentation. The workflow only creates and shares. Missing key details for the stated purpose. | 2 / 3 |
Workflow Clarity | Steps are listed in sequence but there's no validation (e.g., confirming the presentation was created successfully before sharing). Step 2 is vague ('Get the presentation ID from the response') without showing how to extract it. No error handling or verification. | 2 / 3 |
Progressive Disclosure | For a simple skill under 50 lines, the structure is appropriate. It has a clear prerequisite callout and a concise steps section. No need for external references given the scope. | 3 / 3 |
Total | 10 / 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.