bounty-hunter
Find, evaluate, and submit online bounties and hackathons for prize money. Use when user mentions "bounties", "hackathon", "earn money", "Superteam Earn", "prize money", "submissions", "freelance bounties", or asks to find paid opportunities. Covers discovery, eligibility filtering, content drafting, and submission workflows.
Best use case
bounty-hunter is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Find, evaluate, and submit online bounties and hackathons for prize money. Use when user mentions "bounties", "hackathon", "earn money", "Superteam Earn", "prize money", "submissions", "freelance bounties", or asks to find paid opportunities. Covers discovery, eligibility filtering, content drafting, and submission workflows.
Teams using bounty-hunter should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/bounty-hunter/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How bounty-hunter Compares
| Feature / Agent | bounty-hunter | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Find, evaluate, and submit online bounties and hackathons for prize money. Use when user mentions "bounties", "hackathon", "earn money", "Superteam Earn", "prize money", "submissions", "freelance bounties", or asks to find paid opportunities. Covers discovery, eligibility filtering, content drafting, and submission workflows.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Bounty Hunter Systematically find and submit bounties, hackathons, and paid opportunities to generate revenue. Optimized for solo operators and AI-assisted teams. ## Workflow ### Step 1: Discovery Scan these platforms for active bounties: **Primary sources:** - **Superteam Earn** (earn.superteam.fun) — Solana ecosystem bounties, content, projects - **Colosseum** (colosseum.com) — Solana hackathons, often $50K-$500K prize pools - **GitHub Issues** — Bounty-tagged issues on trending repos - **Gitcoin** (gitcoin.co) — Web3 grants and bounties **Secondary sources:** - **ProductHunt** Launch competitions - **DevPost** (devpost.com) — Hackathon aggregator - **HackerOne** / **Bugcrowd** — Security bounties (if applicable) - **Replit Bounties** — Quick coding tasks **How to scan Superteam Earn:** 1. Visit earn.superteam.fun 2. Filter by: Content, Development, Design (match your strengths) 3. Sort by deadline (closest first) or prize (highest first) 4. Note: Some bounties are region-locked — check eligibility carefully ### Step 2: Evaluate (Kill Bad Ones Fast) For each bounty, score on these 5 criteria: | Criteria | Weight | Question | |----------|--------|----------| | Prize-to-effort ratio | 30% | $/hour if you win? Target >$100/hr | | Win probability | 25% | How many submissions? How niche? | | Skill match | 20% | Can you deliver quality with current capabilities? | | Eligibility | 15% | Region restrictions? KYC? Team size? | | Strategic value | 10% | Portfolio piece? Networking? Learning? | **Auto-reject if:** - Region-locked to a country you're not in - Requires video/camera of a specific person (can't fake identity) - Prize < $50 (not worth the time) - Deadline < 24 hours AND requires significant build - Submission count > 100 AND prize < $500 **Auto-prioritize if:** - Prize > $1,000 AND < 20 submissions - Content/writing bounty (fast turnaround) - Matches something you've already built - No region lock, global eligibility ### Step 3: Research the Bounty Before writing a single word: 1. **Read the full brief** — not just the title. Every detail matters. 2. **Study the sponsor** — visit their site, understand their product, read their docs 3. **Check winning submissions** from past bounties by same sponsor — learn their taste 4. **Identify the REAL ask** — often different from the surface-level description 5. **Note evaluation criteria** — if stated, optimize for these specifically ### Step 4: Draft Submission **For content bounties (threads, articles, videos):** 1. Research the topic deeply — 30+ minutes minimum 2. Find unique angles nobody else will cover 3. Include real data, real examples, real insights 4. Format for the platform (X threads ≠ blog posts ≠ video scripts) 5. Cite sources — judges notice this **For development bounties:** 1. Build a working prototype (not just mockups) 2. Deploy publicly — judges click links 3. README with clear setup instructions 4. Demo video or screenshots showing it works 5. Highlight what makes your submission unique **For design bounties:** 1. Show process, not just final output 2. Include mobile AND desktop 3. Use the sponsor's actual brand assets 4. Explain design decisions ### Step 5: Quality Check Before Submission - [ ] Does this EXACTLY match the brief requirements? - [ ] Would you be proud to show this to a potential employer? - [ ] Is it better than what 80% of submissions will look like? - [ ] Are all links working? All images loading? - [ ] Proofread for typos, grammar, formatting? - [ ] Does it show genuine understanding of the sponsor's product? ### Step 6: Submit and Track 1. Submit before deadline (aim for 24+ hours early — judges see early submissions) 2. Log in tracking file: ``` | Bounty | Platform | Prize | Submitted | Deadline | Status | Outcome | ``` 3. Set reminder to check results 4. If you win, document what worked for future pattern matching 5. If you lose, study winning submission — what did they do differently? ## Bounty Types and Strategies ### Content Bounties (Fastest ROI) **X/Twitter Threads:** - 8-12 tweets, strong hook, real data - Include relevant images/charts - Tag the sponsor and relevant people - Post at optimal times (9-11am EST for crypto) **Articles/Blog Posts:** - 1,500-3,000 words - Clear structure: hook, problem, solution, examples, conclusion - Original research or unique angle - SEO-friendly if published on your own blog **Video:** - 2-5 minutes for explainers - Clean audio is more important than visuals - Show, don't just tell — screen recordings, demos - Add captions ### Development Bounties (Highest Prizes) - Always deploy to a public URL - Include a 60-second demo video/GIF - Write clear README - Handle edge cases — judges will try to break it - Open source your code (unless brief says otherwise) ### Design Bounties - Figma files, not just screenshots - Show responsive breakpoints - Include interaction states (hover, active, disabled) - Use the project's actual branding ## Pipeline Management Maintain a bounty pipeline at all times: ``` SCOUTING: [bounties being evaluated] ACTIVE: [bounties being worked on — max 3 at a time] SUBMITTED: [awaiting results] WON: [track earnings] LOST: [track for learning] ``` **Rule: Never have an empty SCOUTING queue.** Always have 5+ bounties being evaluated. **Rule: Max 3 active bounties.** Quality > quantity. A half-assed submission is worse than no submission. ## Earnings Tracking Track cumulative earnings to measure ROI: ``` Total Submitted: X Total Won: Y Win Rate: Y/X % Total Earned: $Z Average $/submission: $Z/X Average $/win: $Z/Y Hours invested: H Effective hourly rate: $Z/H ``` Target: >$50/hour effective rate. If below this, you're picking wrong bounties.
Related Skills
API Fuzzing for Bug Bounty
This skill should be used when the user asks to "test API security", "fuzz APIs", "find IDOR vulnerabilities", "test REST API", "test GraphQL", "API penetration testing", "bug bounty API testing", or needs guidance on API security assessment techniques.
api-fuzzing-bug-bounty
This skill should be used when the user asks to "test API security", "fuzz APIs", "find IDOR vulnerabilities", "test REST API", "test GraphQL", "API penetration testing", "bug b...
seo-snippet-hunter
Formats content to be eligible for featured snippets and SERP features. Creates snippet-optimized content blocks based on best practices. Use PROACTIVELY for question-based content.
oss-hunter
Automatically hunt for high-impact OSS contribution opportunities in trending repositories.
Hunter Automation
Automate Hunter.io email intelligence -- search domains for email addresses, find specific contacts, verify email deliverability, manage leads, and monitor account usage -- using natural language through the Composio MCP integration.
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
chakra-ui
Builds accessible React applications with Chakra UI v3 components, tokens, and recipes. Use when creating styled component systems, theming, or accessible form controls.
cfn-intervention-system
Human intervention detection and orchestration for CFN Loop. Use when automated processes need human oversight, when escalation is required, or when managing intervention workflows and approval gates.
cermont.backend.prisma-v7
Expert guidance for Prisma ORM v7 (7.0+). Use when working with Prisma schema files, migrations, Prisma Client queries, database setup. Covers ESM modules, driver adapters, prisma.config.ts, Rust-free client.
cerebras-api
Cerebras API integration for building AI-powered applications with ultra-fast LLM inference. Use when working with Cerebras's Chat Completions API, Python SDK (cerebras_cloud_sdk), TypeScript SDK (@cerebras/cerebras_cloud_sdk), tool use/function calling, structured outputs with JSON schemas, reasoning models with thinking tokens, streaming responses, or any Cerebras API integration task. Triggers on mentions of Cerebras, Cerebras Inference, Llama on Cerebras, Qwen on Cerebras, GLM, or fast LLM inference needs.
ceo-advisor
Executive leadership guidance for strategic decision-making, organizational development, and stakeholder management. Includes strategy analyzer, financial scenario modeling, board governance frameworks, and investor relations playbooks. Use when planning strategy, preparing board presentations, managing investors, developing organizational culture, making executive decisions, or when user mentions CEO, strategic planning, board meetings, investor updates, organizational leadership, or executive strategy.
cdr-platform-automation
Automate Cdr Platform tasks via Rube MCP (Composio). Always search tools first for current schemas.