explainx.ainewsletter3.4k
Productivity

gws-keep▌

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-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.

how to use gws-keep

How to use gws-keep 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-keep
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-keep

The skills CLI fetches gws-keep 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-keep

Reload or restart Cursor to activate gws-keep. Access the skill through slash commands (e.g., /gws-keep) 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.

Additional Resources

›View source code on GitHub›Skills CLI documentation›Learn more about Cursor›What are agent skills?

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.7★★★★★31 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