gws-people
Google People: Manage contacts and profiles.
55
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 brief and vague to effectively guide skill selection. It lacks specific actions, explicit trigger guidance, and natural keyword variations. The 'Google People' prefix provides minimal distinctiveness, but the description fails to communicate concrete capabilities or usage scenarios.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about Google Contacts, address book, contact information, or needs to look up/add/update people in their Google account'
Replace vague 'Manage' with specific actions: 'Create, search, update, and delete contacts; retrieve profile information; sync contact groups'
Include natural keyword variations users would say: 'Google Contacts', 'address book', 'phone numbers', 'email lookup', 'contact list'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('Manage contacts and profiles') without listing concrete actions. It doesn't specify what 'manage' means - no mention of create, update, delete, search, sync, or other specific operations. | 1 / 3 |
Completeness | Only weakly addresses 'what' with vague 'manage' language, and completely lacks any 'when' guidance or 'Use when...' clause. No explicit triggers for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('contacts', 'profiles') that users might naturally say, but misses common variations like 'address book', 'phone numbers', 'email addresses', 'Google Contacts', or 'contact list'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Google People' in the name helps distinguish from generic contact management, but 'contacts and profiles' is broad enough to potentially conflict with other contact or CRM-related skills. The 'Google' prefix provides some distinctiveness. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-organized and concise, serving as an effective API reference for the Google People CLI wrapper. However, it lacks concrete usage examples showing complete commands with parameters, and the workflow guidance could benefit from validation steps given the repeated warnings about sequential operations and potential errors.
Suggestions
Add 1-2 complete executable examples showing common operations (e.g., creating a contact, listing contact groups) with actual `--params` or `--json` flag usage
Include a brief error handling section addressing the HTTP 409 duplicate name errors and EXPIRED_SYNC_TOKEN scenarios mentioned in the API descriptions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only API resource listings and essential commands without explaining what contacts are or how APIs work. Every section serves a clear purpose. | 3 / 3 |
Actionability | Provides concrete CLI commands for discovery (`gws people --help`, `gws schema`), but lacks executable examples showing actual usage with `--params` or `--json` flags for common operations like creating or listing contacts. | 2 / 3 |
Workflow Clarity | The 'Discovering Commands' section provides a basic two-step workflow, but there's no validation checkpoint or error handling guidance. The repeated warnings about sequential mutate requests suggest validation is important but no verification steps are provided. | 2 / 3 |
Progressive Disclosure | Appropriately structured with a clear prerequisite reference to shared skills, organized API resources by category, and a discovery section. References are one level deep and clearly signaled. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- 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.