investigate-signup-spike

Investigate signup spikes with time-window analysis and baseline comparisons.

1|1|Updated Mar 25, 2026

Search Tags:#onboarding #investigation #reporting #signup #anomaly-detection #bot-detection

Ready to run

npx skills add https://github.com/theultimateshyam/claude-skills --skill investigate-signup-spike

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: investigate-signup-spike
Source: https://github.com/theultimateshyam/claude-skills/tree/main/investigate-signup-spike
Command: npx skills add https://github.com/theultimateshyam/claude-skills --skill investigate-signup-spike

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Abnormal signup surges and suspected bot/abuse waves are identified, analyzed, and reported with actionable insights.

Core Features & Use Cases

End-to-end investigation workflow covering data collection, demographics, referral signals, bot likelihood, and multi-account checks.
Produces two deliverables: a detailed report and a concise one-page summary.
Provides structured hypotheses and recommended actions to mitigate abuse and inform product decisions.

Quick Start

Investigate the signup spike for the specified time window and generate both the detailed report and the one-page summary.

Frequently Asked Questions about investigate-signup-spike

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

FAQPage Schema

How do I investigate abnormal signup spikes and detect bot activity?▼

To investigate abnormal signup spikes, you collect phase-based data on volume, demographics, onboarding status, referrals, and multi-account signals to identify suspected bot waves. This process compares current activity against historical baselines using time-window analysis to surface actionable insights and structured hypotheses.

What is the best way to analyze onboarding surges across web and mobile platforms?▼

Analyzing onboarding surges requires comparing current signup volume against baseline metrics across specified time windows. This approach works across web and mobile platforms, evaluating referral signals and multi-account checks to determine whether the surge is organic or a suspected abuse wave.

How do I report suspected multi-account signals during a referral-driven burst?▼

To report suspected multi-account signals during referral-driven bursts, the investigation generates a detailed report and a concise one-page summary. These deliverables outline structured findings regarding multi-account activity and provide recommended actions to mitigate abuse.

Does this anomaly detection workflow differentiate between organic onboarding surges and bot waves?▼

Yes, this anomaly detection workflow differentiates traffic sources by analyzing demographic data, referral signals, and onboarding status. By comparing current signup metrics against historical baselines, it distinguishes legitimate referral-driven bursts from suspected bot waves and multi-account abuse.

What deliverables should I expect from a signup anomaly investigation?▼

A signup anomaly investigation produces two deliverables: a detailed report and a concise one-page summary. Both outputs contain structured findings, hypotheses regarding bot or multi-account activity, and actionable recommendations to inform product decisions and mitigate abuse.