{"id":51671,"plugin_id":"plugin_asdk_app_6ac688dabe3c81918acfeb3596564046","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:47:05.573Z","digest":"ab44eee30bc8beaa2bfdc9dc3f2204d32203caaa4845610cad9eb0ab4b3e2ee0","against":null,"payload":{"description":"Scan a public website with Website Launch Check when the user wants to review launch readiness, technical SEO, social preview metadata, selected security headers, robots.txt, sitemap.xml, or basic technical setup.","included_files":[],"name":"website-launch-check","skill_md_contents":"---\nname: website-launch-check\ndescription: Scan a public website with Website Launch Check when the user wants to review launch readiness, technical SEO, social preview metadata, selected security headers, robots.txt, sitemap.xml, or basic technical setup.\n---\n\nUse the Website Launch Check MCP tool `scan_website` for the public website the user asks to check.\n\nWhen presenting results:\n- Lead with the overall score and grade.\n- Prioritize failed checks before warnings.\n- Group recommendations under technical SEO, social previews, security headers, and technical readiness when useful.\n- Explain concrete fixes, but do not claim the scan proves a website is secure, accessible, legally compliant, or guaranteed to rank.\n- Treat the scan as a read-only observation of the public response at scan time.\n- If the scan fails because the URL is private, unresolved, too large, unsupported, or blocked by the target, explain the returned error and do not invent results.\n- Do not ask for credentials, API keys, deployment tokens, passwords, or private URLs.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}