gws-slides
Google Slides: Read and write presentations.
55
45%
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/gws-slides/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 too terse, providing only a minimal indication of domain (Google Slides) and two very broad verbs (read, write). It lacks a 'Use when...' clause, specific concrete actions, and sufficient trigger terms to reliably distinguish it from other presentation-related skills.
Suggestions
Add a 'Use when...' clause with explicit trigger terms, e.g., 'Use when the user asks about Google Slides, slide decks, or presentation creation/editing.'
List specific concrete actions such as 'create slides, edit text and layouts, add speaker notes, insert images, reorder slides' to improve specificity.
Include natural keyword variations like 'slide deck', 'slideshow', '.gslides', 'Google presentation' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Slides) and two broad actions (read and write presentations), but does not list specific concrete actions like creating slides, adding speaker notes, modifying layouts, inserting images, etc. | 2 / 3 |
Completeness | Describes a minimal 'what' (read and write presentations) but completely lacks a 'Use when...' clause or any explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' itself is also quite weak, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes 'Google Slides' and 'presentations' which are relevant keywords, but misses common variations like '.pptx', 'slide deck', 'slideshow', 'presentation editing', or 'slides'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Google Slides' is fairly specific and distinguishes it from generic document or PDF skills, but 'presentations' could overlap with PowerPoint or other presentation tools without clearer scoping. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a reasonable structural overview of the Google Slides CLI interface with good progressive disclosure via the shared skill reference. However, it lacks concrete executable examples (e.g., creating a presentation, adding a slide via batchUpdate) and the API method descriptions are verbose copy-paste from docs rather than distilled actionable guidance. Adding at least one end-to-end example and trimming the method descriptions would significantly improve it.
Suggestions
Add at least one concrete, copy-paste-ready example showing a full command (e.g., `gws slides presentations create --params title='My Deck'` and a `batchUpdate` with `--json` to add a slide).
Trim the API method descriptions to one-line summaries—remove the verbose explanations about validation behavior and reply ordering that Claude already understands.
Add a brief workflow for common multi-step operations (e.g., create presentation → get presentation ID → batchUpdate to add slides) with a validation checkpoint (e.g., verify the presentation was created before updating).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The `batchUpdate` description is overly verbose with explanations Claude doesn't need (e.g., 'Each request is validated before being applied. If any request is not valid, then the entire request will fail...'). These read like API docs copy-pasted verbatim rather than distilled for Claude. | 2 / 3 |
Actionability | Provides the CLI pattern and discovery commands (`gws schema`), but lacks any concrete example of actually creating or updating a presentation with specific `--params` or `--json` flags. No executable end-to-end example is given. | 2 / 3 |
Workflow Clarity | The 'Discovering Commands' section establishes a two-step pattern (inspect then call), but there's no explicit workflow for common multi-step tasks like creating a presentation and adding slides, and no validation/verification steps for batch updates which are destructive operations. | 2 / 3 |
Progressive Disclosure | Cleanly references the shared skill file for auth and global flags, keeps the skill focused on Slides-specific content, and the structure is well-organized with clear sections. For a skill of this size, the organization is appropriate. | 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.