Fun Gameplay Revenue Weekly Report Automation

What Problem It Solves

This skill targets weekly revenue reporting workflows where data arrives from backend CSV files, Excel email tables, and gameplay planning sheets. It splits the process into four stages: data cleaning, metric calculation, attribution analysis, and compliance validation. Each stage has a narrow responsibility, which helps avoid accidental changes to raw fields, templates, and business definitions.

Core Capabilities and Key Steps

• Data cleaning: Reads backend_template_data.csv, backend_data_table.csv, fun_gameplay_email_table.xlsx, and gameplay_group_planning_timeline.xlsx, filters rows by a user-defined 14-day window, removes blank or invalid rows, and aligns dates across files.
• Metric calculation: Computes weekly and non-activity metrics such as total fun revenue, delayed fun, instant fun, 100% deposit, withdrawal consumption, and total users, then aggregates gameplay deposit structure by wanfa_type.
• Attribution analysis: Outputs a fixed-template analysis covering time trends, gameplay mix, user tiers, activity impact, abnormal events, and overall summary.
• Compliance validation: Checks heading structure, table 1/table 2 layouts, week-over-week formulas, units, the relationship total fun revenue ≈ delayed fun + instant fun, and required warnings when absolute week-over-week change exceeds 50%.

Boundaries and Caveats

It fits stable reporting environments where source tables already contain dt or date columns and the weekly template rarely changes. If field names, sheet names, or gameplay categories change, input conventions must be updated. The skill does not invent free-form business narratives or replace analyst judgment; abnormal fluctuations are flagged for confirmation by operations, data, or product teams.