Update to Webeyez Analytics

{
  "description": "Generate an executive weekly performance summary of eCommerce conversions, top revenue-impacting issues, UX friction signals, and site health using Webeyez.",
  "included_files": [],
  "name": "weekly-performance-summary",
  "skill_md_contents": "---\nname: weekly-performance-summary\ndescription: Generate an executive weekly performance summary of eCommerce conversions, top revenue-impacting issues, UX friction signals, and site health using Webeyez.\n---\n\n# Weekly Performance Summary\n\nUse this skill when a user asks for a weekly performance report, executive summary, store health check, or prioritization of issues from the past week.\n\n## Workflow\n\n1. **Resolve Target Store**\n   - Call `get_organizations_list` to get the user's `organizationId`.\n   - Call `get_organization_domains` to determine the store `domain` to report on.\n\n2. **Gather Weekly Analytics & Top Friction Points**\n   - Call `start_webeyez_query` asking for a comprehensive summary of the past 7 days covering overall sessions, conversion rates, top revenue-costing issues, checkout drop-offs, JavaScript/API errors, and UX friction signals (rage clicks, dead clicks, slow page loads).\n   - If `start_webeyez_query` returns `status: \"processing\"`, use `check_webeyez_status` with the returned `jobId` until completed.\n\n3. **Fetch Representative Session Recordings**\n   - If specific high-impact sessions are returned in the data, call `get_session_recording_links` for up to 10 session IDs to provide concrete replay examples.\n\n4. **Structure the Weekly Report**\n   - **Key Metrics Overview:** Summarize traffic, conversion trends, and overall digital experience health over the past 7 days.\n   - **Top Revenue-Impacting Issues:** Highlight the highest-cost bugs, failed API requests, or checkout blockers.\n   - **UX & Performance Breakdown:** Note any device, browser, or page-path anomalies (including rage clicks and page load issues).\n   - **Prioritized Action Plan:** Recommend the top 3 fixes the engineering or UX team should tackle first, accompanied by session replay links where available.\n\n"
}