gog-contacts-cleanup

Google Contacts duplicate review and guarded cleanup with gog.

Quality

68%

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

82%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, executable, well-sequenced workflow with appropriate validation safeguards for a destructive contact-merge operation. The main gaps are placeholder values in commands, the absence of a post-apply verification step, and cross-references to sibling skill files that are not present in this bundle.

Suggestions

Add a post-apply verification step (e.g. re-run the readonly dedupe to confirm no remaining approved duplicates) to close the workflow feedback loop.

Clarify how to obtain the real account and resource IDs that the example commands currently leave as placeholders.

Resolve or condition the cross-references to '../gog/SKILL.md' and '../gog-contacts/SKILL.md' so navigation does not dead-end when those files are absent.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient with no explanations of concepts Claude already knows; every line (numbered steps, two command blocks, one guardrail) earns its place.	5 / 5
Actionability	Concrete, executable 'gog' commands with real flags are provided, but account ('user@example.com') and resource IDs ('people/ONE') are placeholders, leaving minor gaps from copy-paste readiness.	4 / 5
Workflow Clarity	A clear four-step sequence with validation checkpoints (readonly detection, --dry-run preview, explicit approval gate) is present for this destructive/batch operation, but there is no post-apply verification or explicit error-recovery feedback loop.	4 / 5
Progressive Disclosure	Structure is good for a small single-purpose skill with clearly signaled one-level-deep references, but the referenced sibling files ('../gog/SKILL.md', '../gog-contacts/SKILL.md') do not resolve in the bundle, a minor navigation gap.	4 / 5
	Total	17 / 20 Passed

Description

53%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 concise and names a clear, specific niche with two concrete actions, but it lacks an explicit 'when to use' trigger clause and broader trigger-term synonyms. Adding a 'Use when...' phrase and synonyms like 'merge' or 'dedupe' would raise it.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to review, dedupe, or merge duplicate Google Contacts.'

Broaden trigger terms with natural synonyms such as 'merge contacts', 'dedupe contacts', or 'find contact duplicates'.

Expand the action list slightly (e.g. mention merge and field-level conflict review) to improve specificity coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Google Contacts' duplicates) and two concrete actions ('duplicate review' and 'guarded cleanup'), but is not comprehensive (no mention of merge, fields, or dedupe).	3 / 5
Completeness	The 'what' is clear (duplicate review and guarded cleanup), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	It includes relevant natural keywords ('Google Contacts', 'duplicate', 'cleanup') but misses common variations/synonyms a user might say such as 'merge contacts' or 'dedupe'.	3 / 5
Distinctiveness Conflict Risk	The niche is specific (Google Contacts dedupe via the 'gog' tool) and mostly distinct, but a sibling 'gog-contacts' skill referenced in the body creates minor overlap risk.	4 / 5
	Total	13 / 20 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: 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.