google-slides

Use this skill any time the user wants to create a Google Slides deck from a template, mentions "Google Slides" with a template in mind, provides a Google Slides URL plus a content brief, or asks to "make slides", "build a deck", "generate a presentation", or "fill this template" in a Google Workspace context. Requires the Studio Google Slides + Google Drive MCP connectors. Do NOT use for PowerPoint (.pptx) creation (use the pptx skill), for editing without a template, or for authoring a new template (template authoring has its own skill).

Quality

87%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

85%

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

This is a strong, well-structured skill that provides highly actionable guidance with clear workflow sequencing, explicit validation steps, and excellent progressive disclosure to supporting references. The failure modes table is particularly valuable for error recovery. Minor verbosity in the introductory sections and template contract explanation prevents a perfect conciseness score, but overall token efficiency is good.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient and avoids explaining basic concepts Claude already knows. However, the 'Why this shape?' paragraph and some of the explanatory text around the template contract could be tightened. The failure modes table is valuable but some entries are slightly verbose.	2 / 3
Actionability	The skill provides specific tool names, exact parameter names (e.g., `requests_yaml`, `replacements_yaml`), concrete workflow steps with named API calls, and a detailed failure modes table with specific symptoms, causes, and fixes. The guidance is highly concrete and executable.	3 / 3
Workflow Clarity	The 10-step workflow is clearly sequenced with explicit validation (Step 9 QA loop until 0 findings), recovery guidance in the failure modes table, and clear checkpoints (user sign-off at step 4, inspection at step 5, QA at step 9). The preference for hiding over deleting adds a safety/reversibility checkpoint.	3 / 3
Progressive Disclosure	The skill provides a clear overview with well-signaled one-level-deep references: `references/workflow.md` for detailed workflow, `references/batch-update-recipes.yaml` for recipes, `references/pattern-selection.md` for pattern matching, and `references/filling-content.md` for content rules. The main SKILL.md stays at summary level while pointing to specifics. Note: bundle files were not provided for verification, but the structure and signaling are exemplary.	3 / 3
	Total	11 / 12 Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong description with excellent trigger terms, clear 'when to use' guidance, and outstanding distinctiveness through explicit negative boundaries. Its main weakness is that it focuses heavily on when to invoke the skill rather than detailing the concrete actions it performs (e.g., what specifically happens when filling a template). The description also uses second person ('Use this skill') which is a minor style issue but doesn't significantly harm functionality.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Replaces placeholder text, inserts images, populates slide content from a brief, and duplicates template slides as needed.'

Dimension	Reasoning	Score
Specificity	The description names the domain (Google Slides deck from a template) and mentions some actions like 'create', 'fill this template', but it doesn't list multiple concrete actions the skill performs (e.g., replacing placeholder text, inserting images, duplicating slides). It focuses more on when to use it than what it concretely does.	2 / 3
Completeness	The description explicitly answers both 'when' (with a detailed 'Use this skill any time...' clause listing multiple trigger scenarios) and 'what' (creating Google Slides decks from templates). It also includes helpful negative boundaries (when NOT to use it), which strengthens the 'when' guidance.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms: 'Google Slides', 'make slides', 'build a deck', 'generate a presentation', 'fill this template', 'Google Slides URL', 'content brief', and 'Google Workspace context'. These are terms users would naturally say.	3 / 3
Distinctiveness Conflict Risk	Very clearly distinguished from related skills: explicitly excludes PowerPoint creation (references pptx skill), editing without a template, and template authoring (references its own skill). The Google Slides + template niche is well-defined and unlikely to conflict.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: treasure-data/td-skills
Commit: adb83d7

Reviewed: 6 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.