Skip to content

Add skill: amiller/google-service-accounts#501

Open
amiller wants to merge 1 commit into
VoltAgent:mainfrom
amiller:add-google-service-accounts
Open

Add skill: amiller/google-service-accounts#501
amiller wants to merge 1 commit into
VoltAgent:mainfrom
amiller:add-google-service-accounts

Conversation

@amiller

@amiller amiller commented Jun 11, 2026

Copy link
Copy Markdown

ClawHub link: https://clawhub.ai/amiller/google-service-accounts

Adds google-service-accounts to Calendar & Scheduling — headless Google Sheets/Docs/Drive/Calendar access via a plain service account: you share the file or calendar with the robot's email instead of standing up an OAuth app. No consent screen, no 7-day testing-mode token expiry, works on a free personal gmail account.

It complements the OAuth-based Google skills already listed (gog, gcal-pro, google-calendar): same APIs, different auth model, with the boundaries documented honestly (can't read unshared private data, can't add attendees — forbiddenForServiceAccounts).

Source repo: https://github.com/amiller/awesome-google-service-accounts

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation
    • Added documentation for Google service accounts integration, describing how to access Google Sheets, Docs, Drive, and Calendar via service-account sharing in the Calendar & Scheduling section.

@coderabbitai

coderabbitai Bot commented Jun 11, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: e54b4822-abd1-4700-a0a3-0153cbbfd2f1

📥 Commits

Reviewing files that changed from the base of the PR and between 0b0c6e2 and df6c1b9.

📒 Files selected for processing (2)
  • README.md
  • categories/calendar-and-scheduling.md

📝 Walkthrough

Walkthrough

This PR adds a single new "google-service-accounts" skill entry to the Calendar & Scheduling section, updating both the main README.md and the dedicated categories/calendar-and-scheduling.md file with the same entry to maintain consistency across documentation.

Changes

Documentation: Add google-service-accounts skill

Layer / File(s) Summary
google-service-accounts skill entry
README.md, categories/calendar-and-scheduling.md
New skill entry for google-service-accounts added to Calendar & Scheduling listings, describing headless access to Google Sheets/Docs/Drive/Calendar via service-account sharing.

Possibly related PRs

Suggested labels

weekly-merge-queue

Poem

🐰 A new skill hops into the list,
Calendar schedules no longer missed,
Service accounts share with grace,
Google's tools in every place! ✨


🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and specifically identifies the main change: adding a new skill entry for google-service-accounts to the repository.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Warning

⚠️ This pull request might be slop. It has been flagged by CodeRabbit slop detection and should be reviewed carefully.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants