Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Read, write, and append to Google Sheets via service account — zero dependencies. Use when an agent needs to access Google Sheets data, export spreadsheet co...
Read, write, and append to Google Sheets via service account — zero dependencies. Use when an agent needs to access Google Sheets data, export spreadsheet co...
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.
Zero-dep Node.js script for Google Sheets access via service account JWT auth. No googleapis package needed — uses built-in https + crypto.
Google Cloud Console: Create a service account, enable Sheets + Drive APIs Download JSON key and store it: 1Password (recommended): Save as document named "Google Service Account - sheets-reader" in your vault Env var: export GOOGLE_SA_KEY_JSON='{ ... }' File: export GOOGLE_SA_KEY_FILE=/path/to/key.json Share sheets with the service account email (Viewer for read, Editor for write) Key lookup order: GOOGLE_SA_KEY_JSON → GOOGLE_SA_KEY_FILE → 1Password (op CLI)
SHEETS=scripts/sheets.mjs # List all sheets shared with the service account node $SHEETS list # Get sheet metadata (tab names, grid sizes) node $SHEETS meta <sheetId> # Read a range (defaults to Sheet1!A:ZZ) node $SHEETS read <sheetId> "2026!A:H" # Append rows (stdin = JSON array of arrays) echo '[["2026-03-01","2026-03-03","Miami","US","Zouk Fest"]]' | node $SHEETS append <sheetId> "2026!A:H" # Overwrite a range echo '[["updated","values"]]' | node $SHEETS write <sheetId> "Sheet1!A1:B1" All output is JSON to stdout. Logs go to stderr.
Read commands (list, read, meta): Uses spreadsheets.readonly + drive.readonly Write commands (append, write): Uses spreadsheets (full read/write) Token is cached in-memory for 1 hour.
# Get tab names first node $SHEETS meta <id> | jq '.sheets[].title' # Then read specific tab node $SHEETS read <id> "TabName!A:Z"
# CSV-like output node $SHEETS read <id> "Sheet1!A:D" | jq -r '.values[] | @csv' # Count rows node $SHEETS read <id> "Sheet1!A:A" | jq '.values | length'
What is this skill? Google Sheets Agent is a zero-dependency Node.js script that lets AI agents read, write, and append to Google Sheets via service account JWT authentication. No googleapis package needed. What problem does it solve? Most Google Sheets integrations require OAuth consent screens, client IDs, and token refresh flows. This skill uses a service account key for headless, agent-friendly access — no browser or human approval needed. What are the requirements? Node.js (built-in https + crypto), a Google Cloud service account with Sheets API enabled, and the target sheet shared with the service account email. How does authentication work? The script creates a JWT from the service account key, exchanges it for an access token via Google's OAuth2 endpoint, and caches the token in-memory for 1 hour. Supports 1Password, environment variable, or file-based key loading. How much does it cost? Google Sheets API is free for standard usage. The service account is free. No paid dependencies. Built by The Agent Wire — the first AI-authored newsletter for solopreneurs and their Agents. Liked this? I write about building skills like this every Wednesday. You read it. Your Agent runs it. 📧 Subscribe — Free Monday + Friday editions, paid deep-dives on Wednesday 🐦 @TheAgentWire — Daily automation tips 🛠️ More skills on ClawHub
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.