CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gog-contacts

Google Contacts through gog. Use for personal contacts, contact groups, and other contacts, with directory lookup also available; use gog-people for the caller profile or Workspace directory profiles.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

93%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.

An exemplary lean CLI skill body: executable safe-start commands, a complete command table with explicit syntax-discovery pointers, and clear pre-write safety checkpoints. The only gap is the absence of post-write verification or an error-recovery loop for its destructive and batch operations.

DimensionReasoningScore

Conciseness

At roughly 45 lines with zero padding, the body never explains concepts Claude already knows — every line is operational (commands, flags, a command table, syntax pointers). This matches anchor 5: lean, efficient, every token earning its place.

5 / 5

Actionability

The 'Safe start' block gives three copy-paste-ready commands (e.g. 'gog --readonly --account user@example.com contacts search alice --json --wrap-untrusted'), the command table maps all twelve subcommands to purposes, and 'gog contacts <command> --help' plus 'gog schema contacts <command> --json' provide exact syntax — fully executable guidance covering common cases (anchor 5).

5 / 5

Workflow Clarity

The safe-start sequence (auth check → schema → read-only search) plus pre-write checkpoints ('--readonly', '--dry-run before supported writes', 'Confirm the exact account, object, and mutation before any write or delete') satisfy the destructive/batch validation requirement, so the cap of 3 does not apply. It stops short of anchor 5 because there is no post-write verification step (e.g. re-get the contact to confirm the mutation) and no error-recovery feedback loop.

4 / 5

Progressive Disclosure

No bundle files exist, and this under-50-line body is well organized into 'Safe start' and 'Commands' sections — per the simple-skill guidance that merits a 5. Bulk detail is appropriately deferred to '--help' and 'gog schema … --json' rather than inlined, and the one external dependency ('Read ../gog/SKILL.md first for shared auth, output, safety, and live-write rules') is clearly signaled and one level deep.

5 / 5

Total

19

/

20

Passed

Description

73%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.

A concise, third-person description with an explicit 'Use for…' trigger clause and excellent boundary guidance against a sibling skill. Its main weakness is that it names contact categories rather than concrete operations, leaving the 'what' at the domain level.

Suggestions

Name the key operations in the description (e.g., create, update, delete, search, dedupe, and export contacts) so the 'what' goes beyond naming the domain and object types.

Add one or two natural synonyms such as 'address book' or 'contact list' to broaden trigger-term coverage.

Make the trigger clause situational rather than purely categorical, e.g. 'Use when the user asks to find, edit, merge, or clean up contacts or contact groups in Google.'

DimensionReasoningScore

Specificity

The description names the domain and tool ("Google Contacts through gog") and enumerates entity types ("personal contacts, contact groups, and other contacts, with directory lookup also available"), but lists no concrete operations such as create, update, search, dedupe, or export — matching anchor 3 (domain named, actions incomplete) rather than anchor 4 (several specific actions).

3 / 5

Completeness

Both parts are present: 'what' is stated ("Google Contacts through gog") and 'when' is explicit ("Use for personal contacts, contact groups, and other contacts, with directory lookup also available"). It is not a 5 because the 'what' side names the domain but not the operations performed, and the trigger clause enumerates object types rather than concrete trigger situations.

4 / 5

Trigger Term Quality

Natural phrases users would say are present ("contacts", "contact groups", "other contacts", "directory lookup"), giving good keyword coverage; a few natural synonyms like "address book" or "contact list" are missing, so it falls just short of anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The niche is clear ("Google Contacts through gog") and it explicitly disambiguates from the sibling skill ("use gog-people for the caller profile or Workspace directory profiles"), giving distinct triggers with minimal conflict risk — a clean match for anchor 5.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

openclaw/gogcli

Path

.agents/skills/gog-contacts/SKILL.md

Reviewed

Table of Contents

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.