A router brain plus a 52-agent catalog. After this setup, anyone with the Project link and the Polar Analytics connector enabled can run any agent - no code, no deploy.
A plan that supports Projects + remote connectors (Pro, Team, or Enterprise).
Five steps. No code, no deploy, no infrastructure to manage.
Projects are reusable workspaces. The Polar Operator lives as one Project, and anyone you share it with can run any of the 52 agents.
Polar Operator (or your brand's variant).This is the router brain - the universal flow, output discipline, and edge-case handling. Copy the full block below and paste into the Project's Custom Instructions field.
Loading…
The system prompt knows the names; this file holds the per-agent specs (inputs, signals, expected impact). The operator reads it on demand when it picks an agent.
dtc-agents-polar-mcp-prompts.md using the link above.Polar Analytics is an official Claude connector - no custom MCP URL, no extra config. One click and the operator can pull live data.
Open a fresh conversation in your Project and paste any of these. Reply defaults when the operator asks for inputs.
Append a "House style" section to the Custom Instructions ("write in [Brand]'s voice, lean concise, no emojis"). Affects only output, not routing.
If your team always reports on linear or last_click, hard-code it in the system prompt to skip asking each run.
Pilot with one team? Comment out non-relevant agents from the catalog list at the top of the system prompt - the router will only offer that subset.
Once an agent gets used 5+ times a week, give it a dedicated Project - tighter prompt, faster, no router overhead.