founder-anomaly-watch

Diagnose revenue anomalies using evidence-first decision rules across commerce data and GA4 analytics.

1|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/perceptiv-digital/ecommerce-operator-playbooks --skill founder-anomaly-watch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: founder-anomaly-watch
Source: https://github.com/perceptiv-digital/ecommerce-operator-playbooks/tree/main/skills/founder-anomaly-watch
Command: npx skills add https://github.com/perceptiv-digital/ecommerce-operator-playbooks --skill founder-anomaly-watch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of discerning significant revenue anomalies by providing a systematic approach to evidence collection and decision-making.

Core Features & Use Cases

  • Evidence-first Analysis: Systematically gather evidence across various sources before reaching conclusions.
  • Multi-Dimensional Insight: Examine anomalies across multiple dimensions like commerce data, GA4 analytics, and other sources.
  • Decision Rules: Follow precise rules to categorize anomalies into categories like 'FIX', 'KILL', 'REFRESH', 'WATCH', and 'KEEP'.
  • Use Case: Identify a sharp increase in revenue without knowing the underlying cause. Use the skill to diagnose if the increase is real and to what extent, without attributing to random anomalies.

Quick Start

Execute the 'Revenue Anomaly Watch' play to diagnose any revenue anomaly. Gather evidence from commerce platforms, GA4 analytics, and other sources.

Frequently Asked Questions about founder-anomaly-watch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose revenue anomalies using GA4 and commerce data?

To diagnose revenue anomalies, you systematically gather evidence across GA4 analytics and commerce data before reaching conclusions. This multi-dimensional integration identifies whether revenue shifts are real or random anomalies for operational decision-making.

What is the best way to identify sudden revenue spikes in ecommerce analysis?

The best way to identify sudden revenue spikes in ecommerce analysis is applying evidence-first decision rules across multi-dimensional data. This approach prevents attributing significant revenue shifts to random anomalies by verifying underlying causes.

How do I categorize ecommerce data anomalies for operational decision-making?

You categorize ecommerce data anomalies for operational decision-making by following precise evidence-first decision rules. These rules systematically categorize anomalies into distinct groups: FIX, KILL, REFRESH, WATCH, and KEEP.

Can I use this revenue anomaly detection approach without external data dependencies?

No, robust revenue anomaly detection requires multi-dimensional data integration. You must gather evidence from commerce platforms, GA4 analytics, and other sources to systematically discern significant anomalies and make defensible decisions.

When should I not use systematic evidence-first rules for anomaly detection?

You should avoid using systematic evidence-first rules when you lack multi-dimensional data sources like GA4 analytics and commerce platforms. Without sufficient evidence to cross-reference, anomaly categorization may produce inaccurate conclusions.

Why does my revenue anomaly detection require multiple data sources?

Revenue anomaly detection requires multiple data sources to ensure evidence-first analysis and avoid false conclusions. Integrating commerce data with GA4 analytics provides robust safety and multi-dimensional insight for defensible operational decisions.