gws-people
by googleworkspacegws-people is the Google People API skill in googleworkspace/cli for managing contacts, contact groups, and profile records from the command line. It fits CRM Operations and admin automation when you need repeatable gws-people usage instead of manual API lookup.
This skill scores 74/100, which is an acceptable but limited listing candidate for directory users. The repo provides real Google People API workflow coverage and enough command structure to trigger the skill, but users should expect to rely on the broader gws shared docs for auth and operational rules, since this file is mostly a resource/method reference rather than a complete end-to-end guide.
- Clear trigger pattern: `gws people <resource> <method> [flags]` plus a `cliHelp` hint makes it easy for agents to invoke correctly.
- Substantial API coverage for contactGroups, people, and other People API resources, with method-level descriptions that support concrete task execution.
- No placeholder or experimental markers, and the frontmatter includes a valid skill definition with a required `gws` binary.
- Operational setup is split out to `../gws-shared/SKILL.md`, so users may need to consult another skill before they can run it confidently.
- The file has no install command and no support files, which limits immediate adoption guidance and reduces standalone discoverability.
Overview of gws-people skill
What the gws-people skill does
The gws-people skill is the Google People API workflow inside googleworkspace/cli. It helps you manage contacts, contact groups, and profile-related records from the command line with the gws people family of commands. Use the gws-people skill when you need repeatable contact operations, not a one-off prompt.
Who should install it
This is a good fit for CRM Operations, admin tooling, and automation tasks where contact data needs to be inspected, grouped, or updated consistently. It is most useful when you want a structured CLI flow for Google People rather than manually exploring API docs or guessing request shapes.
What matters before adoption
The main value of gws-people is that it narrows the job to a specific resource set and command pattern: gws people <resource> <method> [flags]. The main blocker is dependency and context: it requires the gws binary and the shared auth/security guidance in ../gws-shared/SKILL.md. It also follows API constraints that matter in practice, especially sequential mutation behavior for the same user.
How to Use gws-people skill
Install and verify the shared setup
Install with npx skills add googleworkspace/cli --skill gws-people. Before running anything, confirm the shared prerequisite exists: read ../gws-shared/SKILL.md for auth, global flags, and security rules. If your workspace does not have it, run gws generate-skills first. This matters because gws-people usage depends on the shared CLI conventions, not just the skill folder.
Shape your request around the command pattern
A useful prompt should name the resource, the method, the target account context, and the desired outcome. For example, ask for “a gws people contactGroups list command to inspect my contact groups” or “a safe sequence to create and then rename a contact group.” For gws-people for CRM Operations, include whether you are auditing, cleaning, segmenting, or syncing contacts, because that changes which resource and method are appropriate.
Read the right files first
Start with SKILL.md, then inspect ../gws-shared/SKILL.md. If you are deciding whether the skill fits your workflow, read the API resource list in SKILL.md before anything else. That is where the practical boundary shows up: contactGroups, otherContacts, and people are supported, but the skill is not a general-purpose CRM.
Use the skill with workflow constraints in mind
gws-people usage is strongest when you keep writes sequential for the same user and avoid batching assumptions that the API does not support well. For high-signal work, ask for the exact resource, the safest method, and any validation step after the change. If you are unsure of the target resource, ask for a discovery command first rather than jumping straight to mutation.
gws-people skill FAQ
Is gws-people only for advanced users?
No. It is usable by beginners if they can follow a CLI workflow and are willing to inspect the shared gws setup first. The skill is more about having the right resource and method than about writing complex code.
When should I not use gws-people?
Do not use it if you need a broad CRM system, UI-only contact management, or non-Google data sources. It is also a poor fit if your task requires unsupported automation around contact records outside the People API model.
How is this different from a normal prompt?
A normal prompt may produce a generic answer. The gws-people skill gives you a command-shaped workflow, the relevant resource set, and the key constraint that mutate requests for the same user should be sequential. That reduces trial and error when you are working in Google Workspace admin or CRM Operations.
What is the main installation dependency?
The key dependency is the gws CLI plus the shared gws skill context. If that base layer is missing or misconfigured, gws-people install will not be enough to make the workflow usable.
How to Improve gws-people skill
Give the skill a precise operation target
The best gws-people results come from prompts that specify the object, action, and scope. “List all contact groups for the current authenticated user” is better than “help with contacts.” “Update one named contact group without duplicates” is better than “fix my groups.” Precision helps the skill choose the right People resource and avoids unnecessary steps.
Include the operational constraint that matters most
If your task touches writes, say whether the change must be safe, sequential, audited, or reversible. The repository notes sequential mutation behavior for the same user, and that is the kind of detail that materially changes output quality. For CRM Operations, also mention whether the task is cleanup, enrichment, grouping, or profile review.
Iterate from discovery to action
A strong gws-people guide usually starts with a read or list command, then narrows to a single mutation. If the first output is too broad, ask for the exact gws people command, the required flags, and the validation check after the change. This produces better gws-people usage than asking for a fully generic workflow in one step.