gws CLI: Google Keep
Manage Google Keep notes: create, list, get, delete, permissions, attachments
- What
- Manage Google Keep notes: create, list, get, delete, permissions, attachments
- Cost
- Free
- Needs
- the `gws` binary on the PATH; a Google account with browser OAuth (`gws auth login`) or a service account; install the googleworkspace-cli-gws-shared skill first
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the Google Keep v1 API reference for the `gws` CLI: notes (create, get, list, delete, permissions) and media (attachment download), with the `gws schema` discovery workflow for building correct flags. Read the sibling `googleworkspace-cli-gws-shared` fiche first (auth, global flags, security rules). Distinct from the lot 31 googleworkspace workflow fiches (raw API reference, not a persona workflow). By @googleworkspace, listed here with credit to its creator. Honest caveats: deleting a note is immediate and irreversible (OWNER role required) — prefer `--dry-run` and the shared confirm-before-executing rule; browser OAuth is free, service accounts need a Google Cloud project. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
gws CLI: Google Keep is a Google Keep v1 reference for gws, covering notes: create, get, list, delete, permissions, media downloads, plus the gws schema workflow for flags. Read gws-shared first for auth, flags and security: a raw API reference, not a persona workflow. Deleting a note is immediate and irreversible, OWNER required, prefer dry-run and confirm-before-executing.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit a3768d0Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: the `gws` binary on the PATH; a Google account with browser OAuth (`gws auth login`) or a service account; install the googleworkspace-cli-gws-shared skill first Install "gws CLI: Google Keep" for me. Give my agent the Google Keep API reference for the gws CLI — manage notes, permissions and attachments Repository: https://raw.githubusercontent.com/googleworkspace/cli/a3768d0e82ad83cca2da97724e46bea4ff0e6dbd/skills/gws-keep/SKILL.md Pinned version: install the code at commit a3768d0e82ad83cca2da97724e46bea4ff0e6dbd exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the googleworkspace-cli-gws-keep skill from the repository into a temporary folder 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "googleworkspace-cli-gws-keep". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. `gws auth login`). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- a3768d0 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026 · Observed during the install test: registry.npmjs.org
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.