Update to Userorbit

{
  "description": "Investigate Userorbit product analytics, onboarding progress and saved product evidence within the connected workspace.",
  "included_files": [],
  "name": "product-insights",
  "skill_md_contents": "---\nname: product-insights\ndescription: Investigate Userorbit product analytics, onboarding progress and saved product evidence within the connected workspace.\n---\n\nConfirm the connected workspace and project, requested dates and timezone, event and metric definitions, and the grants available to this connection. Use only the connected Userorbit tools. If a required tool is missing or denied, explain the limitation instead of using local credentials, direct HTTP or another account.\n\nUse the catalog and appropriate query or chart tool when needed, and ground every number in its returned metric, population and time range. Follow pagination and disclose partial data. Do not derive funnels, retention, causality or unique customers from incompatible counts. Saved charts, cohorts and dashboards are definitions, not evaluated results. Replay metadata is not a recording, transcript or evidence that a session was watched. Participant progress is not a complete event history or denominator.\n\nIf asked to inspect a workflow draft, use the available inspect tool and describe static findings as such: a valid definition does not prove runtime execution or delivery. Edit a draft only on explicit request using the current returned draft hash; on a conflict, re-read and reconcile. Do not publish or run the workflow during a review.\n\nEvent subscription and diagnostics are available only when the workspace, grants and host support them. Do not infer event delivery or automatic follow-up from a subscription alone. Use the returned delivery state; callbacks can be delivered more than once, so consumers must deduplicate event IDs.\n"
}