google-slides-automation

Lightweight Google Slides integration with standalone OAuth authentication. No MCP server required. Full read/write access.

Quality

62%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/google-slides-automation/SKILL.md

The canonical home for this skill is google-slides in sanjay3290/ai-skills

Quality

Content

76%Weight 40%Scale 1-5

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

The body is a highly actionable, well-structured command reference that assumes Claude's competence and avoids concept padding. Its main gap is the absence of validation feedback loops around the destructive and batch operations, which caps workflow clarity.

Suggestions

Add an explicit verification step before destructive ops, e.g. run get-metadata to confirm the slide object ID before delete-slide, and re-run get-text after batch-update to confirm changes.

Note that scripts/auth.py and scripts/slides.py are referenced but no scripts/ bundle is present; ship the scripts or clarify how they are obtained.

Consider moving the slide-layout list and output-format JSON examples into a short reference file to keep SKILL.md a leaner overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command examples with brief inline comments and no padding about concepts Claude already knows; the only minor trim is the opening line that duplicates the frontmatter description, placing it at 'efficient; minor instances of over-explanation that could be trimmed'.	4 / 5
Actionability	Every section gives fully executable, copy-paste-ready commands with realistic arguments covering the common cases (get-text, find, create, add-slide, replace-text, delete-slide, batch-update), matching the 'fully executable; copy-paste ready' anchor.	5 / 5
Workflow Clarity	Setup and command flows are clearly sequenced, but destructive (delete-slide) and batch (batch-update) operations have no explicit validate-then-proceed feedback loop; per the scoring notes this caps workflow clarity at 3 even though the single-purpose structure is otherwise clear.	3 / 5
Progressive Disclosure	Content is well-organized into clearly labeled sections with no nested or buried references, but the ~130-line body inlines everything (layouts list, output-format JSON) with no bundle files or one-level-deep references to split out detail, fitting 'good structure; most content appropriately placed; minor organization gaps'.	4 / 5
	Total	16 / 20 Passed

Description

48%Weight 40%Scale 1-5

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 third-person and identifies a clear niche, but it is generic about capabilities and entirely lacks trigger guidance. Adding concrete actions and a 'Use when...' clause would materially raise specificity and completeness.

Suggestions

Replace 'Full read/write access' with concrete actions, e.g. 'Create and edit presentations, add slides, find/replace text, extract slide content.'

Add a trigger clause such as 'Use when the user asks to create, edit, search, or extract text from Google Slides presentations.'

Include natural synonyms (presentations, slides, decks) alongside 'Google Slides' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Google Slides integration') and gestures at capability ('Full read/write access'), but never lists concrete actions like create, add-slide, replace-text, or extract — 'read/write access' is a generic capability claim, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It clearly states what the skill does (Google Slides integration with OAuth, read/write access) but provides no 'Use when...' clause or equivalent trigger guidance; per the judging guidelines a missing explicit trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	'Google Slides' is a strong natural term a user would say, but the description omits common variations and synonyms (presentations, slides, decks, .gslides), landing at 'some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	'Google Slides integration' is a clear, distinct niche with minimal conflict risk, though 'Full read/write access' leaves minor overlap with adjacent Google Workspace/presentation skills, fitting 'mostly distinct; minor overlap risk with closely related skills' rather than a clean 5.	4 / 5
	Total	12 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 17 missing	Warning

	Total	14 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/google-slides-automation/SKILL.md
Commit: 57c135b

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.