CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gog-slides

Google Slides through gog. Use for presentations, slides, text, images, speaker notes, and exports.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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.

A tightly written command-catalog skill: lean token usage, executable safe-start commands, explicit write-safety checkpoints, and clean deferral of per-command detail to runtime help and schema discovery. The main gap is the absence of any worked example of a typical operation and any post-write verification step.

Suggestions

Add one or two copy-paste-ready examples of common operations, e.g., creating a deck from markdown or inserting text by objectId.

Add a post-write verification step to the workflow, e.g., "After a write, confirm the result with `gog slides read-slide` or `info` before reporting success."

State how to handle a failed write (e.g., inspect the error, re-run with the corrected objectId/range) to close the feedback loop for destructive operations.

DimensionReasoningScore

Conciseness

The body is lean and dense: a compact safe-start command block, five terse safety bullets, and a command table where every row states a command and its purpose in one line. No concepts Claude already knows are explained; the only non-essential text is a one-line build-artifact comment.

5 / 5

Actionability

The safe-start block ("gog auth list --check --json --no-input", "gog schema slides --json") is copy-paste ready, and the footer gives a concrete discovery contract ("Run `gog slides <command> --help`... `gog schema slides <command> --json`"). Not anchor 5 because no worked example of a common operation (e.g., an actual `create-from-markdown` or `insert-text` invocation with arguments) is shown.

4 / 5

Workflow Clarity

There is a clear entry sequence (read the parent gog skill, check auth, inspect schema, explore with --readonly) and explicit write-safety checkpoints ("--dry-run before supported writes", "Confirm the exact account, object, and mutation before any write or delete"), so the destructive-operation cap does not apply. Not anchor 5 because there is no post-write verification or feedback loop (e.g., re-read the slide with `read-slide`/`info` to confirm the mutation).

4 / 5

Progressive Disclosure

The single-file skill is well organized into overview sections, per-command details are delegated to runtime `--help` and machine-readable `schema` output rather than inlined, and the one file reference ("Read `../gog/SKILL.md` first for shared auth, output, safety, and live-write rules") is clearly signaled, states exactly what it covers, and is one level deep.

5 / 5

Total

18

/

20

Passed

Description

70%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.

A concise, third-person description that names a distinct niche and includes an explicit trigger clause with natural keywords. Its main weakness is the absence of concrete action verbs, which leaves the capability picture implied by object nouns rather than stated.

Suggestions

Replace the noun list with concrete actions, e.g., "Create, edit, and export Google Slides presentations: add slides, insert text and images, update speaker notes, export to PDF/PPTX."

Add missing natural trigger terms and synonyms such as "deck", "slide deck", and ".pptx" to the "Use for" clause.

Make the "when" more explicit, e.g., "Use when the user mentions Google Slides, slide decks, or speaker notes, or asks to export a presentation."

DimensionReasoningScore

Specificity

"Google Slides through gog" names the domain clearly, and "text, images, speaker notes, and exports" list capability objects, but almost no concrete action verbs are given (only "exports" reads as an action). It sits between anchor 2 (minimal actions) and anchor 3 (1-2 concrete actions): more concrete than a bare domain claim, but not the several specific actions of anchor 4.

3 / 5

Completeness

The "what" is present ("Google Slides through gog" plus the capability list) and an explicit "Use for..." trigger clause provides the "when". Not anchor 5 because the "what" lacks explicit action verbs and the "when" clause could name more concrete trigger phrases (e.g., "when the user mentions Google Slides or asks to build a deck").

4 / 5

Trigger Term Quality

"presentations, slides, text, images, speaker notes, and exports" are natural terms users would say, giving good keyword coverage. Not anchor 5 because common synonyms and file extensions like "deck", "slide deck", or "pptx" are missing.

4 / 5

Distinctiveness Conflict Risk

"Google Slides through gog" carves out a clear, tool-anchored niche with minimal conflict risk. Not anchor 5 because generic trigger words like "presentations", "slides", and "speaker notes" overlap closely related presentation skills (e.g., a PowerPoint/pptx skill).

4 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

openclaw/gogcli

Path

.agents/skills/gog-slides/SKILL.md

Reviewed

Table of Contents

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.