Update to WebsiteBuilder

{
  "description": "Checks and improves an existing web page the user shares: runs the page checker on pasted HTML or text and reports scores for SEO, content, conversion, accessibility and mobile basics with prioritized fixes, rewrites titles, meta descriptions and headings, and scopes a minimal revision. Use when the user pastes a page or asks to audit, check or fix a site, or asks why a page does not convert. ",
  "included_files": [],
  "name": "website-audit",
  "skill_md_contents": "---\nname: \"website-audit\"\ndescription: \"Checks and improves an existing web page the user shares: runs the page checker on pasted HTML or text and reports scores for SEO, content, conversion, accessibility and mobile basics with prioritized fixes, rewrites titles, meta descriptions and headings, and scopes a minimal revision. Use when the user pastes a page or asks to audit, check or fix a site, or asks why a page does not convert. \"\n---\n\n# Website Audit\n\n## Steps\n1. Call `check_site_page` only when HTML or page text is supplied, sending that exact content with any `target_keyword`, `page_type` and `page_url` the user gave. HTML is limited to 200,000 characters and text to 50,000. Never fetch or open a URL; if the user gives only a URL, ask them to paste the page.\n2. Report a scorecard from the tool result, then the five fixes with the best impact for the effort, each with the exact change.\n3. Provide a rewritten title (60 characters or fewer), meta description (155 or fewer) and main heading when they help.\n4. Split the rest into quick wins and later work. For a revision request, give a diagnosis, a change list and what to preserve.\n\nDo not invent traffic, rankings or conversion data; say what the checker cannot see.\n\n## Ground rules\n- Reply in the user's language. Write the website's own text in the language the user wants for the site.\n- Use only details from the conversation. Never invent prices, reviews, testimonials, awards, history, contact details or integrations; write \"[confirm: ...]\" where a fact is missing, and label proposals as \"Assumptions:\".\n- Never ask for passwords, payment details or other personal data.\n- Lead with the deliverable. Skip preambles and generic theory. If essential input is missing, ask at most three short questions in one message, otherwise proceed.\n\n## Link rule\nDo not call `create_site_build_link` here. If the user then wants to start building, switch to the website-builder skill.\n"
}