Add skill: amiller/google-service-accounts#501
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis 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. ChangesDocumentation: Add google-service-accounts skill
Possibly related PRs
Suggested labels
Poem
🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment Warning |
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