google-workspace▌
casper-studios/casper-marketplace · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Interact with Google Drive, Gmail, Calendar, and Docs using OAuth authentication. Supports file uploads, folder management, email search, calendar search, and document operations.
Google Workspace
Overview
Interact with Google Drive, Gmail, Calendar, and Docs using OAuth authentication. Supports file uploads, folder management, email search, calendar search, and document operations.
Quick Decision Tree
What do you need?
│
├── Google Drive
│ ├── Search files/folders → references/drive-search.md
│ │ └── Script: scripts/gdrive_search.py
│ │
│ ├── Upload files → references/drive-upload.md
│ │ └── Script: scripts/google_drive_upload.py
│ │
│ ├── Create folder structure → references/folder-structure.md
│ │ └── Script: scripts/gdrive_folder_structure.py
│ │
│ ├── Create client folder → references/create-folder.md
│ │ └── Script: scripts/create_client_folder.py
│ │
│ └── Search transcripts → references/transcript-search.md
│ └── Script: scripts/gdrive_transcript_search.py
│
├── Gmail
│ └── Search emails → references/gmail-search.md
│ └── Script: scripts/gmail_search.py
│
└── Calendar
└── Search meetings → references/calendar-search.md
└── Script: scripts/google_calendar_search.py
Environment Setup
OAuth credentials are stored locally after first authentication.
Required Files
client_secrets.json- From Google Cloud Consolesettings.yaml- PyDrive2 configurationmycreds.txt- Auto-generated OAuth tokens
First-Time Setup
- Go to Google Cloud Console
- Enable APIs: Drive, Gmail, Calendar, Docs
- Create OAuth 2.0 credentials (Desktop app)
- Download as
client_secrets.json - Run any script - browser opens for OAuth consent
Common Usage
Search Client Folder
python scripts/gdrive_search.py folder "Microsoft"
Upload Files
python scripts/google_drive_upload.py --files *.png --folder "Clients/Acme/Assets"
Search Emails
python scripts/gmail_search.py --domain "microsoft.com" --days 14
Search Calendar
python scripts/google_calendar_search.py "Microsoft" --days-back 30
OAuth Scopes
| Scope | Purpose |
|---|---|
drive |
Full Drive access |
spreadsheets |
Sheets access |
documents |
Docs access |
gmail.readonly |
Read emails |
calendar.readonly |
Read calendar |
Cost
Free - Google Workspace APIs have generous free quotas.
Security Notes
Credential Handling
client_secrets.json- OAuth app credentials (never commit to git)mycreds.txt- User OAuth tokens (never commit to git, add to .gitignore)settings.yaml- PyDrive2 config (can be committed, no secrets)- Tokens auto-refresh; revoke via Google Account settings if compromised
- Never share OAuth credentials between users/machines
Data Privacy
- Access to user's personal Google Drive, Gmail, and Calendar
- Files may contain confidential business information
- Email content is highly sensitive - minimize storage
- Calendar events may contain private meeting details
- Shared Drive access respects original permissions
Access Scopes
- Request minimum required scopes:
drive- Full Drive access (read/write)drive.readonly- Read-only Drive access (preferred when possible)spreadsheets- Google Sheets accessdocuments- Google Docs accessgmail.readonly- Read-only email accesscalendar.readonly- Read-only calendar access
- Review/revoke access: https://myaccount.google.com/permissions
Compliance Considerations
- OAuth Consent: Users explicitly consent to access scopes
- GDPR: Google Workspace data contains EU user PII
- Data Residency: Google Workspace may have data residency requirements
- Shared Drives: Respect organizational sharing policies
- Audit Trail: Google Admin Console tracks API access
- Credential Security: Store
client_secrets.jsonsecurely, not in repos
Troubleshooting
Common Issues
Issue: OAuth token expired
Symptoms: "Invalid credentials" or "Token has been expired or revoked" error Cause: OAuth refresh token expired or revoked Solution:
- Delete
mycreds.txtfile - Re-run any script to trigger fresh OAuth flow
- Complete the browser authorization
- New
mycreds.txtwill be created automatically
Issue: File not found
Symptoms: "File not found" error with valid file ID Cause: No access to file, file deleted, or wrong file ID Solution:
- Verify file ID from the Google Drive URL
- Check file sharing permissions
- Ensure OAuth user has access to the file
- Try accessing file directly in browser first
Issue: Quota exceeded
Symptoms: "User rate limit exceeded" or "Quota exceeded" error Cause: Too many API requests in 24-hour period Solution:
- Wait 24 hours for quota reset
- Create a new Google Cloud project with fresh quota
- Implement exponential backoff in scripts
- Reduce frequency of API calls
Issue: settings.yaml missing
Symptoms: "settings.yaml not found" or PyDrive2 configuration error Cause: Missing PyDrive2 configuration file Solution:
- Copy from template:
cp settings.yaml.example settings.yaml - Ensure
client_secrets.jsonpath is correct in settings - Verify save_credentials_backend is set to "file"
- Check settings.yaml is in the script's working directory
Issue: client_secrets.json invalid
Symptoms: "Invalid client secrets" or OAuth configuration error Cause: Malformed or incorrect OAuth credentials file Solution:
- Re-download from Google Cloud Console
- Ensure "Desktop app" type was selected when creating credentials
- Check JSON format is valid
- Verify redirect URIs are configured for local auth
Issue: Scope access denied
Symptoms: "Insufficient permission" error Cause: OAuth consent missing required scopes Solution:
- Delete
mycreds.txtto reset OAuth session - Re-authenticate and accept all requested scopes
- Verify scopes in
settings.yamlmatch script requirements - Check Google Cloud Console for scope restrictions
Resources
- references/drive-search.md - Search files and folders
- references/drive-upload.md - Upload files to Drive
- references/folder-structure.md - Create folder hierarchies
- references/create-folder.md - Create client folders
- references/transcript-search.md - Search transcript files
- references/gmail-search.md - Search Gmail
- references/calendar-search.md - Search calendar meetings
Integration Patterns
Drive to Video Production
Skills: google-workspace → video-production Use case: Assemble course videos from Drive folder Flow:
- Search Drive for video folder with lesson files
- Download videos via video-production scripts
- Stitch videos with title slides and upload final output
Templates to Content
Skills: google-workspace → content-generation Use case: Generate documents from branded templates Flow:
- Load template from Drive (proposal, report format)
- Generate content via content-generation
- Create new Google Doc with formatted content
Calendar to Transcripts
Skills: google-workspace → transcript-search Use case: Find meeting recordings from calendar events Flow:
- Search calendar for meetings with specific client
- Get meeting dates and titles
- Search transcript-search for matching recordings
How to use google-workspace on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add google-workspace
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches google-workspace from GitHub repository casper-studios/casper-marketplace and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate google-workspace. Access the skill through slash commands (e.g., /google-workspace) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★75 reviews- ★★★★★Nikhil Choi· Dec 28, 2024
Registry listing for google-workspace matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Mateo White· Dec 28, 2024
Useful defaults in google-workspace — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Benjamin Farah· Dec 24, 2024
We added google-workspace from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Dev Abbas· Dec 16, 2024
Keeps context tight: google-workspace is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Mateo Harris· Dec 12, 2024
We added google-workspace from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Sofia Gonzalez· Dec 12, 2024
Solid pick for teams standardizing on skills: google-workspace is focused, and the summary matches what you get after install.
- ★★★★★Mateo Jackson· Dec 8, 2024
google-workspace reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Benjamin Thomas· Dec 8, 2024
Registry listing for google-workspace matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Chaitanya Patil· Dec 4, 2024
google-workspace is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Naina Abbas· Nov 27, 2024
Registry listing for google-workspace matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 75