gws-slides
Google Slides: Read and write presentations.
58
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/skillEvaluation — 56%
↑ 2.07xAgent success when using this skill
Validation 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 is too minimal to effectively guide skill selection. While it correctly identifies the platform (Google Slides) and basic capability (read/write), it lacks specific actions, natural trigger terms, and most critically, explicit guidance on when Claude should use this skill over alternatives.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user mentions Google Slides, slide decks, or needs to create/edit presentations in Google Workspace'
Expand specific actions beyond 'read and write' to include concrete capabilities like 'create slides, add speaker notes, modify layouts, insert images and charts'
Include more natural trigger terms users might say: 'slides', 'slide deck', 'Google presentation', 'slideshow'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Slides) and two general actions (read and write), but lacks specific concrete actions like 'create slides', 'add speaker notes', 'modify layouts', or 'insert images'. | 2 / 3 |
Completeness | Only addresses 'what' at a basic level (read/write presentations). Completely missing 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 'presentations' which are relevant keywords, but misses common variations like 'slides', '.gslides', 'slide deck', 'slideshow', or 'Google presentation'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Google Slides' provides some distinction from generic presentation tools, but 'presentations' is broad and could overlap with PowerPoint or other presentation skills without clearer differentiation. | 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.
This is a well-structured, concise skill that effectively documents the Google Slides CLI wrapper. Its main weakness is the lack of concrete, executable examples showing actual API calls with parameters. The discovery workflow is mentioned but would benefit from a complete example demonstrating the full flow from schema inspection to successful API call.
Suggestions
Add 1-2 complete executable examples showing actual API calls, e.g., creating a presentation with `gws slides presentations create --params '{...}'`
Include a brief example showing how to use `gws schema` output to construct a valid `--params` flag for a common operation like `presentations.get`
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean content that assumes Claude's competence. No unnecessary explanations of what Google Slides is or how APIs work. Every line serves a purpose. | 3 / 3 |
Actionability | Provides concrete CLI commands and method descriptions, but lacks executable examples showing actual usage with --params or --json flags. The 'Discovering Commands' section is helpful but no complete working examples are provided. | 2 / 3 |
Workflow Clarity | Shows a discovery workflow (help -> schema -> build params) but lacks explicit validation steps or feedback loops for operations like batchUpdate which could fail partially. No error handling guidance. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear reference to prerequisite shared skill file, concise overview of available resources, and well-organized discovery section. Appropriate for a simple CLI wrapper skill. | 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.