by Crowd9
Skills for running better giveaways: prize, entry methods, timing, winner structure, promotion, provably fair draws, winner messages and ideas. Platform-neutral, supported by Gleam.
# Add to your Claude Code skills
git clone https://github.com/Crowd9/giveaway-skillsGuides for using ai agents skills like giveaway-skills.
See how giveaway-skills compares with popular alternatives.
giveaway-skills is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by Crowd9. Skills for running better giveaways: prize, entry methods, timing, winner structure, promotion, provably fair draws, winner messages and ideas. Platform-neutral, supported by Gleam. It has 2 GitHub stars.
giveaway-skills's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/Crowd9/giveaway-skills" and add it to your Claude Code skills directory (see the Installation section above).
giveaway-skills is primarily written in Python. It is open-source under Crowd9 on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh giveaway-skills against similar tools.
No comments yet. Be the first to share your thoughts!
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
See comparison
Plan, run and draw a giveaway your audience will trust, with an AI assistant that has read 167,068 real campaigns. Ten skills cover the whole job, from the idea to the draw to the review afterwards. No code to write. Install once, then ask in plain English.
Works with Claude Code, OpenAI Codex, Cursor and any assistant that reads SKILL.md files under the Agent Skills specification. Maintained by Gleam, and the advice fits any giveaway platform.
Benchmarks come from 116,499 campaigns run by 17,633 businesses, in six size bands from 100 Entrants up. Every figure carries its sample size, and every finding describes what businesses chose, never what caused participation. The detail is in Evidence Behind the Advice.
Claude Code, as a plugin:
/plugin marketplace add Crowd9/giveaway-skills
/plugin install giveaway-skills
OpenAI Codex, Cursor and anything else that reads .agents/skills, with the skills CLI:
npx skills add Crowd9/giveaway-skills
Or copy a skill folder into the place your assistant loads skills from: .claude/skills/ for Claude Code, .agents/skills/ for Codex (Codex skills docs). Then ask: How long should my giveaway run?
If you keep the marketingskills product context file at .agents/product-marketing.md, every skill reads it first and skips the questions it answers.
Run them in order for a whole campaign, or call one when you are stuck. Each hands off to the next.
| Skill | Ask it | You get |
|---|---|---|
| Idea Generator | "Giveaway ideas for our 10k milestone" | Three concepts with hook, mechanic and prize direction, and the one to run |
| Prize Picker | "Is a PS5 a good prize for us?" | A prize that attracts buyers, two alternatives, and a budget with shipping and duties |
| Entry Method Planner | "How should people enter?" | A weighted entry list that builds the asset you want and stops before entrants drop off |
| Timing and Duration | "How long should it run?" | A run length, a start date and a dated timeline from terms to delivery |
| Winner Structure | "One winner or ten?" | Winner count, tiers, redraw rules and a terms draft for your country |
| Promotion Plan | "How do I promote it with no ad budget?" | A channel schedule with the posts and emails written, plus partner briefs and retargeting audiences |
| Random Draw | "Pick 3 winners from this CSV" | Winners from a public randomness beacon with an audit record anyone can check |
| Winner Communications | "The winner hasn't replied" | Every message after the draw, from notification through the welcome series |
| Results Review | "How did our giveaway do?" | Where your campaign ranks against campaigns its own size, and three changes for next time |
| Gleam Campaign Setup | "Walk me through the settings in Gleam" | A checklist in tab order with the documentation page beside every setting |
Three giveaway concepts that fit your business, your date and your goal, then the one to run.
"We're a candle brand about to hit 10k followers, budget $300, ideas?"
A prize that pulls the people you want, and the budget worked out before you commit.
"Is a PS5 a good prize for our accounting software?"
The actions entrants take, weighted so the giveaway builds the list, following or community you will use.
"We want email subscribers, we have Instagram and Klaviyo."
A run length and a start date that fit the launch, the promotion plan and the shipping window.
"Shoe launches 14 October, want hype and emails."
How many winners, what tiers, and a process that holds up when a winner disappears or disputes the result.
"Budget $1,500 of our own $60 meal-prep sets, we want reviews."
A schedule that fills the whole run, with the copy written.
"Runs 1 to 14 October, one partner post, no paid budget."
Winners nobody can dispute, from a script that needs no account and no dependencies.
"Pick 3 winners from this CSV, weight by entries, exclude staff."
Every message after the draw, in send order, in your voice.
Winner notification with a deadline, and the line that says you will never ask for payment or a login
Verification request that asks only what the terms allow, and address collection with a privacy note
Shipping and delivery updates, the public announcement, and the thank-you to everyone who did not win
The welcome series for entrants who opted in, and the list hygiene pass that retires addresses that never engage
Replies for the winner who stalls, the winner who disputes, and the entrant who says the draw was rigged
For a store, the non-winner code: one single-use code per person, 7 to 14 day expiry, a larger code for referrers, tracked as the campaign's revenue line
"Winner hasn't replied in five days."
giveaway-winner-communications
Your finished campaign read against 116,499 others in its own s