gws-people

Google People: Manage contacts and profiles.

Quality

36%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/gws-people/SKILL.md

Quality

Discovery

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too terse and vague to be effective for skill selection. It lacks concrete actions, explicit trigger guidance ('Use when...'), and sufficient natural keywords. It would be easily confused with other contact or profile management skills.

Suggestions

Add specific concrete actions such as 'Create, search, update, and delete contacts; retrieve profile information; list contact groups' to improve specificity.

Add an explicit 'Use when...' clause with trigger terms like 'Use when the user asks about Google Contacts, address book, contact lists, people profiles, or managing phone numbers and email addresses.'

Include file/format references or API-specific terms like 'Google Contacts', 'contact groups', 'vCard' to improve distinctiveness from other contact management skills.

Dimension	Reasoning	Score
Specificity	The description says 'Manage contacts and profiles' which is extremely vague. It does not list any concrete actions like 'create contacts', 'search contacts', 'update profile fields', 'merge duplicates', etc.	1 / 3
Completeness	The 'what' is very weak ('manage contacts and profiles') and there is no 'when' clause or explicit trigger guidance at all, which per the rubric should cap completeness at 2 — but since the 'what' is also weak, this scores a 1.	1 / 3
Trigger Term Quality	It includes 'contacts' and 'profiles' which are natural terms users might say, but misses common variations like 'address book', 'phone numbers', 'email addresses', 'Google Contacts', or 'people API'.	2 / 3
Distinctiveness Conflict Risk	'Google People' in the name helps narrow the domain, and 'contacts and profiles' is somewhat specific, but 'manage contacts' could overlap with other contact management skills (e.g., Outlook contacts, CRM tools). The description lacks enough specificity to clearly distinguish itself.	2 / 3
	Total	6 / 12 Passed

Implementation

50%

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

This skill serves as a reference catalog of Google People API resources and methods but lacks concrete usage examples that would make it immediately actionable. The API descriptions are largely copied from Google's documentation, adding token cost without proportional value. The discovery workflow is a good start but needs concrete examples and validation/error-handling guidance.

Suggestions

Add 2-3 concrete, copy-paste-ready examples of common operations (e.g., creating a contact, listing contacts, searching) with actual `--params` and `--json` flags.

Trim the API method descriptions to just the method name and a brief purpose — remove Google-specific implementation details like sync token behavior and error codes that can be discovered via `gws schema`.

Add a brief workflow for mutate operations that addresses the sequential request requirement and error handling (e.g., check for 409 duplicates, retry logic).

Dimension	Reasoning	Score
Conciseness	The content includes lengthy API descriptions that are essentially copied from Google's API docs, including details like error codes, sync token behavior, and propagation delays that Claude could look up or that could be discovered via the CLI. However, it's not egregiously padded with basic concept explanations.	2 / 3
Actionability	The skill provides the CLI syntax pattern and a discovery mechanism via `gws schema`, but lacks concrete executable examples of common operations like creating a contact, listing contacts, or searching. Users must figure out the actual flag/param syntax themselves.	2 / 3
Workflow Clarity	The 'Discovering Commands' section provides a two-step discovery workflow (browse then inspect), but there are no validation steps, no examples of handling the noted sequential mutation requirement, and no error recovery guidance despite multiple warnings about latency/failures and sync token expiration.	2 / 3
Progressive Disclosure	The skill references a shared prerequisite file (`../gws-shared/SKILL.md`) which is good progressive disclosure, but the API resource listing is a large inline block that could be better organized or summarized, with details deferred to `gws people --help`.	2 / 3
	Total	8 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning

	Total	10 / 11 Passed

Repository: googleworkspace/cli
Commit: c7c6646

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