/hackathon-finder

name: hackathon-finder
description: Find hackathons tailored to your tech profile and location by searching Devpost, Luma, Partiful, MLH, and Eventbrite. Use this skill when a user asks "find me a hackathon", "are there any hackathons near me", "what hackathons are coming up", "I want to compete in a hackathon", "find hackathons I could win", "upcoming hackathons in [city]", "online hackathons for [skill/tech]", or any request to discover hackathon opportunities.

Hackathon Finder

Build a tech profile from everything known about you, then search Devpost, Luma, Partiful, MLH, and Eventbrite for upcoming hackathons — local or online — that match your stack and give you the best shot at winning.

Pre-flight Check (REQUIRED)

Before making any TinyFish call, always run BOTH checks:

**1. CLI installed?**

which tinyfish && tinyfish --version || echo "TINYFISH_CLI_NOT_INSTALLED"

If not installed, stop and tell the user: > Install the TinyFish CLI: `npm install -g @tiny-fish/cli`

**2. Authenticated?**

tinyfish auth status

If not authenticated, stop and tell the user: > You need a TinyFish API key. Get one at: https://agent.tinyfish.ai/api-keys > > Then authenticate: > ``` > tinyfish auth login > ```

Do NOT proceed until both checks pass.

---

Step 1 — Build the user's tech profile

Before searching for anything, build a picture of who you're helping. Draw from everything available in the current conversation and session context:

• Languages and frameworks mentioned or used (e.g. React, Python, Rust)
• Projects described or worked on
• Areas of interest expressed (e.g. AI/ML, Web3, hardware, design)
• Skill level signals (beginner, experienced, specialist)
• Any past hackathon experience mentioned

Summarize this as a brief internal profile:

Tech profile:
- Primary languages: {e.g. Python, TypeScript}
- Frameworks / tools: {e.g. React, FastAPI, LangChain}
- Interest areas: {e.g. AI, developer tools, consumer apps}
- Skill level: {beginner / intermediate / experienced}
- Past hackathons: {yes/no, any wins?}

If very little is known, ask one quick question: > "What do you usually build with? (e.g. languages, frameworks, or areas like AI, web, mobile)"

---

Step 2 — Ask for location and format preference

Ask the user two things before searching:

Two quick questions:

1. **Where are you based?** (city and country — e.g. "Singapore", "London, UK", "Austin, TX")
   Or if you prefer online-only hackathons, just say "online".

2. **What are you optimizing for?**
   - 🏆 Best chance of winning (match your stack to the theme)
   - 🌍 Biggest / most prestigious (large prize pools, well-known sponsors)
   - 🤝 Best for networking / meeting people
   - 🧪 Most interesting theme (something you'd genuinely enjoy building)

Wait for the user's response before proceeding.

---

Step 3 — Parallel hackathon search

Fire all agents simultaneously based on the user's location and tech profile.

# Agent 1 — Devpost (largest hackathon aggregator)
tinyfish agent run \
  --url "https://devpost.com/hackathons?challenge_type=online&status=upcoming" \
  "You are on Devpost's upcoming hackathons page.
   Find hackathons relevant to these technologies: {TECH_KEYWORDS}.
   For each relevant hackathon extract:
   - name
   - theme or focus area
   - prize pool (total or top prize)
   - registration deadline
   - hackathon dates
   - online or in-person (and location if in-person)
   - direct URL
   - sponsor companies (if shown)
   STRICT RULES:
   - Do NOT click into any hackathon page
   - Read only what is visible in the listing cards
   - Only include hackathons with future dates
   - Maximum 10 listings then stop
   Return JSON array: [{name, theme, prize_pool, deadline, dates, format, location, url, sponsors: []}]" \
  --sync > /tmp/hf_devpost.json &

# Agent 2 — Devpost (in-person / local, if user specified a city)
tinyfish agent run \
  --url "https://devpost.com/hackathons?challenge_type=in-person&status=upcoming&search={LOCATION_ENCODED}" \
  "You are on Devpost's upcoming in-person hackathons page filtered to {LOCATION}.
   Find hackathons in or near {LOCATION}.
   For each extract:
   - name
   - theme or focus area
   - prize pool
   - registration deadline
   - hackathon dates
   - exact location (city, venue if shown)
   - direct URL
   - sponsor companies
   STRICT RULES:
   - Do NOT click into any hackathon page
   - Maximum 8 listings then stop
   - Only include hackathons with future dates
   Return JSON array: [{name, theme, prize_pool, deadline, dates, location, url, sponsors: []}]" \
  --sync > /tmp/hf_devpost_local.json &

# Agent 3 — MLH (Major League Hacking)
tinyfish agent run \
  --url "https://mlh.io/seasons/2026/events" \
  "You are on the MLH (Major League Hacking) events page for the current season.
   Find upcoming hackathons, especially any in or near {LOCATION} or online.
   For each event extract:
   - name
   - date
   - location (city or online)
   - direct URL
   - any theme or focus if shown
   STRICT RULES:
   - Do NOT click any event
   - Read only the visible event cards
   - Maximum 10 events then stop
   - Only future events
   Return JSON array: [{name, date, location, url, theme}]" \
  --sync > /tmp/hf_mlh.json &

# Agent 4 — Luma
tinyfish agent run \
  --url "https://lu.ma/discover?q=hackathon+{LOCATION_ENCODED}" \
  "You are on Luma event discovery searching for hackathons near {LOCATION}.
   Find upcoming hackathon events.
   For each event extract:
   - name
   - date and time
   - location (in-person address or online)
   - host / organizer
   - short description or theme
   - direct URL
   STRICT RULES:
   - Do NOT click any event
   - Read only what is visible in the event cards
   - Maximum 8 events then stop
   - Only future events
   - If no hackathons found, return {found: false}
   Return JSON array: [{name, date, location, host, description, url}]" \
  --sync > /tmp/hf_luma.json &

# Agent