gws-keep

googleworkspace/cli · updated Apr 8, 2026

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

Create, retrieve, list, delete, and manage permissions for Google Keep notes via CLI.

  • Supports five core note operations: create, get, list, delete, and manage permissions on notes
  • List command includes pagination support with page_token and page_size parameters for handling large note collections
  • Download attachments from notes using the media resource with MIME type specification
  • Requires Google Workspace authentication via the shared gws CLI tool; inspect command schemas with g
skill.md

keep (v1)

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

gws keep <resource> <method> [flags]

API Resources

media

  • download — Gets an attachment. To download attachment media via REST requires the alt=media query parameter. Returns a 400 bad request error if attachment media is not available in the requested MIME type.

notes

  • create — Creates a new note.
  • delete — Deletes a note. Caller must have the OWNER role on the note to delete. Deleting a note removes the resource immediately and cannot be undone. Any collaborators will lose access to the note.
  • get — Gets a note.
  • list — Lists notes. Every list call returns a page of results with page_size as the upper bound of returned items. A page_size of zero allows the server to choose the upper bound. The ListNotesResponse contains at most page_size entries. If there are more things left to list, it provides a next_page_token value. (Page tokens are opaque values.) To get the next page of results, copy the result's next_page_token into the next request's page_token.
  • permissions — Operations on the 'permissions' resource

Discovering Commands

Before calling any API method, inspect it:

# Browse resources and methods
gws keep --help

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

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

Discussion

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

Ratings

4.731 reviews
  • Arjun Sharma· Dec 24, 2024

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

  • Advait Okafor· Dec 16, 2024

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

  • Pratham Ware· Dec 8, 2024

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

  • Sofia Verma· Nov 27, 2024

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

  • Maya Lopez· Nov 7, 2024

    Solid pick for teams standardizing on skills: gws-keep is focused, and the summary matches what you get after install.

  • Daniel Iyer· Oct 26, 2024

    gws-keep has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Sakshi Patil· Sep 13, 2024

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

  • Jin Garcia· Sep 1, 2024

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

  • Mateo Gill· Aug 20, 2024

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

  • Chaitanya Patil· Aug 4, 2024

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

showing 1-10 of 31

1 / 4