recipe-create-presentation
Create a new Google Slides presentation and add initial slides.
56
46%
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 a 'Use when...' clause with trigger terms like 'create a slide deck', 'new Google Slides presentation', 'make slides', 'slideshow'.
Expand the capability list with more specific actions, e.g., 'Create a new Google Slides presentation with title slides, content slides, and custom layouts'.
Include common keyword variations such as 'slide deck', 'slideshow', 'Google presentation' to improve trigger term coverage.
| 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 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also fairly thin, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes 'Google Slides' and 'presentation' which are natural terms, but misses common variations like 'slide deck', '.gslides', 'slideshow', or 'Google presentation'. | 2 / 3 |
Distinctiveness Conflict Risk | Specifying 'Google Slides' helps distinguish it from generic presentation skills (e.g., PowerPoint/.pptx), but could still overlap with other Google Slides editing or analysis skills since it doesn't clearly scope to only creation of new presentations. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
60%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 fails to deliver on its stated purpose of adding initial slides—it only creates a presentation and shares it. The workflow has gaps: step 2 is vague, there's no validation, and the core promised functionality (adding slides) is entirely missing.
Suggestions
Add concrete commands for adding initial slides to the presentation, as promised in the skill description (e.g., batchUpdate with createSlide requests).
Replace the vague 'Get the presentation ID from the response' with a concrete extraction method (e.g., jq command or specific JSON path).
Add a validation step to verify the presentation was created and slides were added successfully (e.g., `gws slides presentations get --params '{"presentationId": "PRESENTATION_ID"}'`).
| 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 sharing step is tangential to the stated goal. Missing the core task of adding slides. | 2 / 3 |
Workflow Clarity | Steps are incomplete relative to the stated goal of adding initial slides. Step 2 ('Get the presentation ID from the response') is vague with no concrete guidance on how to extract it. No validation or verification that the presentation was created successfully or that slides were added. | 1 / 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 | 9 / 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.