gog-contacts

Google Contacts operations through gog.

Quality

67%

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-contacts/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 a tight, well-structured operational reference with executable safe-start commands, a complete command table, and appropriate deferral to --help/schema and the shared gog skill. The main gap is the absence of an explicit validate-retry feedback loop for destructive operations.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient: a terse safe-start block, a compact command table, and a pointer to ../gog/SKILL.md for shared rules, with no over-explanation of concepts Claude already knows.	5 / 5
Actionability	Copy-paste-ready safe-start commands and a full command table give concrete executable guidance, but per-command flag usage is deferred to --help/schema rather than shown, leaving minor gaps.	4 / 5
Workflow Clarity	A clear safe-start sequence (auth check, schema, readonly probe) plus checkpoints (--readonly, --dry-run, confirm-before-write/delete) is present for destructive operations; it lacks an explicit validate-fix-retry feedback loop, so it sits at 4 rather than 5.	4 / 5
Progressive Disclosure	Under 50 lines with well-organized sections (Safe start, Commands) and a single one-level-deep, clearly signaled reference to ../gog/SKILL.md; no bundle files are present, so the simple-skill exception applies.	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 is accurate and distinct but terse and generic: it names the domain without listing concrete actions or providing an explicit 'use when' trigger. Adding 1-2 specific operations and a trigger clause would raise specificity and completeness.

Suggestions

List 1-2 concrete actions in the description, e.g. 'search, create, and update Google Contacts through gog'.

Add an explicit 'Use when...' trigger clause, e.g. 'Use when the user asks to manage Google Contacts or contact lists.'

Include natural synonyms/extensions (e.g. 'contacts', 'address book', '.vcf') to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Google Contacts operations through gog.') but the action word 'operations' is generic with no concrete capabilities listed, matching the score-2 anchor 'Names the domain but actions are minimal or generic'.	2 / 5
Completeness	It states a clear 'what' (Google Contacts operations via gog) but has no 'Use when...' or equivalent explicit trigger guidance, so per the judging guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	'Google Contacts' is a natural term users would say, but synonyms/variations (e.g. 'contacts', 'address book') and the jargon 'gog' are present without broader coverage, fitting 'Some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	'Google Contacts' carves a clear niche with minimal conflict risk, though the generic 'operations' and sibling gog skills leave minor overlap risk, matching 'Mostly distinct; minor overlap risk with closely related skills'.	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-contacts/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.