gws-slides

Google Slides: Read and write presentations.

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./gws-slides/SKILL.md

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-organized and points to a shared prerequisite cleanly, with usable discovery commands. It is held back by verbose API prose, the absence of a concrete worked example, and no validation/retry guidance for batch operations.

Suggestions

Trim the `batchUpdate` description to the essential behavior, dropping the replies/ordering prose that Claude can infer from `gws schema`.

Add at least one complete executable example, e.g. `gws slides presentations create --params '{"title":"My Deck"}'`.

Add a validation/verification step for batch operations, such as inspecting the returned replies or re-running `gws slides presentations get` to confirm changes applied.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and well-structured, but the `batchUpdate` entry is padded with API-doc prose ("Some requests have replies... Other requests do not need to return information... The order of replies matches that of the requests") that could be tightened.	2 / 3
Actionability	Concrete commands are present (`gws slides --help`, `gws schema slides.<resource>.<method>`) and the base invocation syntax is given, but there is no complete worked example with real `--params`/`--json` values that is copy-paste ready.	2 / 3
Workflow Clarity	There is a sensible inspect-then-call sequence (prerequisite → help → schema → build flags → call), but no validation checkpoint or fix-retry loop is given for the batch `batchUpdate` operation, which caps workflow clarity at 2.	2 / 3
Progressive Disclosure	The skill is short and well-organized into clear sections, with a single one-level-deep prerequisite reference to `../gws-shared/SKILL.md` that is clearly signaled; no nested or multi-level references exist.	3 / 3
	Total	9 / 12 Passed

Description

57%

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 concise and clearly names its niche, but it only partially covers capabilities and omits any explicit "when to use" trigger guidance. Adding a Use-when clause and a few more concrete actions would lift it.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to read, create, or edit Google Slides presentations or slide decks."

Expand "Read and write" into more specific concrete actions (e.g. create, fetch, batch-update, or inspect pages) to improve specificity.

Include common natural terms such as "slides", "decks", or "presentations" alongside "Google Slides" for better trigger coverage.

Dimension	Reasoning	Score
Specificity	The phrase "Read and write presentations" names the domain (presentations) and two actions, but these are generic verbs rather than the multiple specific concrete actions (e.g. extract, fill, merge) required for a 3.	2 / 3
Completeness	It states what the skill does (read and write presentations) but provides no explicit "Use when..." trigger for when Claude should invoke it, which caps completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	"Google Slides" and "presentations" are natural terms a user would say, but common variations like "slides", "decks", or "slide decks" are missing, so coverage is partial rather than complete.	2 / 3
Distinctiveness Conflict Risk	"Google Slides" names a clear niche with a distinct product trigger that is unlikely to overlap with other skills.	3 / 3
	Total	9 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 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	13 / 16 Passed

Repository: JetBrains/skills
Path: gws-slides/SKILL.md
Commit: e0f258b

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.