Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Read, create, edit, search, and manage Google Keep notes and lists via CLI.
Read, create, edit, search, and manage Google Keep notes and lists via CLI.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Manage Google Keep notes and lists from the command line using the unofficial gkeepapi.
After installing, the CLI lives in the skill directory. Set up a convenience alias or wrapper: SKILL_DIR="<path-to-this-skill>" # e.g. skills/google-keep alias gkeep="$SKILL_DIR/.venv/bin/python3 $SKILL_DIR/gkeep.py" Or create a global wrapper: cat > ~/.local/bin/gkeep << 'EOF' #!/bin/bash SKILL_DIR="$(dirname "$(readlink -f "$0")")/../.openclaw/workspace/skills/google-keep" exec "$SKILL_DIR/.venv/bin/python3" "$SKILL_DIR/gkeep.py" "$@" EOF chmod +x ~/.local/bin/gkeep
Go to https://accounts.google.com/EmbeddedSetup in your browser Log in with your Google account Click "I agree" on the consent screen (page may spin forever โ ignore it) Open DevTools: F12 โ Application tab โ Cookies โ accounts.google.com Copy the value of the oauth_token cookie Run: gkeep auth <email> <oauth_token>
gkeep auth-master <email> <master_token> Credentials are stored in <skill-dir>/.config/ (chmod 600). The master token has full account access โ treat it like a password. It does not expire (unlike standard OAuth refresh tokens).
gkeep list # Active notes gkeep list --archived # Include archived gkeep list --pinned # Pinned only gkeep list --label "Shopping" # Filter by label gkeep list --json # JSON output gkeep list -v # Show IDs
gkeep search "grocery" gkeep search "todo" --json
gkeep get <note-id> gkeep get "Shopping List" # By title (case-insensitive) gkeep get <id> --json
gkeep create --title "Ideas" --text "Some thoughts" gkeep create --title "Groceries" --list --items "Milk" "Eggs" "Bread" gkeep create --title "Important" --pin --color Red --label "Work"
gkeep edit <id-or-title> --title "New Title" gkeep edit <id-or-title> --text "Updated text" gkeep edit <id-or-title> --pin true gkeep edit <id-or-title> --archive true gkeep edit <id-or-title> --color Blue
gkeep check "Groceries" "milk" # Check off an item gkeep check "Groceries" "milk" --uncheck # Uncheck gkeep check "Groceries" "m" --all # Check all matching gkeep add-item "Groceries" "Butter" "Cheese" # Add items
gkeep delete <id-or-title>
gkeep labels # List all labels gkeep labels --json
gkeep dump # All notes as JSON gkeep dump > backup.json
Valid colors: White, Red, Orange, Yellow, Green, Teal, Blue, DarkBlue, Purple, Pink, Brown, Gray
Uses gkeepapi (1,600+ stars, actively maintained) โ an unofficial reverse-engineered Google Keep client Auth via gpsoauth โ Google Play Services OAuth flow to obtain a master token State is cached locally (.config/state.json) for fast startup after the initial sync Master tokens don't expire, so no re-auth dance Unofficial API โ Google could break compatibility at any time (but gkeepapi has been stable for years)
The master token grants full access to the associated Google account Credentials are stored with 600 permissions in .config/ Never commit .config/ to version control delete moves notes to trash (recoverable) โ it does not permanently delete
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.