Interact with Google Drive, Gmail, Calendar, and Docs using OAuth authentication. Supports file uploads, folder management, email search, calendar search, and document operations.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongoogle-workspaceExecute the skills CLI command in your project's root directory to begin installation:
Fetches google-workspace from casper-studios/casper-marketplace and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate google-workspace. Access via /google-workspace in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
10
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
10
stars
Interact with Google Drive, Gmail, Calendar, and Docs using OAuth authentication. Supports file uploads, folder management, email search, calendar search, and document operations.
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
OAuth credentials are stored locally after first authentication.
client_secrets.json - From Google Cloud Consolesettings.yaml - PyDrive2 configurationmycreds.txt - Auto-generated OAuth tokensclient_secrets.jsonpython scripts/gdrive_search.py folder "Microsoft"
python scripts/google_drive_upload.py --files *.png --folder "Clients/Acme/Assets"
python scripts/gmail_search.py --domain "microsoft.com" --days 14
python scripts/google_calendar_search.py "Microsoft" --days-back 30
| Scope | Purpose |
|---|---|
drive |
Full Drive access |
spreadsheets |
Sheets access |
documents |
Docs access |
gmail.readonly |
Read emails |
calendar.readonly |
Read calendar |
Free - Google Workspace APIs have generous free quotas.
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)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 accessclient_secrets.json securely, not in reposSymptoms: "Invalid credentials" or "Token has been expired or revoked" error Cause: OAuth refresh token expired or revoked Solution:
mycreds.txt filemycreds.txt will be created automaticallySymptoms: "File not found" error with valid file ID Cause: No access to file, file deleted, or wrong file ID Solution:
Symptoms: "User rate limit exceeded" or "Quota exceeded" error Cause: Too many API requests in 24-hour period Solution:
Symptoms: "settings.yaml not found" or PyDrive2 configuration error Cause: Missing PyDrive2 configuration file Solution:
cp settings.yaml.example settings.yamlclient_secrets.json path is correct in settingsSymptoms: "Invalid client secrets" or OAuth configuration error Cause: Malformed or incorrect OAuth credentials file Solution:
Symptoms: "Insufficient permission" error Cause: OAuth consent missing required scopes Solution:
mycreds.txt to reset OAuth sessionsettings.yaml match script requirementsSkills: google-workspace → video-production Use case: Assemble course videos from Drive folder Flow:
Skills: google-workspace → content-generation Use case: Generate documents from branded templates Flow:
Skills: google-workspace → transcript-search Use case: Find meeting recordings from calendar events Flow:
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
kostja94/marketing-skills
skillhq/flight-search
jwynia/agent-skills
mindrally/skills
github/awesome-copilot
wispbit-ai/skills
Registry listing for google-workspace matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in google-workspace — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added google-workspace from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: google-workspace is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added google-workspace from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: google-workspace is focused, and the summary matches what you get after install.
google-workspace reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for google-workspace matched our evaluation — installs cleanly and behaves as described in the markdown.
google-workspace is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for google-workspace matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 75