giveaway-results-reviewlisted

Review a finished giveaway from its export or its numbers against benchmarks from 116,499 real campaigns, with a full report in the order of the reporting tabs (overview, traffic, entry methods, viral, audience, outcomes) from a Gleam Actions export or another platform's export: Entrants for campaigns your size, how many entered, actions per Entrant, invalid entries, which entry actions pulled their weight, and what to change next time. Use when the user asks 'how did my giveaway do', 'was this a good result', 'review my campaign results', 'why was conversion low', 'which actions worked', 'giveaway post-mortem', 'debrief', or pastes campaign stats, a reporting screenshot or an actions export. Platform-neutral. For planning the next one see giveaway-timing-and-duration and giveaway-entry-method-planner.
Crowd9/giveaway-skills · ★ 2 · Code & Development · score 78

Install: claude install-skill Crowd9/giveaway-skills

# Giveaway Results Review Read a finished campaign's numbers against what 116,499 campaigns of the same size did, name the two or three things that mattered, and turn them into changes for the next run. ## Before starting If `.agents/product-marketing.md` exists in the project (or `.claude/product-marketing.md`), read it first for the business and its objective. Ask only for what it lacks. When the message carries a JSON summary from Gleam's Reporting tab (fields such as `contestants`, `impressions`, `hasRepeatableAction`, an actions table and a previous-campaigns table), load `references/gleam-reporting.md` before anything else. It says what each field means, that `days` is the planned run and the campaign may still be live, that previous campaigns under 100 Entrants do not count, and how to rank from the tables when the scripts cannot run. ## What to ask first  Answer first, ask second. A message that names a task is a request for the work, so do the work. "Walk me through it", "give me ideas", "how long should it run" and a three-word request are all asking you to deliver. Build the best version the message supports, then put the questions that would change it at the end, each one saying what it would change. A reader who wanted an interview would have asked for one. Missing facts narrow the answer, they never cancel it. When you do not know the budget, give the shape of the recommendation and the typical figures for a campaign like theirs,