Update to Dalton

{
  "description": "Get a new Dalton user oriented right after they connect. Confirm the connection, show the accounts they can open, and suggest a first question about their store's analytics or A/B tests. Use when the user has just installed Dalton, asks what Dalton can do, or asks how to start.",
  "included_files": [],
  "name": "get-started",
  "skill_md_contents": "---\nname: get-started\ndescription: Get a new Dalton user oriented right after they connect. Confirm the connection, show the accounts they can open, and suggest a first question about their store's analytics or A/B tests. Use when the user has just installed Dalton, asks what Dalton can do, or asks how to start.\n---\n\n# Get started with Dalton\n\nDalton is A/B testing for online stores. Through this plugin the user can read their store's analytics and test results and have you draft new A/B tests. You act as them and see only the accounts they're a member of.\n\n## Steps\n\n1. Call `whoami`. It confirms the connection and lists the accounts (customers) the user can open, each with its `customer_id`. Every account-scoped tool takes that id.\n   - One account: use it without asking.\n   - Several: name them and ask which store to look at.\n   - None: tell the user their login isn't a member of any Dalton account yet, and to ask whoever manages their store's Dalton account to add them.\n2. Give the user a short overview of what they can ask:\n   - **Analytics:** conversion rate, revenue, the funnel and its weakest step, traffic by channel or device, and which pages win or lose visitors.\n   - **Experiments:** how each A/B test is doing, the winners now deployed, and what Dalton has learned across tests.\n   - **Drafting:** a new A/B test on a page, or a copy of an existing one on other pages.\n3. Offer one concrete first question, for example \"How did my store convert over the last 30 days?\", and run it if they agree (`get_site_totals`).\n\n## Keep in mind\n\n- Results stay hidden until every variant has enough traffic and the test's planned window has run. Say \"too early to call\", not \"no result\".\n- You never launch, pause or deploy a test. Drafts are launched by the user in the Dalton app, or with the Launch button in the experiment view.\n- Before proposing a new test, read `get_learnings` so you don't suggest what was already tried.\n- If an account shows no rulesets or experiments while the user is sure it has them, the account may not be on Dalton's current platform yet. Offer to pass that on with `suggestion_box`.\n"
}