recipe-create-presentation
Create a new Google Slides presentation and add initial slides.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill recipe-create-presentation59
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 clear domain (Google Slides) and basic actions but is incomplete. It lacks explicit trigger guidance ('Use when...'), misses common user terminology variations, and doesn't fully differentiate itself from other presentation-related skills.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks to create Google Slides, make a slideshow, or build a presentation deck'
Include more natural trigger terms users might say: 'slides', 'deck', 'slideshow', 'Google presentation'
Expand the capability list to be more specific: what types of slides, layouts, or content can be added
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Slides) and two actions (create presentation, add slides), but lacks comprehensive detail about what kinds of slides, formatting options, or other capabilities. | 2 / 3 |
Completeness | Describes what it 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 Slides' and 'presentation' which are natural terms, but misses common variations like 'slides', 'slideshow', 'deck', '.pptx', or 'PowerPoint' that users might say. | 2 / 3 |
Distinctiveness Conflict Risk | Google Slides is fairly specific, but 'presentation' could overlap with other presentation tools (PowerPoint, Keynote). The lack of explicit triggers increases conflict risk with similar skills. | 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 fails to deliver on its stated purpose of adding initial slides - it only covers creation and sharing. The workflow is incomplete and lacks the core functionality promised in both the title and description.
Suggestions
Add concrete commands for creating initial slides (e.g., batchUpdate with createSlide requests) to fulfill the skill's stated purpose
Show how to extract the presentation ID from the JSON response (e.g., using jq or noting the field path)
Add a validation step to confirm presentation creation succeeded before proceeding to share
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean content with no unnecessary explanations. Every line serves a purpose - prerequisite, description, and concrete steps only. | 3 / 3 |
Actionability | Provides concrete CLI commands which is good, but the title promises 'add initial slides' which is not demonstrated. Step 2 is vague ('Get the presentation ID') without showing how to extract it from JSON response. | 2 / 3 |
Workflow Clarity | Steps are sequenced but incomplete - missing the actual slide creation steps promised in the description. No validation checkpoint to confirm presentation was created successfully before sharing. | 2 / 3 |
Progressive Disclosure | For this simple skill, the structure is appropriate - clear prerequisite callout, brief description, and numbered steps. No need for external references given the scope. | 3 / 3 |
Total | 10 / 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.