get-startedlisted

Use this skill when the user's Coupler.io workspace is NEW or EMPTY — no datasets, no credentials — and they want their data flowing, or when any data request arrives from an account with nothing set up yet. Triggers include: "get started", "set up Coupler", "connect my data", "I just signed up", "pull my QuickBooks/Shopify/HubSpot/ads data", an empty list-datasets result, or a missing credential. Goal: take the user from an empty workspace to their own data rendered in this chat, in one guided pass — including the one-time browser step to authorize their source. Do NOT use for accounts that already have datasets or dataflows (work with their data directly), for platform questions ("what sources do you support?"), or for adding a source to an existing setup (use the create-dataflow skill instead).
coupler-io/skills · ★ 33 · AI & Automation · score 72

Install: claude install-skill coupler-io/skills

# Get Started You are onboarding a brand-new Coupler.io user. They very likely signed up moments ago — often from inside this chat — and their workspace is empty. Your job is to get their FIRST data rendered in this conversation. Do not give a feature tour. Do not list capabilities. Continue the job they already came for. Work through five gates in order; only proceed past a gate when its condition is met. If the workspace already has datasets or dataflows, this skill does not apply: say so in one line ("You're already set up — let's work with your data") and continue with normal analysis. ## Gate 1 — Anchor on their intent The user almost always stated their goal earlier in this chat (e.g. "consolidate my QuickBooks companies", "see my Facebook Ads spend", "get my Shopify orders into a report"). - Re-read the conversation. Extract the SOURCE system and the JOB. - If clear: confirm it in one line and continue. - If no goal is stated: ask exactly ONE question — "Which tool holds the data you want to work with? (QuickBooks, Shopify, HubSpot, Google Ads, a spreadsheet…)". Never open with a menu of Coupler features. - If the client has not yet resolved which workspace to use, settle that in this same message — do not make the user answer two separate setup questions in two turns. Proceed when you know the source and the job. ## Gate 2 — Route: template first, scratch second 1. Call list-templates for the user's source and job. 2. If a good match exists, use the temp