Crowd9/giveaway-skills / skills/giveaway-timing-and-duration
giveaway-timing-and-duration
VerifiedSet giveaway duration, launch date and wrap-up timeline. Use for 'how long should my giveaway run', 'when should I launch', 'best day to start', 'best time for an Instagram giveaway', 'Black Friday giveaway timing', 'should it run over Christmas', 'giveaway calendar', or 'evergreen giveaway'. Match dates to promotion, holidays, draw and fulfilment.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.5 KB |
| evals/cases.md | markdown | 6.9 KB |
| evals/evals.json | config | 26.4 KB |
| references/calendar-by-region.md | markdown | 4.5 KB |
| references/evidence-detail.md | markdown | 3.2 KB |
| references/holiday-benchmarks.md | markdown | 32.1 KB |
| references/house-style.md | markdown | 4.7 KB |
| references/timeline-template.md | markdown | 3.8 KB |
| references/timing-findings.md | markdown | 37.7 KB |
| scripts/style_check.pyexecutable | script | 40.3 KB |
references/timeline-template.md
View on GitHub# Timeline template
Advice. Fill in the dates and delete what does not apply.
## Two-week campaign
| When | What |
|---|---|
| T minus 10 days | Terms written (eligibility, dates with time zone, Prize value, how Winners are chosen and contacted, redraw rule). Prize secured or ordered. Partner briefs sent. |
| T minus 5 days | Entry page built and tested on a phone. Assets for every channel ready. Email announcement drafted. |
| T minus 2 days | Instrument before launch. Every link to the entry page carries UTM parameters (source, medium, campaign) so each channel can be told apart afterwards. Conversion tracking is live on the entry page and fires on a completed entry. The campaign timezone is written down and used on every date in the terms and the posts. Without this, the results review has nothing to attribute and every channel looks the same., email authentication (SPF, DKIM, DMARC) passing and the entry sync to the email provider tested with an admin entry |
| T minus 1 day | Teaser post. Team knows who answers questions and who draws. |
| Launch day (a weekday) | Push one: announce on every channel within the same two hours. Email the list. Pin the post. Schedule the launch post and, later, the last-call post for the hours the audience is on each channel, taken from the channel's own analytics. |
| One day in days 4 to 6 | Push two: show the Prize in use, share early Entrant count if it helps, remind of the sharing action. One post per channel and one email within the same two hours. |
| Days 10 to 13 | Supporting partner posts without an extra email, in the quiet middle. Use the partner's fixed posting day instead when needed. |
| One day in the final 48 hours | Push three, last call: "Closing soon" on every channel, with one email within the same two hours. Check the close time reads correctly in the audience's time zone. Supporting story countdowns can continue until close. |
| Close plus 1 day | Draw. Verify the winning entry. Contact Winners with a 72-hour reply deadline. |
| Close plus 4 days | Redraw unclaimed Prizes. Announce Winners publicly. Thank Entrants and offer a small consolation (a code, a content link) if the objective was leads. |
| Close plus 7 to 21 days | Ship or deliver. Ask Winners for a photo or review if the terms allowed it. |
## Adjusting the length
- One week: a single push, a small list, one channel. Shorter campaigns recorded fewer Entries per Entrant in the duration comparison.
- Three to four weeks: a content series, two or more partners, or a product launch with staged reveals.
- Longer than six weeks: only with daily repeatable actions, fresh content each week, and a reason the audience keeps coming back. Otherwise the middle goes quiet.
## Seasonal notes
- December is the busiest month for launches in the data, holding 10.4% of starts against 8.3% for an even month. December campaigns get 30.9% to enter against 25.6% to 26.9% for every other month, on a run of 10 days against 14 or 15 (12,068 campaigns, 3,958 businesses). More competition, more attention, slower shipping. Close before the shipping cut-off if the Prize must arrive for a holiday. [Extracted from `analysis/output/prize_timing_cuts.json` (`by_start_month`), the start month table in `holiday-benchmarks.md` and `timing-findings.md`.]
- If low advertising cost determines the launch date, use your own seasonal channel-cost history. Campaign start counts do not measure advertising prices.
- Align with the audience's calendar. A back-to-school Prize in the week schools return, a gardening Prize in early spring for that hemisphere.
- Avoid closing on a public holiday or a weekend when nobody on the team will draw and respond. The Conversion Rate itself does not drop on a weekend or public-holiday close once run length is held fixed, so team availability is the reason to plan around it.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |