ericrisco/rsc-harness / skills/google-workspace
google-workspace
VerifiedUse when server-side code reads or writes Gmail, Drive, Calendar, or Sheets with a GCP service account and no human in the OAuth loop: picking the auth mode (app-owned vs domain-wide delegation vs keyless), scoping to least privilege, building the authed Node/Python client, staying under per-user quota, and debugging unauthorized_client / 403 / 429. NOT SMTP providers or deliverability (that is `email-connector`), NOT slot-finding and booking UX (that is `calendar-scheduling`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.6 KB |
| evals/README.md | markdown | 1.1 KB |
| evals/cases.yaml | config | 4.6 KB |
| references/api-recipes.md | markdown | 4.6 KB |
| references/auth-setup.md | markdown | 4.7 KB |
| scripts/verify.shexecutable | script | 4.8 KB |
evals/cases.yaml
View on GitHubskill: google-workspace
should_trigger:
- prompt: "I need a Node cron job to send a daily email through the Gmail API using a service account, no user clicking Allow. How do I authenticate?"
why: "Core use case: server-side, no-human-in-the-loop Gmail send via a service account. Names the auth-mode decision this skill owns."
- prompt: "I'm getting unauthorized_client when my service account tries to impersonate ops@acme.com. What did I miss?"
why: "Non-obvious error-symptom trigger. unauthorized_client maps directly to a missing/incorrect domain-wide-delegation client-ID + scope authorization in the Admin console — the skill's troubleshooting core."
- prompt: "Read values from a Google Sheet in a Python script with a service account and write a couple of rows back."
why: "Sheets API read/write transport via SA — exactly this skill, not the data-modeling concern of spreadsheet-ops."
- prompt: "Necesito automatizar Gmail con una cuenta de servicio sin login del usuario, ¿qué scope y delegación uso?"
why: "Spanish phrasing of the flagship: service-account Gmail automation, scope + delegation question. Must fire across language."
- prompt: "Which OAuth scope do I need to upload a file into a shared drive with the Drive API — is drive.file enough?"
why: "Scope-selection question, the least-privilege table is the skill's job. Non-obvious because the answer hinges on shared-drive support + drive.file semantics."
- prompt: "Walk me through setting up the domain-wide delegation client ID in the Google Admin console for my service account."
why: "Setup step unique to this skill: authorizing the SA's numeric client ID plus exact scopes under Manage Domain Wide Delegation. Non-obvious that it's the client ID, not the email."
- prompt: "My Drive API integration keeps throwing 403 rateLimitExceeded under load — how should I handle it?"
why: "Quota-safe calling (per-user limits + exponential backoff with jitter) is a named section. Error symptom routes here, not to a generic performance skill."
should_not_trigger:
- prompt: "Help me configure SPF, DKIM, and DMARC so our cold outreach stops landing in spam."
route_to: "email-deliverability"
why: "Deliverability / DNS auth records / inbox placement — provider-and-domain concern, explicitly out of scope. This skill is Gmail-the-API, not email reputation."
- prompt: "Build a booking page that finds free 30-minute slots across attendees in different timezones and generates a meeting link."
route_to: "calendar-scheduling"
why: "Scheduling-as-a-product: availability search, timezone UX, booking-link generation. This skill only covers the raw Calendar event CRUD underneath."
- prompt: "Write the formulas and a pivot table to summarize monthly sales by region in this spreadsheet."
route_to: "spreadsheet-ops"
why: "Spreadsheet data modeling and formulas as the deliverable — spreadsheet-ops. This skill is the Sheets API transport, not the analysis."
- prompt: "Extract the line items and totals from these invoice PDFs sitting in a Drive folder."
route_to: "document-processing"
why: "Content extraction / OCR from documents. Drive here is only storage transport; parsing file contents belongs to document-processing."
- prompt: "When a Stripe payment succeeds, create a Drive folder, add a Sheets row, and ping Slack — wire up the whole flow."
route_to: "automation-flows"
why: "Multi-step orchestration spanning several connectors. This skill owns the individual Google calls; chaining across connectors is automation-flows."
capability:
- scenario: "A Node cron must run as a service account impersonating ops@acme.com to (1) send a Gmail summary and (2) append a row to a Sheet. It currently throws 403 insufficient permissions on the send. Diagnose and give working code."
must_include:
- "Identify the auth mode as service-account + domain-wide delegation, setting subject/with_subject to ops@acme.com on the JWT/credentials"
- "Prescribe minimal scopes: gmail.send + spreadsheets (not full drive / mail.google.com), and note the scope IS the blast radius"
- "Call out the Admin console Manage Domain Wide Delegation step: authorize the SA's numeric client ID plus the exact scope list (mismatch -> unauthorized_client; missing scope here -> 403 insufficient permissions)"
- "Show a googleapis Node client build (google.auth.JWT with email/key/scopes/subject, then google.gmail and google.sheets)"
- "Add exponential backoff with jitter on 403 rateLimitExceeded / 429 around the calls"
- "Warn never to commit the SA key JSON; prefer keyless ADC/WIF or a secret manager, unescape the private key newlines from env"
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |