gws-admin

googleworkspace/cli · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/googleworkspace/cli --skill gws-admin
0 commentsdiscussion
summary

Manage Google Workspace users, groups, devices, and organizational settings through CLI commands.

  • Covers 20+ resource types including users, groups, Chrome OS devices, mobile devices, organizational units, domains, roles, and schemas
  • Supports full CRUD operations on most resources: create, retrieve, list, update, patch, and delete
  • Includes specialized actions like device provisioning/deprovisioning, group membership management, 2-step verification control, and user sign-out
  • Requir
skill.md

admin (directory_v1)

PREREQUISITE: Read ../gws-shared/SKILL.md for auth, global flags, and security rules. If missing, run gws generate-skills to create it.

gws admin <resource> <method> [flags]

API Resources

asps

  • delete — Deletes an ASP issued by a user.
  • get — Gets information about an ASP issued by a user.
  • list — Lists the ASPs issued by a user.

channels

  • stop — Stops watching resources through this channel.

chromeosdevices

  • action — Use BatchChangeChromeOsDeviceStatus instead. Takes an action that affects a Chrome OS Device. This includes deprovisioning, disabling, and re-enabling devices. Warning: * Deprovisioning a device will stop device policy syncing and remove device-level printers. After a device is deprovisioned, it must be wiped before it can be re-enrolled.
  • get — Retrieves a Chrome OS device's properties.
  • list — Retrieves a paginated list of Chrome OS devices within an account.
  • moveDevicesToOu — Moves or inserts multiple Chrome OS devices to an organizational unit. You can move up to 50 devices at once.
  • patch — Updates a device's updatable properties, such as annotatedUser, annotatedLocation, notes, orgUnitPath, or annotatedAssetId. This method supports patch semantics.
  • update — Updates a device's updatable properties, such as annotatedUser, annotatedLocation, notes, orgUnitPath, or annotatedAssetId.

customer

  • devices — Operations on the 'devices' resource

customers

  • get — Retrieves a customer.
  • patch — Patches a customer.
  • update — Updates a customer.
  • chrome — Operations on the 'chrome' resource

domainAliases

  • delete — Deletes a domain Alias of the customer.
  • get — Retrieves a domain alias of the customer.
  • insert — Inserts a domain alias of the customer.
  • list — Lists the domain aliases of the customer.

domains

  • delete — Deletes a domain of the customer.
  • get — Retrieves a domain of the customer.
  • insert — Inserts a domain of the customer.
  • list — Lists the domains of the customer.

groups

  • delete — Deletes a group.
  • get — Retrieves a group's properties.
  • insert — Creates a group.
  • list — Retrieves all groups of a domain or of a user given a userKey (paginated).
  • patch — Updates a group's properties. This method supports patch semantics.
  • update — Updates a group's properties.
  • aliases — Operations on the 'aliases' resource

members

  • delete — Removes a member from a group.
  • get — Retrieves a group member's properties.
  • hasMember — Checks whether the given user is a member of the group. Membership can be direct or nested, but if nested, the memberKey and groupKey must be entities in the same domain or an Invalid input error is returned. To check for nested memberships that include entities outside of the group's domain, use the checkTransitiveMembership() method in the Cloud Identity Groups API.
  • insert — Adds a user to the specified group.
  • list — Retrieves a paginated list of all members in a group. This method times out after 60 minutes. For more information, see Troubleshoot error codes.
  • patch — Updates the membership properties of a user in the specified group. This method supports patch semantics.
  • update — Updates the membership of a user in the specified group.

mobiledevices

  • action — Takes an action that affects a mobile device. For example, remotely wiping a device.
  • delete — Removes a mobile device.
  • get — Retrieves a mobile device's properties.
  • list — Retrieves a paginated list of all user-owned mobile devices for an account. To retrieve a list that includes company-owned devices, use the Cloud Identity Devices API instead. This method times out after 60 minutes. For more information, see Troubleshoot error codes.

orgunits

  • delete — Removes an organizational unit.
  • get — Retrieves an organizational unit.
  • insert — Adds an organizational unit.
  • list — Retrieves a list of all organizational units for an account.
  • patch — Updates an organizational unit. This method supports patch semantics
  • update — Updates an organizational unit.

