gws-people

Google People: Manage contacts and profiles.

Quality

36%

Does it follow best practices?

Impact

—

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

Content

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 methods accessible via the `gws` CLI, but it reads more like auto-generated API documentation than an actionable skill. It lacks concrete usage examples (e.g., creating a contact with specific flags), and the repeated API descriptions add bulk without proportional value since they're discoverable via `gws schema`.

Suggestions

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

Trim the API resource descriptions to just method names and one-line summaries, since detailed behavior is discoverable via `gws schema` and the descriptions are largely copied from Google's docs.

Add a brief workflow section for mutation operations that addresses the sequential request constraint and error handling (e.g., 409 duplicate name, 400 missing personFields).

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 sequential mutation constraint mentioned repeatedly, and no error recovery guidance for the various error conditions described.	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 --help` or a reference file.	2 / 3
	Total	8 / 12 Passed

Description

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 effectively guide skill selection. It lacks concrete actions, explicit trigger conditions, and sufficient keyword coverage. It would benefit significantly from listing specific capabilities and adding a 'Use when...' clause with natural trigger terms.

Suggestions

List specific concrete actions such as 'create, search, update, and delete contacts; retrieve profile information; list contact groups' instead of the generic 'manage contacts and profiles'.

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Google Contacts, address book entries, contact groups, or people profiles.'

Include natural trigger term variations like 'Google Contacts', 'address book', 'contact list', 'phone numbers', 'email lookup' to improve matching.

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 only vaguely stated ('manage contacts and profiles') and there is no 'when' clause or explicit trigger guidance at all, which per the rubric caps completeness at 2 at best, but the 'what' is also too weak to merit a 2.	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 CRM or contact management skills without more precise triggers.	2 / 3
	Total	6 / 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: a3768d0

Reviewed: 2 months 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.