skills/integrations/google/google-connect/SKILL.md
Connect Google Workspace and route requests across Gmail, Docs, Sheets, Calendar, Drive, Tasks, and Slides. Use when the user needs Google setup, OAuth validation, or integration troubleshooting.
npx skillsauth add beam-ai-team/beam-next-skills google-connectInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Setup wizard for Google Workspace integration.
Before starting OAuth, writing credentials, changing token files, or routing requests across Google services, show the Google account/workspace, requested scopes, credential/token paths, and expected service access. Require explicit user approval in the current turn before launching OAuth or writing credentials/tokens. Config checks and setup guidance do not require approval.
Guide users through connecting their Google account to Beam Next. One OAuth setup grants access to all 7 Google services: Gmail, Docs, Sheets, Calendar, Drive, Tasks, and Slides.
This skill uses google-master shared library:
| Resource | When to Load |
|----------|--------------|
| google-master/scripts/check_google_config.py | Always first (pre-flight) |
| google-master/scripts/google_auth.py | For authentication |
| google-master/references/setup-guide.md | Detailed setup instructions |
| google-master/references/error-handling.md | On any errors |
Every interaction MUST start with config validation:
uv run python skills/integrations/google/google-master/scripts/check_google_config.py --json
Exit code meanings:
Route based on exit code:
Triggers: "connect google", "setup google", config check returns exit 2
Purpose: Guide user through complete Google Cloud setup.
Display:
--- GOOGLE WORKSPACE SETUP ---------------------------------
This will connect Beam Next to your Google account, enabling:
📧 Gmail - Read, send, manage emails
📄 Docs - Create and edit documents
[STATS] Sheets - Work with spreadsheets
[DATE] Calendar - Manage events and schedules
[DIR] Drive - Upload, download, organize files
[OK] Tasks - Create and manage task lists
📽️ Slides - Create and edit presentations
Time: ~10 minutes (one-time setup)
You'll need: A Google account and browser access
------------------------------------------------------------
Ask: "Ready to set up Google integration?"
Display:
--- STEP 1: CREATE GOOGLE CLOUD PROJECT -------------------
1. Go to: https://console.cloud.google.com/
2. Click the project dropdown (top-left) → "New Project"
3. Enter project name: "Beam Next Integration" (or any name)
4. Click "Create"
5. Wait for project to be created, then select it
------------------------------------------------------------
Ask: "Done creating the project? (yes/no)"
Display:
--- STEP 2: ENABLE GOOGLE APIS ----------------------------
Go to: APIs & Services → Library
Search for and ENABLE each of these APIs:
☐ Gmail API
☐ Google Docs API
☐ Google Sheets API
☐ Google Calendar API
☐ Google Drive API
☐ Google Tasks API
☐ Google Slides API
Click each one → Click "Enable"
------------------------------------------------------------
Ask: "All 7 APIs enabled? (yes/no)"
Display:
--- STEP 3: CONFIGURE OAUTH CONSENT -----------------------
Go to: APIs & Services → OAuth consent screen
1. Select "External" user type → Create
2. Fill in required fields:
• App name: "Beam Next"
• User support email: (your email)
• Developer contact: (your email)
3. Click "Save and Continue"
4. On "Scopes" page → Click "Save and Continue" (skip for now)
5. On "Test users" page:
• Click "Add Users"
• Add YOUR email address
• Click "Save and Continue"
6. Review and go back to dashboard
------------------------------------------------------------
Ask: "OAuth consent screen configured? (yes/no)"
Display:
--- STEP 4: CREATE OAUTH CREDENTIALS ----------------------
Go to: APIs & Services → Credentials
1. Click "Create Credentials" → "OAuth client ID"
2. Application type: "Desktop app"
3. Name: "Beam Next Desktop" (or any name)
4. Click "Create"
5. A popup shows your credentials. Copy these values:
• Client ID (ends in .apps.googleusercontent.com)
• Client Secret
Also note your Project ID from the project dropdown.
------------------------------------------------------------
Ask: "Please paste your Client ID:"
After user provides Client ID, Client Secret, and Project ID:
.env file exists at Beam Next rootGOOGLE_CLIENT_ID=<user-provided-client-id>
GOOGLE_CLIENT_SECRET=<user-provided-client-secret>
GOOGLE_PROJECT_ID=<user-provided-project-id>
Display:
[OK] Credentials saved to .env file
Your Google Cloud credentials are now stored securely.
Next: We'll authenticate with your Google account.
Proceed to: Workflow 3 (Authenticate)
Run before authentication if needed:
pip install google-auth google-auth-oauthlib google-api-python-client
Display:
Installing Google API libraries...
Triggers: Config check returns exit 1, or after Workflow 1 completes
Purpose: Run OAuth flow to get access token.
Display:
--- AUTHENTICATION ----------------------------------------
A browser window will open for Google sign-in.
1. Select your Google account
2. Click "Continue" (you may see "unverified app" warning)
3. Grant access to all requested permissions
4. Close the browser when done
------------------------------------------------------------
uv run python skills/integrations/google/google-master/scripts/google_auth.py --login
If successful:
[OK] Google Integration Complete!
You now have access to:
📧 Gmail → "list emails", "send email"
📄 Docs → "create doc", "read doc"
[STATS] Sheets → "read sheet", "append to sheet"
[DATE] Calendar → "list events", "create event"
[DIR] Drive → "list files", "upload file"
[OK] Tasks → "list tasks", "create task"
📽️ Slides → "create presentation", "add slide"
Try: "list my upcoming calendar events"
If failed, check error and refer to google-master/references/error-handling.md.
Triggers: Config check returns exit 0
Purpose: Show user they're already set up.
Display:
--- GOOGLE ALREADY CONNECTED ------------------------------
[OK] Your Google integration is fully configured!
Available services:
📧 Gmail 📄 Docs [STATS] Sheets
[DATE] Calendar [DIR] Drive [OK] Tasks 📽️ Slides
Commands:
• "list emails" → Gmail inbox
• "create doc [title]" → New Google Doc
• "list calendar events" → Upcoming events
• "list drive files" → Drive contents
• "list tasks" → Task lists
• "create presentation" → New Slides
------------------------------------------------------------
Triggers: "reconnect google", "reauth google", "refresh google token"
Purpose: Get new OAuth token (e.g., after scope changes or token expiry).
uv run python skills/integrations/google/google-master/scripts/google_auth.py --login
This removes the old token and initiates a fresh OAuth flow.
Triggers: "disconnect google", "remove google", "logout google"
Purpose: Remove stored credentials.
uv run python skills/integrations/google/google-master/scripts/google_auth.py --logout
Display:
[OK] Google disconnected
Token removed. Your .env credentials are still saved.
To fully remove, delete these lines from .env:
GOOGLE_CLIENT_ID
GOOGLE_CLIENT_SECRET
GOOGLE_PROJECT_ID
| Error | Solution | |-------|----------| | "Missing credentials" | Run full setup (Workflow 1) | | "Invalid client" | Check Client ID/Secret in .env | | "Access denied" | Add your email as test user in OAuth consent | | "Token expired" | Run reconnect (Workflow 5) | | "API not enabled" | Enable the specific API in Google Cloud Console |
Load google-master/references/error-handling.md for detailed troubleshooting.
| Command | Action |
|---------|--------|
| connect google | Start setup wizard |
| google status | Check connection status |
| reconnect google | Refresh authentication |
| disconnect google | Remove token |
| File | Path | Purpose |
|------|------|---------|
| Credentials | .env | Client ID, Secret, Project ID |
| Access Token | 02-memory/integrations/google-token.json | OAuth token |
Both files are in .gitignore and will not be committed.
Google Connect v1.0 - Setup wizard for Google Workspace integration
tools
Build a Palantir-shape, PDF-native use-case proposal document for a sophisticated enterprise account: research-grounded use cases (each with description, challenge, impact, value), an operating-graph ontology page, a recommended PoC with a week-by-week plan, and a closing page that asks for one decision. Load when a client asks us to 'propose high-impact use cases', requests a use-case presentation/catalog for a function (finance, HR, ops), or when a technical evaluation team will review candidates to pick a PoC. NOT for single-account cold outreach (use prospect-brief), full process diagnostics (use operating-diagnostic), or priced proposals (use proposal-creation).
development
Convert Beam Figma slide designs into high-fidelity, editable HTML presentation decks. Use when Codex is asked to audit Figma slides, extract slide templates, rebuild Beam slides as HTML decks, decide whether Figma imagery should be exported or rebuilt in HTML/CSS, create Beam/Prism-compatible deck templates, or improve fidelity of existing Beam HTML slide rebuilds.
development
Use the Beam AI reusable slide library: individual HTML slide templates extracted from Beam Figma rebuilds, kept separate from deck themes and full deck templates. Load when the user asks for a slide library, specific Beam slide patterns, reusable Figma-inspired slides, Prism slide-library items, or slide-level HTML templates.
development
Use Beam AI deck and report design packs, HTML templates, and curated examples to create sales decks, customer intro decks, RPO decks, and DIN A4 use-case proposal reports. Load when the user asks for Beam-branded presentation templates, Prism-compatible deck templates, Beam report templates, customer intro decks, commercial proposals, or reusable HTML deck/report examples.