Runs the connector setup phase of Tandem onboarding (Step 5). Guides through Gmail, Calendar, Notion, Monday.com, Outlook connectors. Reads state from ~/Tandem/.onboarding-state.md. Do NOT invoke directly — only called from /begin onboarding sequence via Skill tool.
From tandemnpx claudepluginhub binatrixai/tandem-marketplace --plugin tandemThis skill is limited to using the following tools:
evals/evals.jsonExecutes pre-written implementation plans: critically reviews, follows bite-sized steps exactly, runs verifications, tracks progress with checkpoints, uses git worktrees, stops on blockers.
Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
At startup, read ~/Tandem/.onboarding-state.md to recover session context:
language — use for all output throughout this phaserole — for role-aware connector pre-check (begin-connectors) or workspace creation (begin-workspace)use_cases — for priority use cases contexttools_selected — for which connectors to set up (begin-connectors only)Pre-check — detect already-active connectors:
Before guiding setup, test which connectors are already active in this session.
For each tool selected in Step 3d (read from tools_selected in onboarding state):
This prevents asking users to set up connectors that the service operator already pre-configured.
Based on the tools from onboarding state, guide the user through connecting each service (only those NOT already active).
For each selected tool that needs setup, present:
AskUserQuestion:
Per-service guidance:
After each connector, test the connection if possible. Then:
AskUserQuestion:
IMPORTANT — Connector Timing: Newly connected MCP connectors may NOT be available in the current session. They typically require a session restart (close and reopen Cowork) to become active. Inform the user:
"The connectors you just set up are being configured. Some may need a session restart to become fully active. We'll test them in a moment — if any aren't ready yet, don't worry, they'll work in your next session." / "Подключения настроены. Некоторые могут потребовать перезапуска сессии для активации. Мы проверим их — если что-то не заработает сразу, не волнуйтесь, в следующей сессии всё будет работать."
For the onboarding call: The service operator should pre-configure connectors BEFORE the call whenever possible. This ensures they're active during the session and the "wow moment" in Step 7 works.
After the connector setup loop is complete (user selects "Done with connectors — continue"):
Append to ~/Tandem/.onboarding-state.md:
connectors_configured: true
connectors_status: [comma-separated — e.g., "Gmail: active, Monday.com: active, Calendar: pending-restart"]
Then invoke the workspace creation phase:
Skill(skill="tandem:begin-workspace")