القائمة
Google Workspace integration with Calendar, Gmail, and Drive for research tasks
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/bobmatnyc/claude-mpm-agents --skill research-google-workspace-integrationيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Production-readiness process checklist covering the code-production pipeline — research, architecture, implementation, tests, critic review, and security gates
Severity-tagged code review rubric (CRITICAL/HIGH/MEDIUM/LOW) used by the code-critic agent to produce APPROVE/WARN/BLOCK verdicts with evidence-backed findings
Audit whether a test suite actually detects regressions (not just whether it runs) by introducing small code mutations and measuring how many your tests catch. Advisory and on-demand — not a blocking CI gate.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | Research Google Workspace Integration |
| description | Google Workspace integration with Calendar, Gmail, and Drive for research tasks |
| version | 1.0.0 |
| category | agent-protocol |
| author | Claude MPM Team |
| license | MIT |
| progressive_disclosure | {"entry_point":{"summary":"Leverage Google Workspace tools for calendar, email, and Drive research","when_to_use":"When research involves calendar, email, or Drive tasks requiring Google Workspace access","quick_start":"Check for mcp__google-workspace-mpm__* tools -> use as supplementary research layer"}} |
| context_limit | 700 |
| tags | ["research","google-workspace","calendar-research","email-research","drive-research","gmail"] |
| requires_tools | [] |
When conducting research that involves the user's calendar, email, or Drive files, you can leverage the google-workspace-mpm MCP server if it is installed and authenticated. This is an OPTIONAL enhancement that supplements your standard research tools.
/oauth setup workspace-mcpCheck for Google Workspace tools by looking for tools with the prefix: mcp__google-workspace-mpm__*
Available google-workspace-mpm tools:
calendar_id (default: "primary"), time_min, time_max (RFC3339 format), max_resultsquery (Gmail search syntax like "from:user@example.com subject:meeting"), max_resultsmessage_idquery (Drive search syntax like "name contains 'requirements'"), max_resultsfile_id| Research Task | Google Workspace Tool | Example Use Case |
|---|---|---|
| Finding meeting times | get_events | "When is the next sprint planning meeting?" |
| Checking availability | get_events + list_calendars | "What's my availability next Tuesday?" |
| Email context gathering | search_gmail_messages | "Find emails about the API redesign" |
| Reading specific email | get_gmail_message_content | "Read the full email from Jane about requirements" |
| Finding requirements docs | search_drive_files | "Find specs for the authentication feature" |
| Reading project documents | get_drive_file_content | "Read the architecture document from Drive" |
When Google Workspace tools are available, enhance your research process:
Standard Research Layer (Always executed):
Google Workspace Layer (Optional - if authenticated):
Synthesis (Comprehensive analysis):
User Request: "Research the requirements for the payment feature"
Standard Approach (Always executed):
|- WebSearch: "payment feature requirements best practices"
|- Grep: Search codebase for payment-related code
|- Read: Review existing payment implementation
'- Synthesize: Compile findings
Enhanced with Google Workspace (if available):
|- search_drive_files: query="payment requirements" OR "payment spec"
|- get_drive_file_content: Read requirements doc from results
|- search_gmail_messages: query="subject:payment feature"
|- get_gmail_message_content: Read relevant email threads
|- Grep: Search codebase for payment-related code
|- Read: Review existing payment implementation
'- Synthesize: Requirements from Drive + email context + code analysis
Result: Complete picture of requirements, stakeholder discussions, and current implementation
User Request: "What was discussed in the architecture review meeting?"
Standard Approach (Always executed):
|- search_drive_files: "architecture review notes"
|- Read: Check for meeting notes in project docs/
'- Synthesize: Available documentation
Enhanced with Google Workspace (if available):
|- get_events: calendar_id="primary", time_min=<last_week>, time_max=<now>
| -> Find "architecture review" event
|- search_drive_files: "architecture review" + meeting date
|- get_drive_file_content: Read meeting notes document
|- search_gmail_messages: "subject:architecture review" + attendees
|- get_gmail_message_content: Read follow-up emails
'- Synthesize: Calendar event + meeting notes + follow-up discussions
Result: Full context including when it happened, what was discussed, and follow-ups
User Request: "Research the decision history for choosing PostgreSQL"
Standard Approach (Always executed):
|- Grep: Search for PostgreSQL references in codebase
|- Read: Review database configuration and migration files
|- WebSearch: "PostgreSQL vs alternatives"
'- Synthesize: Technical analysis
Enhanced with Google Workspace (if available):
|- search_gmail_messages: "subject:database" OR "subject:postgresql"
|- get_gmail_message_content: Read decision-related emails
|- search_drive_files: "database decision" OR "tech stack"
|- get_drive_file_content: Read ADR or decision documents
|- Grep: Search for PostgreSQL references in codebase
|- Read: Review database configuration
'- Synthesize: Decision emails + docs + current implementation
Result: Complete decision history with stakeholder input and rationale
DO:
DON'T:
from:john@example.com - Emails from specific senderto:team@example.com - Emails to specific recipientsubject:requirements - Emails with specific subjecthas:attachment - Emails with attachmentsafter:2024/01/01 before:2024/06/01 - Date rangelabel:important - Emails with specific labelfrom:john@example.com subject:api has:attachmentname contains 'requirements' - Files with name containing textmimeType = 'application/vnd.google-apps.document' - Google Docs onlymodifiedTime > '2024-01-01T00:00:00' - Recently modified files'folder_id' in parents - Files in specific folderBefore using Google Workspace tools, verify availability in your tool set:
# Conceptual pattern (not literal code)
available_tools = [list of available tools]
google_workspace_available = any(tool.startswith('mcp__google-workspace-mpm__') for tool in available_tools)
if google_workspace_available:
# Enhanced research workflow with workspace tools
use_standard_tools()
use_google_workspace_tools() # Supplementary layer
synthesize_all_findings()
else:
# Standard research workflow only
use_standard_tools()
synthesize_findings()
# No error/warning needed - optional enhancement
If Google Workspace tools are not available or not authenticated:
/oauth setup workspace-mcp to enable calendar, email, and Drive access."