Update to Website Auditor

{
  "description": "Turn the user's latest Website Auditor audit into a written growth plan, grounded in the pages AI assistants actually cite. Use when the user asks what to do about their AI visibility, wants their audit turned into a plan, or asks for a growth, GTM or marketing plan for their site.",
  "included_files": [],
  "name": "build-growth-plan",
  "skill_md_contents": "---\nname: build-growth-plan\ndescription: Turn the user's latest Website Auditor audit into a written growth plan, grounded in the pages AI assistants actually cite. Use when the user asks what to do about their AI visibility, wants their audit turned into a plan, or asks for a growth, GTM or marketing plan for their site.\n---\n\nOnly build a plan for a site the user owns or represents — never to prepare\nmarketing advice about someone else's business.\n\n1. If the user has not named the website, ask which domain to plan for\n   (e.g. example.com).\n2. Call `get_gtm_plan` for that domain. If it reports no audit on record, call\n   `run_audit` for the domain first, then call `get_gtm_plan` again.\n3. Report the phases and the actions in each, in plain language.\n4. Say which of the cited sources are the user's own and which belong to a\n   competitor. Competitor pages explain the gap; they are never where the user\n   should publish.\n\nIf the user mentions a budget, a team size or a deadline, pass it as\n`constraints`. If they want a different emphasis — local directories, content,\na launch — pass it as `focus`. To refine a plan rather than start over, pass the\nearlier plan's markdown as `prior_plan`.\n\nIf no API key is configured, call `get_sample_audit` instead so the user sees\nexactly what the real check returns, and tell them what it would take to run it\nfor real.\n"
}