store-pulse

From README

Store Pulse Daily-driver ecommerce snapshot. Every invocation leads with a fresh inline answer (24h summary, KPI row, funnel). Saving a dashboard artifact and scheduling a recurring report are explicit, optional actions — never prerequisites. One dashboard + one schedule per domain. Different domains can each have their own, side by side. Call metadata: on every noibu call this skill drives, pass skill: "store-pulse" and a short skillStep (see the querying-noibu-data skill). Default flow Runs on every invocation ("how's my store doing", "check on flyinmiata.com", a bare /store-pulse). No existence check gates this and no listartifacts call here — always fresh, and never mentions an existing saved dashboard even if one exists (see "Save as artifact" for the one place existence is checked). Resolve the domain — use it without asking if already clear from context; otherwise noibulistdomains (one result → use it; multiple with none named → AskUserQuestion).