Crowd9/giveaway-skills / skills/giveaway-winner-structure
giveaway-winner-structure
VerifiedSet giveaway Winner counts, Prize tiers, draw rules, verification, response deadlines, redraws and fulfilment. Use for 'how many Winners', 'one Winner or several', 'runner-up Prizes', 'daily Winners', 'how do I pick the Winner', 'how to announce Winners', 'Winner terms', or 'what if the Winner does not reply'.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.2 KB |
| evals/cases.md | markdown | 5.0 KB |
| evals/evals.json | config | 20.7 KB |
| references/drawing-and-fulfillment.md | markdown | 9.5 KB |
| references/eligibility-and-compliance.md | markdown | 4.0 KB |
| references/evidence-detail.md | markdown | 3.2 KB |
| references/gleam-drawing.md | markdown | 3.7 KB |
| references/house-style.md | markdown | 4.7 KB |
| references/structure-findings.md | markdown | 17.4 KB |
| references/winner-verification.md | markdown | 5.8 KB |
| scripts/style_check.pyexecutable | script | 40.3 KB |
| scripts/terms.py | script | 15.5 KB |
references/winner-verification.md
View on GitHub# Winner verification
Advice from practice. A drawn entry is a Winner only after it passes these checks. Scale the checks to the Prize, ask for the least you need, and delete verification proof after the check. Keep delivery details only for fulfilment and delete them within the stated retention period. Sweepstakes and privacy law differ by jurisdiction. This is not legal advice.
## Why it matters
The typical campaign has 4.2% of Entries marked invalid, and mixes with referral actions run higher. This measures Entry status across campaigns, not failed verification among selected Winners. It cannot determine how many backups a campaign needs.
As operational practice, agree a backup procedure in the terms for a selected Entrant who is ineligible, declines or misses the reply deadline.
[Extracted from 107,109 campaigns and 16,490 businesses. 45% of campaigns had 5% or more invalid. Count source: `analysis/output/invalid_share.json`.]
## Check the entry first
Do these before contacting anyone. They use your own records and take minutes.
- The entry exists in the frozen export with the same identifier the draw used.
- It arrived inside the entry window, in the time zone the terms state.
- Every required action was completed at the time specified by the published terms. Require a follow or shared post to remain in place only when the terms explicitly require that retention. A removed action alone fails this check only when it breaches that requirement. Missing completion evidence calls for investigation before any exclusion.
- One entry per person per the terms. Look for the same person under a second email, a plus-addressed variant, or two handles with the same display name.
- The person is not staff, a partner, their household, or a prior Winner the terms exclude.
- The entered region and age fit the eligibility clause.
## Read the account
Open the social account or email that entered. These signals are reasons to investigate. Their number does not prove fraud. Exclude an Entrant only after confirming a breach of the published eligibility rules, with the reason recorded for that Entrant.
| Signal | What it looks like |
|---|---|
| Fresh account | Created in the weeks before the giveaway, few or no posts, no profile photo or a stock one |
| Handle pattern | A name plus a string of digits, or a run of near-identical handles in your list (`ava_k_2291`, `ava_k_2292`) |
| Giveaway-only feed | Every post is an entry, a repost of a contest, or a tag-a-friend comment |
| Follow ratio | Follows thousands, followed by a handful |
| Name mismatch | Email says one name, the form another, the social handle a third, with no obvious link |
| Shared details | The same postal address, phone or device as another Entrant or a previous Winner |
| Disposable email | A throwaway domain, a mailbox that bounces, or one that never replies |
| Location mismatch | Profile, language and IP point somewhere the terms exclude |
Enthusiastic Entrants who enter many giveaways ("compers") are legitimate. A household of compers can share an address and have new accounts. Keep each eligible member in the draw. A full feed of entries or multiple accounts warrants exclusion only when the records confirm a breach of the published rules.
## Ask for proof in proportion to the Prize
| Prize | Ask for | Do not ask for |
|---|---|---|
| Under about 100 USD | A reply from the account or email that entered, and a delivery address | Any document |
| 100 to 1,000 USD | A reply from the entered email or account, and the name and delivery address needed for fulfilment. Ask for a DM only if that social account was used to enter and is relevant to eligibility under the terms | Government ID |
| Over 1,000 USD, cash, travel | The above, plus one photo ID with the number covered, and proof of residence if the terms restrict region. View it, record that it was checked, delete it | A copy kept on file, card details, a login |
| Skill contests or where local law requires | A signed declaration of eligibility and release, on the form your terms describe | Anything beyond the form |
For an email-only Entrant, use a reply from the entered email and the eligibility checks required by the published terms. Prize value alone does not create a social-account requirement.
Age checks need only a date of birth or an ID with the number covered. In the United States a Prize of 600 USD or more usually means a tax form for the Winner. That is US practice, checked 9 September 2026, and thresholds move. Confirm the threshold and the form with an accountant before asking.
## How to ask
- Use the channel the person entered with. A reply from that account is itself a check.
- Say what you need, why, the deadline, and that the details are deleted after the check. The Winner-communications skill has the wording.
- Say plainly that you will never ask for payment, card details or a password. Scam accounts do, and real Winners are wary.
- Collect documents through a form or a reply the Winner controls, never in a public thread.
- Log each request and reply with a date. The contact log format is in the Winner-communications skill.
## When it fails
- No reply by the deadline, a confirmed eligibility breach, or a decline: follow the published backup procedure under the same audit record. An unresolved signal needs review before any exclusion.
- Record the reason privately. Never publish why someone was disqualified.
- If several drawn entries raise the same concern, pause and review each one against the published rules. Record each confirmed breach privately and retain eligible cluster members. Use the applicable backup or input-correction procedure. If correcting the eligible list requires another draw under the terms, preserve the original record and publish a replacement commitment tied to a future seed before it exists.
- Announce Winners by first name and city, or handle, with consent, only after verification is complete.
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: 194k | 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: 194k | 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: 194k | Updated | Claude CodeCodex | Verified | Install |