Work Connectors

Wire calendar and CRM into Work via MCP and skills.

Skill metadata

Source	Bundled (installed by default)
Path	skills/work/work-connectors
Version	1.0.0
Author	VibeOS
License	MIT
Platforms	linux, macos, windows
Tags	work, work-mode, mcp, calendar, crm, connectors, email
Related skills	work-operate, google-workspace, choose-interaction-surface

Reference: full SKILL.md

к сведению

The following is the complete skill definition that VibeOS loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.

Work Connectors Skill

Practical connectors for Work Mode without cloning ChatGPT’s Plugins directory or shipping Salesforce-in-core. Prefer the MCP catalog + existing skills; keep the agent core narrow.

When to Use

• A Work goal needs calendar (list/create events), Gmail/Workspace, or a CRM-ish board (Linear/Notion) alongside vibeos work.
• Operator asks “how do I connect Gmail / Calendar / CRM to Work?”
• Before reaching for browser_* or computer_use for an API that MCP already covers.

Do not use this to invent a new core tool or in-tree vendor plugin.

Prerequisites

• Work pack enabled (work: in config.yaml). No behavioral VIBEOS_WORK_* env vars.
• MCP CLI available: vibeos mcp ….
• For Google Calendar/Drive/Docs/Sheets: Workspace OAuth ready (skill google-workspace or MCP google-workspace).
• For inbound email → WorkTask: real EMAIL_* keys + vibeos work email-enable (not the stub hermes@gmail.com).

How to Run

1. Pick the thinnest surface (MCP/API → skill → browser → CU).
2. Install/login the MCP or run the Workspace skill setup once.
3. Create or resume a WorkTask (vibeos work create / inbox).
4. Use connector tools inside that Work turn; honor work.approvals for send/pay/delete/share.
5. Package deliverables under the Work folder; do not rebuild the system prompt mid-run.

Quick Reference

Need	Prefer	Avoid
Calendar list/create	vibeos mcp install google-workspace or skill google-workspace	Scraping calendar.google.com with CU first
Gmail send/search (API)	Workspace MCP/skill	Silent SMTP outside work.approvals
Inbound mail → WorkTask	vibeos work email-enable + allowlist	Treating every newsletter as a task
CRM-ish issues/boards	MCP linear / notion from catalog	In-tree Salesforce plugin
Generic SaaS	vibeos mcp catalog + optional MCP manifests	New core tools
Authenticated web only	browser_* after MCP fails	CU for a documented REST API

Catalog pointers (repo): optional-mcps/google-workspace, optional-mcps/google-gmail, optional-mcps/linear, optional-mcps/notion. Setup detail: references/connectors-setup.md.

Procedure

1. Calendar

1. Prefer MCP: vibeos mcp install google-workspace then vibeos mcp login for that server (follow CLI prompts).
2. Or skill path: load google-workspace and use its calendar commands (calendar list / calendar create via the skill bridge).
3. Attach results to the Work ledger (vibeos work ledger …) or package files — not a mid-run system-prompt dump.

2. Email

1. Inbound → Work: replace stub EMAIL_ADDRESS / masked EMAIL_PASSWORD, run vibeos work email-enable, restart gateway, confirm with vibeos work doctor / vibeos work ready.
2. Outbound: keep work.approvals.send=ask; complete parks an ask — never silent send. Use Workspace/Gmail MCP for API sends when that is the configured path; still respect ask-before-send.
3. Rehearse without live IMAP: vibeos work mail-rehearsal (temp home).

3. CRM / boards (not Salesforce-in-core)

1. Install from catalog: e.g. vibeos mcp install linear or notion.
2. Optional boards: skill airtable; Drive files via vibeos mcp install google-drive (or Workspace when Calendar + Drive share OAuth).
3. Login if the server requires OAuth.
4. Drive the Work goal with MCP tools; soft-link Kanban when the job must survive reboot (vibeos work link-kanban / complex create).
5. If the vendor is missing from the catalog, publish a standalone plugin/MCP for ~/.vibeos/plugins/ — do not add a third-party product tree under plugins/ in this repo.

4. Surface ladder (same as Work Operate)

MCP / skill / terminal → web_search / web_extract → browser_* → computer_use (load desktop-operate only when needed).

Pitfalls

• Adding a core tool “because MCP felt slow.”
• Shipping Salesforce (or any vendor SaaS) under in-tree plugins/.
• Auto-sending mail when approvals are ask.
• Using stub hermes@gmail.com / masked *** and calling IMAP “done.”
• Mid-run toolset or system-prompt rebuild to “add calendar.”

Verification

• vibeos mcp list shows the intended server after install/login.
• Calendar or CRM call returns structured data usable in the Work ledger.
• For IMAP: vibeos work doctor has email_imap ok (or preview-ready with a clear stub tip only).
• Outbound still asks when work.approvals.send=ask.
• No new core toolset and no mid-run system-prompt rebuild.