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 extremely terse, naming only the platform and two generic actions without elaborating on specific capabilities or providing any trigger guidance. While 'Google Slides' provides some distinctiveness, the lack of a 'Use when...' clause and absence of detailed actions make it insufficient for reliable skill selection among many options.
Suggestions
Add a 'Use when...' clause with explicit triggers, 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, export presentations.'
Include natural keyword variations users might say, such as 'slide deck', 'slideshow', 'Google presentation', or 'Slides API'.
| 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 so thin it warrants 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 overview of the Google Slides CLI interface with good progressive disclosure via the shared skill reference. However, it lacks concrete executable examples of common operations (creating presentations, adding slides, reading content) and the API method descriptions are unnecessarily verbose, essentially duplicating API documentation that Claude could discover via the schema command.
Suggestions
Add 2-3 concrete, copy-paste-ready examples showing common operations like creating a presentation and reading its content with actual --params/--json flags.
Trim the API resource descriptions to just method names and one-line summaries—the verbose behavioral details can be discovered via `gws schema`.
Add a brief workflow showing the discover → execute → verify pattern, especially for batchUpdate which can be destructive.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient, but the batchUpdate description is verbose and explains behavior Claude could infer. The descriptions for create and get also include unnecessary detail about how IDs work and what gets ignored. | 2 / 3 |
Actionability | Provides CLI syntax and discovery commands, but lacks concrete examples of actual slide operations (e.g., creating a presentation, adding a slide, reading content). No executable examples with --params or --json flags. | 2 / 3 |
Workflow Clarity | The discovery workflow (help → schema → build command) is implicit but not explicitly sequenced. For a tool that uses batchUpdate with destructive potential, there are no validation or verification steps mentioned. | 2 / 3 |
Progressive Disclosure | Cleanly references the shared skill file for auth/security, 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
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.