shield_lock
金大哥
← 返回 Skill 列表
extension
分类: 数据与分析无需 API Key

神策Wave智能助手（Wave）

Sensors Wave platform router skill. Use when the user asks a broad or ambiguous Wave question and you need to route to tracking implementation (wave-tracking), tracking validation (wave-tracking-validation), analytics (wave-analytics), dashboard building (wave-dashboard-builder), product help (wave-product-help), or Catalog governance (wave-catalog-governance). For MCP access, please refer to: https://sensorswave.cn/docs/ai/mcp/

person作者: u_06f09f2chubenterprise
download下载资源包

Wave

Goal

Route the user to exactly one concrete Wave skill, then read that skill and follow it. Do not execute domain work from this router.

Routing

  • Tracking implementation -> read ../wave-tracking/SKILL.md Use for event design, code/PRD discovery, client/server ownership, identify/reset strategy, Tracking Plan draft/write/publish, Pipeline selection/creation, SDK integration, and preparing tracking context for dashboard handoff. Treat the published Tracking Plan as the required baseline before implementation or other downstream stages.
  • Tracking validation -> read ../wave-tracking-validation/SKILL.md Use only after events are firing and the user wants Tracking Plan validation, rollout acceptance, or missing event/property checks.
  • Analytics -> read ../wave-analytics/SKILL.md Use for event metrics, funnel, retention, user list, user sequence, user profile, and custom SQL.
  • Dashboard building -> read ../wave-dashboard-builder/SKILL.md Use when the user asks to create, update, organize, or polish saved charts, dashboards, overview pages, KPI cards, dashboard layouts, or reusable analysis assets.
  • Product help -> read ../wave-product-help/SKILL.md Use for product usage, setup steps, concepts, FAQ, page entry, permission, and troubleshooting questions.
  • Catalog governance -> read ../wave-catalog-governance/SKILL.md Use for maintaining existing Catalog display names, descriptions, event trigger conditions, platform tags, and example values.

Disambiguation

  • If the request mixes tracking and analytics, finish the tracking design or implementation path first, then hand off to analytics.
  • If the request mixes tracking implementation and validation, do implementation in wave-tracking; only run validation after the user confirms events are already firing and explicitly asks to check.
  • If the request asks to analyze data and then save the result as charts or dashboards, run analytics first for the metric/query shape, then hand off to wave-dashboard-builder.
  • If the request asks to change technical names, data types, delete metadata, or merge duplicates, route to wave-catalog-governance only to explain the current MCP boundary; do not imply those operations are currently available.
  • If the user asks "Wave 怎么用 / 在哪配置 / 为什么看不到", prefer wave-product-help over analytics or tracking.

Stop

After choosing a route, stop using this file and follow the target skill. If no route is clear, ask one concise question: "你现在要做埋点落地、质检、数据分析、看板构建、产品帮助，还是 Catalog 元数据治理？"