Create, retrieve, list, delete, and manage permissions for Google Keep notes via CLI.
Works with
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
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongws-keepExecute the skills CLI command in your project's root directory to begin installation:
Fetches gws-keep from googleworkspace/cli and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate gws-keep. Access via /gws-keep in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
23.9K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
23.9K
stars
PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, global flags, and security rules. If missing, rungws generate-skillsto create it.
gws keep <resource> <method> [flags]
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.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' resourceBefore 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.
Make data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
ailabs-393/ai-labs-claude-skills
Useful defaults in gws-keep — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
gws-keep is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in gws-keep — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: gws-keep is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: gws-keep is focused, and the summary matches what you get after install.
gws-keep has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added gws-keep from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
We added gws-keep from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
gws-keep fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
gws-keep fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 31