gog-contacts-cleanup

Google Contacts duplicate review and guarded cleanup with gog.

Quality

78%

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 ./.agents/skills/gog-contacts-cleanup/SKILL.md

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, well-sequenced skill body that gives executable commands and strong safety checkpoints for a destructive contact-merge workflow. It appropriately defers to sibling skills rather than restating their content.

Dimension	Reasoning	Score
Conciseness	The body is lean and executable with no filler — it jumps straight into numbered steps and real `gog` commands without explaining what contacts or duplicates are.	3 / 3
Actionability	Provides fully executable, copy-paste-ready commands plus concrete guidance on flagging conflicts in specific fields (names, organizations, notes, phone/email).	3 / 3
Workflow Clarity	A clear numbered sequence (detect → present → preview → apply) with explicit validation checkpoints: readonly detection in step 1, `--dry-run` preview in step 3, and 'apply only explicitly approved groups' guarding a destructive batch merge.	3 / 3
Progressive Disclosure	One-level-deep references are clearly signaled up front ('Read `../gog/SKILL.md` and `../gog-contacts/SKILL.md` first') and the body stays a concise overview with no nested or dangling references.	3 / 3
	Total	12 / 12 Passed

Description

57%

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 concise and on a clear niche but is missing an explicit usage trigger and leans on a jargony tool name. It states the what clearly without fully covering the when or natural user phrasings.

Suggestions

Add a 'Use when ...' clause naming natural triggers (e.g., 'Use when reviewing or merging duplicate Google Contacts entries').

Swap or supplement the tool name 'gog' with user-facing terms like 'merge contacts' and 'find duplicate contacts'.

Replace the abstract 'guarded cleanup' with concrete operations, e.g., 'preview merge plans and apply only approved contact merges'.

Dimension	Reasoning	Score
Specificity	It names the domain and actions ('Google Contacts duplicate review and guarded cleanup') but 'guarded cleanup' is somewhat abstract and it omits concrete operations like merging or field conflict resolution.	2 / 3
Completeness	It conveys what the skill does but lacks an explicit 'Use when...' trigger clause, which the guidelines cap at 2.	2 / 3
Trigger Term Quality	Includes natural terms ('Google Contacts', 'duplicate', 'cleanup') alongside the jargony tool name 'gog', but misses common phrasings a user might say such as 'merge contacts' or 'find duplicates'.	2 / 3
Distinctiveness Conflict Risk	The narrow Google Contacts dedup niche is clearly distinguishable from other skills and unlikely to trigger the wrong one.	3 / 3
	Total	9 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: openclaw/gogcli
Path: .agents/skills/gog-contacts-cleanup/SKILL.md
Commit: 1dbd820

Reviewed: about 23 hours 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.