Update to SERPHub

{
  "description": "Review the SEO health of one of the user's SERPHub sites and turn it into a short, prioritized list of fixes. Use when the user asks how a site is doing, what to fix first, for an SEO check-up or health review, or for a weekly or monthly SEO summary.",
  "included_files": [],
  "name": "seo-health-review",
  "skill_md_contents": "---\nname: seo-health-review\ndescription: Review the SEO health of one of the user's SERPHub sites and turn it into a short, prioritized list of fixes. Use when the user asks how a site is doing, what to fix first, for an SEO check-up or health review, or for a weekly or monthly SEO summary.\n---\n\nUse this skill when the user wants an overall picture of how one of their sites is doing and what to fix, rather than a single number.\n\n## Inputs\n- The site. If the user did not name it, or named one that `list_sites` does not return, call `list_sites` and ask which site. Never guess a `site_id`.\n\n## Steps\n1. Call `get_site` for the chosen site to see whether an audit is running and which integrations are connected.\n2. Call `get_audit`.\n   - If it reports an audit is running, say so and do not start another. Offer to check `get_audit_progress`.\n   - If there is no completed audit, say so and offer to start one with `run_audit`. Ask first: it crawls the site and replaces audit results older than the account's retention limit.\n3. Call `get_issues` with `severity` set to `high`. If there are fewer than five, call it again for `medium`.\n4. If Search Console is connected, call `get_search_overview` for the trend in clicks, impressions and position. Remember that a lower position is better, and that Search Console data runs about two days behind.\n5. Call `get_uptime`. If monitoring is off or there are no checks, say that rather than reporting the site as up.\n\n## Output\n- One line on overall health: the audit score and the direction of search performance.\n- Up to five fixes, most important first. For each: what is wrong, how many pages it affects, and one example page URL from `get_issues`.\n- Anything urgent outside the audit, such as downtime or a sharp drop in clicks.\n\nThen offer to create SEO tasks for the fixes with `create_task`. Only create tasks the user agrees to, one call per task, with the priority they choose.\n\n## Do not\n- Do not invent issues, page counts, scores or trends. Report only what the tools returned, and say plainly when a tool returned nothing.\n- Do not start an audit or create a task without the user's confirmation.\n- Do not compare the site with competitors unless the user asks, and then only with `get_competitors` data.\n\nIf the user's own instructions conflict with this skill, follow the user.\n"
}