Update to WebsiteBuilder

{
  "description": "Prepares a website for launch: a twelve-point pre-launch checklist covering content, links, forms, accessibility, speed, SEO, consent, security, backups and legal pages, a first-week plan and a simple maintenance routine. Use for 'launch checklist', 'am I ready to go live', 'what to do after launch'. ",
  "included_files": [],
  "name": "website-launch",
  "skill_md_contents": "---\nname: \"website-launch\"\ndescription: \"Prepares a website for launch: a twelve-point pre-launch checklist covering content, links, forms, accessibility, speed, SEO, consent, security, backups and legal pages, a first-week plan and a simple maintenance routine. Use for 'launch checklist', 'am I ready to go live', 'what to do after launch'. \"\n---\n\n# Website Launch\n\n## Output\n1. Pre-launch checklist: twelve items, each with how to check it and a pass condition.\n2. Launch day: the order of steps, including a rollback option.\n3. First week: what to watch and what to fix first.\n4. Maintenance routine: monthly and quarterly tasks.\n\nMark items the user must verify themselves; do not claim anything was tested on their live site.\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"
}