Update to Sitelas

{
  "description": "Use when someone wants their Sitelas website on their own domain (\"put it on mybakery.com\", \"connect my domain\"), wants to check why a domain isn't working, or wants the site ready for search engines and analytics (titles and descriptions, sitemap, Google Analytics or Search Console). Walks through DNS one step at a time and reports exactly what the person needs to change at their registrar.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 107
    }
  ],
  "name": "launch-on-a-domain",
  "skill_md_contents": "---\nname: launch-on-a-domain\ndescription: Use when someone wants their Sitelas website on their own domain (\"put it on mybakery.com\", \"connect my domain\"), wants to check why a domain isn't working, or wants the site ready for search engines and analytics (titles and descriptions, sitemap, Google Analytics or Search Console). Walks through DNS one step at a time and reports exactly what the person needs to change at their registrar.\n---\n\n# Launch on your own domain\n\nA Sitelas site always has a `….sitelas.com` address. The person can point a domain they own at it. You set the domain up on Sitelas and give them the exact DNS records. They add those records at their registrar themselves, because you can't reach their registrar.\n\nIf the person's own instructions conflict with anything below, follow the person.\n\n## Connect a domain\n\n1. Find the site with `list_sites` and confirm which domain they mean: the bare domain (`example.com`), `www.example.com`, or a subdomain (`shop.example.com`).\n2. Call `set_custom_domain`. Relay its `dns_instructions` and `next_step` as they are. For a bare domain that is usually an A record plus a `www` CNAME; for a subdomain, a single CNAME. Don't rewrite the record values.\n3. Tell them the records usually take 5 to 30 minutes to take effect after they're saved, sometimes longer.\n4. When they say the records are in, call `check_custom_domain` with the `domain`.\n   - **Verified and published:** give them the `https://` address.\n   - **Verified but the site was never published:** the domain will show nothing until the site is published. Say so and offer to publish. Call `publish` only after a clear yes.\n   - **Not verified yet:** show the `expected_records` next to what they entered so they can see the mismatch. Usually it's the wrong host, the wrong target, or an old record that needs removing.\n\n`check_custom_domain` without a domain shows what is already attached. Use `remove_custom_domain` only when they ask to remove a domain.\n\nA custom domain is a Pro feature on Sitelas. If a call returns `billing_gate`, pass its message on as it is. Don't quote prices or try to sell a plan, and carry on with anything else they asked for.\n\n## Ready for search engines and sharing\n\n- `update_seo` sets each page's search title, description and share image. Without a page, it sets site-wide defaults: language, business type, address, phone, logo, and verification tags for Google Search Console, Bing, Meta or Pinterest. `get_site` shows the current values first.\n- Every published site serves its sitemap at `/sitemap.xml` on its live address. That is the address to submit in Search Console.\n- `set_tracking_codes` adds the owner's own Google Analytics, Google Tag Manager, Meta Pixel or Plausible ID. Ask them for the ID; never invent one.\n- `review_site` lists problems worth fixing before they share the site widely, such as leftover sample text, missing titles or broken links.\n\nThese settings change the draft. Like any edit, they reach the live site only when the person says to publish.\n"
}