skills.rest
createtree2017
createtree2017COMMUNITY
Explore all skills by this author →
GitHub

office-google-workspace

Automate Google Drive workflows with permission-safe access and conditional Resend email sending.

Updated Mar 3, 2026
Search Tags:#google workspace#google drive#resend email#shared drive permissions#service account auth#file upload search#forms calendar integration
One-click install
npx skills add https://github.com/createtree2017/createtree-office --skill office-google-workspace
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: office-google-workspace
Source: https://github.com/createtree2017/createtree-office/tree/main/.agents/skills/office-google-workspace
Command: npx skills add https://github.com/createtree2017/createtree-office --skill office-google-workspace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Office teams need a single, permission-safe workflow to access shared Google Drive materials, send sales-related email, and manage Forms/Calendar actions without exposing service account credentials or accidentally emailing ineligible customers.

Core Features & Use Cases

  • Drive materials library workflow: Locate, browse, upload, and search shared drive content using workspace API patterns while handling authorization errors and preserving tenant-safe access boundaries.
  • Shared drive permission correctness: Enforce correct access control per client/tenant, including shared drive handling behaviors such as supportsAllDrives and driveId.
  • Sales email sending with safeguards: Send sales materials via Resend while using guardrails that prevent risky delivery paths (e.g., Railway SMTP blocking) and avoid real sending when required secrets are missing.
  • Forms/Calendar extension compatibility: Extend Calendar/Forms capabilities without breaking the existing Drive authentication/authorization model.
  • Business-rule blocking for outbound materials: Apply block conditions for cases like sales refusal, closure, or missing email so no real emails are sent to ineligible recipients.

Quick Start

Use the office-google-workspace skill to verify the correct route/service/hook flow for Drive upload and search for a specific client, including permission error handling and shared drive behavior.

Frequently Asked Questions about office-google-workspace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Google Drive file upload and search for a specific client tenant?▼

Automate Google Drive file upload and search for a specific client tenant by using service account authentication and applying shared drive parameters like supportsAllDrives and driveId to enforce client permission separation. Handle authorization failures safely without exposing credentials.

Can I send sales email through Google Workspace without exposing service account credentials?▼

Send sales email through Google Workspace securely by using Resend for outbound delivery with safe .env configuration patterns. Guardrails prevent risky delivery paths like Railway SMTP blocking and avoid real sending when required secrets are missing.

How does shared drive permission handling work when accessing tenant-scoped materials?▼

Shared drive permission handling enforces strict client permission separation by applying supportsAllDrives and driveId flags during API traversal. This preserves tenant-safe access boundaries and prevents unauthorized material access across different client scopes.

When should outbound sales materials be blocked from being emailed to recipients?▼

Block outbound sales materials from being emailed when business rule conditions are met, such as sales refusal, closure, or missing email addresses. These explicit blocking rules ensure no real emails are sent to ineligible recipients via Resend.

Does Google Workspace integration support Forms and Calendar actions alongside Drive workflows?▼

Google Workspace integration supports optional Forms and Calendar actions alongside Drive workflows without breaking the existing authentication model. Extend Calendar and Forms capabilities while maintaining service account authorization and tenant-safe access boundaries.

What is the best way to handle authorization failures when browsing shared Google Drive content?▼

Handle authorization failures when browsing shared Google Drive content by applying safe service-account patterns and verifying tenant-scoped access boundaries. Gracefully manage permission errors during shared drive traversal to prevent workflow disruption.

Related Skills

Explore More Software Engineering Skills→
VincentChong123VincentChong123

add-resend

Integrate the Resend email service into the NanoClaw agent framework.

Community
Intermediate
claude-office-skillsclaude-office-skills
368

Pipedrive Automation

Automates Pipedrive CRM workflows including deal management, pipeline tracking, and reporting.

Official
Advanced
pphatdevpphatdev

crm

Coordinate CRM workflows from lead capture to Sales handoff.

Community
Advanced
fishyerfishyer
1

recipe-email-drive-link

Email a Google Drive file link with a custom message.

Community
Intermediate