gog-contacts

Google Contacts operations through gog.

Quality

72%

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

87%

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

The body is lean, executable, and well-structured for a simple CLI-wrapper skill, with strong actionability and progressive disclosure. The main gap is the absence of an explicit feedback loop for destructive operations.

Suggestions

Add a short validate-then-act loop for destructive commands: run with '--dry-run', inspect the output, then confirm before the real write/delete.

For dedupe merges, show an explicit review/confirm step before applying the merge so the workflow has a clear checkpoint.

Dimension	Reasoning	Score
Conciseness	Lean, command-first content with no background explanation of concepts Claude already knows; every line is actionable and earns its place.	3 / 3
Actionability	Provides copy-paste safe-start commands, a complete command-purpose table, and explicit pointers to '--help' and 'schema ... --json' for the machine-readable contract.	3 / 3
Workflow Clarity	Safety bullets give validation cues ('--readonly', '--dry-run', 'confirm the exact account, object, and mutation before any write or delete'), but there is no structured validate→fix→retry feedback loop for destructive/batch ops like dedupe or delete.	2 / 3
Progressive Disclosure	Under 50 lines, organized into 'Safe start' and 'Commands', with a single clearly-signaled one-level reference ('../gog/SKILL.md') and '--help'/'schema' for deeper detail.	3 / 3
	Total	11 / 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 stakes out a clear niche, but it is generic about actions ('operations') and omits explicit 'Use when' trigger guidance. Adding concrete verbs and a trigger clause would raise specificity and completeness.

Suggestions

Add a 'Use when...' clause with natural triggers, e.g., 'Use when managing Google Contacts, adding or finding contacts, exporting vCards, or deduplicating an address book'.

Replace the vague 'operations' with concrete actions like 'create, search, update, delete, and dedupe Google Contacts'.

Dimension	Reasoning	Score
Specificity	Names the concrete domain ('Google Contacts') and tool ('gog'), but 'operations' is abstract and lists no specific actions, so it stops short of the multi-action anchor.	2 / 3
Completeness	It states what the skill does but provides no 'Use when...' trigger guidance, which caps completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	'Google Contacts' is a natural term a user would say, but no common variations (e.g., 'contacts', 'address book') are included.	2 / 3
Distinctiveness Conflict Risk	'Google Contacts operations through gog' scopes a clear, specific niche that is unlikely to trigger for unrelated skills.	3 / 3
	Total	9 / 12 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: 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.