gog-photos

Google Photos operations through gog.

Quality

63%

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-photos/SKILL.md

Quality

Content

90%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 lean, executable skill page: a safe-start preflight with real flags, a compact command table, and clear one-level-deep pointers to shared rules and per-command contracts. Its only weakness is workflow clarity being preflight-style rather than a full validate-retry loop, which is acceptable for a thin wrapper skill.

Dimension	Reasoning	Score
Conciseness	The body is lean and every line earns its place — a short shared-rules pointer, three safe-start commands, six terse bullets, and a compact command table — with no concept over-explanation and no padding, matching the score-5 anchor 'Lean and efficient; assumes Claude's competence; every token earns its place.'	5 / 5
Actionability	Guidance is fully executable: copy-paste-safe 'Safe start' bash commands, concrete flag recommendations (--account, --readonly, --no-input, --dry-run), a complete command table, and exact help/schema invocations, matching the score-5 anchor 'Fully executable; copy-paste ready code or commands; specific examples cover the common cases.'	5 / 5
Workflow Clarity	The 'Safe start' block gives a clear, ordered preflight sequence (auth check -> schema -> readonly help) with safety checkpoints (confirm account/object/mutation, use --readonly, --dry-run before writes), but it is a preflight rather than a full validate->fix->retry loop, fitting the score-4 anchor 'Clear sequence with most checkpoints present; minor validation gaps.'	4 / 5
Progressive Disclosure	Structure is clean with well-signaled one-level-deep pointers (to ../gog/SKILL.md for shared rules and to per-command --help / schema JSON for contracts), and the bulk command detail is appropriately deferred rather than inlined; only a minor gap in that the command table could link out to per-command references, so it sits at score-4 'Good structure; most content is appropriately placed.'	4 / 5
	Total	18 / 20 Passed

Description

36%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 a terse, third-person label that names the domain and tool but omits concrete actions and any 'Use when' trigger guidance. It is clean and non-generic but underspecified for both capability coverage and invocation triggers.

Suggestions

List concrete actions in the description, e.g. 'List, search, get, and download app-created media items, and access user-selected media via the Photos Picker API.'

Add an explicit trigger clause, e.g. 'Use when the user wants to manage Google Photos media or mentions Google Photos, photo media items, or the Photos Picker API.'

Include natural synonyms/extensions (e.g. 'Google Photos, photo media, picker') to strengthen trigger-term coverage beyond the bare product name.

Dimension	Reasoning	Score
Specificity	"Google Photos operations through gog" names the domain (Google Photos) and the tool (gog) but states no concrete actions — download, list, search, picker are all absent, matching the score-2 anchor 'Names the domain but actions are minimal or generic.'	2 / 5
Completeness	A clear 'what' is present (Google Photos operations through gog) but there is no 'when' / 'Use when...' clause at all; per the judging guidelines a missing trigger clause caps completeness at 3, and the total absence of any when-guidance places it at the score-2 anchor 'Has a vague what and no when.'	2 / 5
Trigger Term Quality	The phrase 'Google Photos' is a natural term users say, and 'photos' is a common keyword, but there are no synonyms or file extensions and no trigger phrases beyond the bare product name, fitting the score-3 anchor 'Some relevant keywords but missing common variations or synonyms.'	3 / 5
Distinctiveness Conflict Risk	Scoping to 'Google Photos through gog' is reasonably distinct from other skills, but the description is generic enough that it could overlap with a sibling gog-* skill (e.g. gog-drive) when a user just says 'photos', matching the score-3 anchor 'Somewhat specific but could still overlap with similar skills.'	3 / 5
	Total	10 / 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-photos/SKILL.md
Commit: eb85a99

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.