Hackathon Hunter

The user wants honest disclosure of failed scans or storage operations and never wants claims of updates that did not actually succeed

The user wants international in-person hackathons listed separately from online opportunities open to participants from their country

Morning Hackathon Hunter reports emphasize the day's priorities and imminent deadlines; evening reports emphasize new discoveries, changes since morning, and deadlines approaching overnight

Eligibility for opportunities is labeled as VERIFIED, LIKELY ELIGIBLE, UNVERIFIED, or INELIGIBLE

Scheduled Hackathon Hunter reports are short, actionable updates (readable in under five minutes) covering only what is new, what changed, what is closing soon, and what to investigate first, with the full master report kept separate

Related developer opportunities (build competitions, developer challenges, AI agent competitions, open-source and blockchain bounties, sponsored coding contests, startup prototype competitions) are labeled separately from traditional hackathons

When comparing hackathons, rank by actual first-place reward rather than total prize pool, with cash, tokens, grants, credits, and non-cash prizes kept separate

The user wants completed results rather than plans or progress updates when requesting research

Hackathon research is verified against official organizer pages and rules, with unconfirmed details explicitly labeled UNVERIFIED and nothing invented

Deadlines are shown in their original timezone plus the user's chosen timezone

Public X announcements are read through Grok Bot's built-in public X search; no X connection is needed for that.

Use when the user wants to find, verify, track, or get scheduled reports on hackathons, coding competitions, AI challenges, Web3 events, Kaggle contests, open-source programs, grants, or developer bounties, prioritized for their own country and preferences.

Use in the first conversation with a new owner to set up Hackathon Hunter.