gog-slides

Google Slides operations through gog.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/gog-slides/SKILL.md

Quality

Content

86%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 an exemplary terse command-dispatch skill: executable safe-start commands, a complete one-line-per-command reference table, explicit safety rules for writes and deletes, and runtime `--help`/`schema` lookup instead of inlined flag documentation. The only meaningful gap is the absence of a worked example and a post-write verification step for its destructive operations.

Dimension	Reasoning	Score
Conciseness	The body is lean throughout: a two-line intro, three safe-start commands, six terse safety bullets, a one-line-per-command table, and a closing pointer to `--help` and `gog schema`. No concept explanations Claude already knows, no padding — every token earns its place.	5 / 5
Actionability	Concrete, copy-paste commands are given ('gog auth list --check --json --no-input', 'gog schema slides --json', 'gog --readonly --account user@example.com slides --help') alongside a complete command table. Falls short of 5 because no worked example covers a common case (e.g. create-from-markdown or insert-text with real arguments) and the account placeholder must be substituted.	4 / 5
Workflow Clarity	The 'Safe start' section sequences auth check -> schema -> readonly help, and explicit checkpoints exist ('--dry-run before supported writes', 'Confirm the exact account, object, and mutation before any write or delete'). Not 5: despite destructive commands (delete-slide, replace-slide), there is no post-write verification or error-recovery feedback loop.	4 / 5
Progressive Disclosure	A compact (~57 line) body with well-organized sections, one clearly-signaled one-level reference ('Read `../gog/SKILL.md` first for shared auth, output, safety, and live-write rules'), and per-command detail delegated to runtime `--help`/`gog schema`. No bundle files exist, and the structure fits the simple-skill guidance for a 5.	5 / 5
	Total	18 / 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 correctly names the domain (Google Slides) and the tool (gog) but stops there: no concrete capabilities, no synonyms, and no 'Use when...' trigger guidance. It is a stub that fails the rubric's completeness cap and reads closer to the rubric's minimal examples than its good ones.

Suggestions

Add a 'Use when...' trigger clause, e.g. 'Use when the user mentions Google Slides, presentations, decks, or slide IDs' — its absence caps completeness at 3.

List 3-4 concrete actions from the command table, e.g. 'Create presentations from markdown, add slides with images, find-and-replace text, and export decks as PDF or PPTX.'

Include natural synonyms and extensions users say ('presentations', 'decks', '.pptx', 'speaker notes') to raise trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description 'Google Slides operations through gog' names the domain and tool but 'operations' is generic — no concrete actions like create, edit, or export are stated. This matches the anchor 'Names the domain but actions are minimal or generic', not 3 since not even one specific action verb appears.	2 / 5
Completeness	A domain-level 'what' is present ('Google Slides operations through gog') but there is no 'Use when...' or equivalent trigger clause, capping completeness at 3 per the rubric guidelines. Not 2 because the 'what' is not extremely vague — the domain and tool are clearly named.	3 / 5
Trigger Term Quality	'Google Slides' is a natural phrase users would say, but common variations and synonyms are missing — no 'presentations', 'decks', 'slides', or '.pptx'. Some relevant keywords exist, but coverage lacks the synonyms the anchor-5 example requires.	3 / 5
Distinctiveness Conflict Risk	'Google Slides' carves a clear niche with distinct triggers and low conflict risk, but 'operations' and the shared 'gog' tool prefix leave minor overlap with sibling gog skills. Mostly distinct with minor overlap risk — anchor 4.	4 / 5
	Total	12 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: openclaw/gogcli
Path: .agents/skills/gog-slides/SKILL.md
Commit: 414e2ff

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