privileges

  • list — Retrieves a paginated list of all privileges for a customer.

resources

  • buildings — Operations on the 'buildings' resource
  • calendars — Operations on the 'calendars' resource
  • features — Operations on the 'features' resource

roleAssignments

  • delete — Deletes a role assignment.
  • get — Retrieves a role assignment.
  • insert — Creates a role assignment.
  • list — Retrieves a paginated list of all roleAssignments.

roles

  • delete — Deletes a role.
  • get — Retrieves a role.
  • insert — Creates a role.
  • list — Retrieves a paginated list of all the roles in a domain.
  • patch — Patches a role.
  • update — Updates a role.

schemas

  • delete — Deletes a schema.
  • get — Retrieves a schema.
  • insert — Creates a schema.
  • list — Retrieves all schemas for a customer.
  • patch — Patches a schema.
  • update — Updates a schema.

tokens

  • delete — Deletes all access tokens issued by a user for an application.
  • get — Gets information about an access token issued by a user.
  • list — Returns the set of tokens specified user has issued to 3rd party applications.

twoStepVerification

  • turnOff — Turns off 2-Step Verification for user.

users

  • createGuest — Create a guest user with access to a subset of Workspace capabilities. This feature is currently in Alpha. Please reach out to support if you are interested in trying this feature.
  • delete — Deletes a user.
  • get — Retrieves a user.
  • insert — Creates a user. Mutate calls immediately following user creation might sometimes fail as the user isn't fully created due to propagation delay in our backends. Check the error details for the "User creation is not complete" message to see if this is the case. Retrying the calls after some time can help in this case. If resolveConflictAccount is set to true, a 202 response code means that a conflicting unmanaged account exists and was invited to join the organization.
  • list — Retrieves a paginated list of either deleted users or all users in a domain.
  • makeAdmin — Makes a user a super administrator.
  • patch — Updates a user using patch semantics. The update method should be used instead, because it also supports patch semantics and has better performance. If you're mapping an external identity to a Google identity, use the update method instead of the patch method. This method is unable to clear fields that contain repeated objects (addresses, phones, etc). Use the update method instead.
  • signOut — Signs a user out of all web and device sessions and reset their sign-in cookies. User will have to sign in by authenticating again.
  • undelete — Undeletes a deleted user.
  • update — Updates a user. This method supports patch semantics, meaning that you only need to include the fields you wish to update. Fields that are not present in the request will be preserved, and fields set to null will be cleared. For repeating fields that contain arrays, individual items in the array can't be patched piecemeal; they must be supplied in the request body with the desired values for all items.
  • watch — Watches for changes in users list.
  • aliases — Operations on the 'aliases' resource
  • photos — Operations on the 'photos' resource

verificationCodes

  • generate — Generates new backup verification codes for the user.
  • invalidate — Invalidates the current backup verification codes for the user.
  • list — Returns the current set of valid backup verification codes for the specified user.

Discovering Commands

Before calling any API method, inspect it:

# Browse resources and methods
gws admin --help

# Inspect a method's required params, types, and defaults
gws schema admin.<resource>.<method>

Use gws schema output to build your --params and --json flags.

how to use gws-admin

How to use gws-admin on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add gws-admin
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/googleworkspace/cli --skill gws-admin

The skills CLI fetches gws-admin from GitHub repository googleworkspace/cli and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/gws-admin

Reload or restart Cursor to activate gws-admin. Access the skill through slash commands (e.g., /gws-admin) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.634 reviews
  • Aditi Jackson· Dec 24, 2024

    Keeps context tight: gws-admin is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Chaitanya Patil· Dec 20, 2024

    We added gws-admin from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Diya Jackson· Nov 15, 2024

    gws-admin is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Diya Shah· Oct 6, 2024

    Useful defaults in gws-admin — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Henry Choi· Sep 13, 2024

    Registry listing for gws-admin matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Sakura Kim· Sep 13, 2024

    gws-admin is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Maya Huang· Sep 1, 2024

    gws-admin fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Min Haddad· Aug 20, 2024

    Registry listing for gws-admin matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Kwame Harris· Aug 4, 2024

    gws-admin fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Kiara Rahman· Aug 4, 2024

    Useful defaults in gws-admin — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

showing 1-10 of 34

1 / 4