gws-keep
by googleworkspacegws-keep is the Google Keep skill in googleworkspace/cli for creating, listing, inspecting, and deleting notes with the gws CLI. Use it for repeatable gws-keep usage in scripted or agent-assisted workflows, with clear command discovery, auth, and deletion constraints.
This skill scores 68/100, which means it is listable but best framed as a moderately useful, narrowly scoped Google Keep CLI skill rather than a fully polished workflow package. For directory users, it offers enough real command structure and resource coverage to justify installation, but the repository leaves some adoption questions unresolved, especially around setup and end-to-end usage.
- Clear CLI trigger and scope: `gws keep <resource> <method> [flags]` with a focused Google Keep objective.
- Concrete API/resource coverage for notes and media, including create, delete, get, list, download, and permissions.
- Operational guidance is present: it tells users to inspect `gws keep --help` before calling methods and notes a prerequisite shared skill for auth and security rules.
- No install command or setup walkthrough in the skill itself, so users may need to infer integration steps from the parent repo.
- Workflow guidance is thin beyond method listings; practical examples and edge-case handling are limited, which may increase guesswork for agents.
Overview of gws-keep skill
What gws-keep does
gws-keep is the Google Keep skill in googleworkspace/cli for managing Keep notes from the gws CLI. It is best for agents or users who need to create, list, inspect, or delete notes without hand-editing API calls.
Who should install it
Use the gws-keep skill if you want a repeatable workflow for Google Keep operations, especially in scripted or agent-assisted environments. It fits users who care about correct CLI discovery, authenticated access, and understanding what the skill can and cannot change before acting.
Why it is different
The skill is command-driven and API-specific, not a generic prompt about Keep. It centers on gws keep <resource> <method> [flags], which makes the gws-keep guide useful when you need a predictable path from intent to command rather than a conversational summary.
How to Use gws-keep skill
Install and load the right context
For gws-keep install, use the repository skill path and then read the prerequisite shared skill first:
npx skills add googleworkspace/cli --skill gws-keep
The skill explicitly depends on ../gws-shared/SKILL.md for auth, global flags, and security rules. If that file is missing in your checkout, run gws generate-skills before using gws-keep.
Start with command discovery
Before choosing a method, inspect the available surface area with:
gws keep --help
That is the fastest way to confirm the exact commands, resource names, and flags available in your local version. The repo also points to these core areas first: SKILL.md, then the shared skill file, then any CLI help output that shows method-level details.
Turn a rough request into a usable prompt
A strong gws-keep usage prompt should name the resource, the action, and the outcome. For example:
- “Create a Google Keep note from this meeting summary and title it with the project name.”
- “List my notes and identify the ones about Q2 launch.”
- “Delete this note only if it is owned by me.”
That level of specificity matters because notes supports different methods with different side effects, and delete is irreversible.
Know the practical constraints
The most important boundaries in gws-keep are permission and resource type. Deleting requires the OWNER role, note listings may be paginated, and attachment download only works when the media MIME type is available. If your task involves attachments, pages, or deletion, mention those constraints up front so the skill can choose the right path.
gws-keep skill FAQ
Is gws-keep only for Google Keep?
Yes. The gws-keep skill is for Google Keep notes within the gws CLI ecosystem, not for general note-taking apps or arbitrary document editing.
Do I need the shared gws skill too?
Usually yes. The skill’s own instructions treat ../gws-shared/SKILL.md as required for authentication, global flags, and security behavior, so gws-keep works best when that shared context is available.
When should I not use gws-keep?
Do not use gws-keep if you only need a one-off natural-language draft with no actual Keep API action, or if you cannot provide permission-safe instructions for operations like delete. It is also a poor fit if you need broad note migration or offline editing that does not map to the CLI methods.
Is it beginner-friendly?
Yes, if you start with gws keep --help and keep the first request simple. Beginners usually succeed faster by asking for one action at a time, such as create or list, before chaining multiple operations.
How to Improve gws-keep skill
Give the skill the exact note intent
For better gws-keep results, specify whether the note is a draft, a task, a meeting note, or an attachment-based note. Include title, body, and any labels or ownership constraints you care about. The more concrete the input, the less the model has to infer about Keep note structure.
Make edge cases explicit
The most common failure modes are vague deletion requests, missing pagination expectations, and unclear attachment requirements. If you need “all notes,” say how you want the result handled across pages. If you need a download, name the attachment and expected format so the gws-keep guide can avoid unsupported MIME-type guesses.
Iterate from safe read-only commands
A good workflow is to start with list or get, verify the target note, then move to create or delete. For gws-keep for Office Documents or other content-heavy notes, first confirm the source text is complete and the target note title is unambiguous. That reduces accidental edits and makes the output easier to trust.