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-claude/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.

A well-structured, highly actionable command reference that assumes Claude's competence, held back by missing validation checkpoints on destructive/batch operations and the absence of any progressive file structure.

Suggestions

Add validation steps before destructive/batch operations — e.g. instruct running get-metadata to confirm a slide object ID before delete-slide, or preview replace-text matches before applying.

Confirm the referenced scripts (scripts/auth.py, scripts/slides.py) are actually bundled; if absent, either ship them or note where they live.

Consider moving the JSON output-format details and layout enumeration into a short reference file to lighten the main body.

Dimension	Reasoning	Score
Conciseness	The body is a lean command reference with brief inline comments and JSON output samples; the only redundancy is repeating the frontmatter description as the opening line.	4 / 5
Actionability	Commands are fully executable and copy-paste ready (e.g. 'python scripts/slides.py get-text "1abc..."'), with examples covering get-text, find, create, add-slide, replace-text, delete-slide, and batch-update.	5 / 5
Workflow Clarity	Setup and command groups are sequenced, but destructive ops (delete-slide) and batch ops (replace-text across all slides, batch-update) have no validation/verification checkpoints, capping this dimension at 3.	3 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections; however everything is inlined in SKILL.md with no bundle files (references/, scripts/, assets/ are absent), so there is no one-level-deep reference structure.	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 clearly identifies the domain and differentiates itself, but it is missing explicit trigger guidance and concrete action verbs, leaving 'when' and 'specificity' underdeveloped.

Suggestions

Add a 'Use when...' clause naming natural triggers, e.g. 'Use when the user asks to create or edit Google Slides presentations, search decks, or batch-update slide text.'

Replace the generic 'Full read/write access' with 2-3 concrete actions (e.g. 'create presentations, add slides, find/replace text across slides').

Include synonyms users actually say — 'presentations', 'decks', 'slides' — to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Google Slides integration') but the only action framing is the generic 'Full read/write access' — no concrete actions like create, add-slide, or find/replace are listed.	2 / 5
Completeness	It states clearly what the skill does, but there is no 'Use when...' or equivalent trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	'Google Slides' is a natural user term, but common synonyms and variations ('presentations', 'decks', 'slides', file extensions) are absent.	3 / 5
Distinctiveness Conflict Risk	'Google Slides integration' with 'standalone OAuth' and 'No MCP server required' carves a clear niche with only minor overlap risk against other presentation/Google skills.	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-claude/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.