hackathon

Name: hackathon
Author: solanabr

93stars58forks

How to install hackathon?

solanabr/solana-ai-kit/hackathon

$npx -y skills add solanabr/solana-ai-kit --skill hackathon

Installs into the current project.

Summary

Prepare a winning hackathon submission. Use when the user says "hackathon submission", "submit to hackathon", "demo script", "demo video", "which track should I enter", "Colosseum", "help me win the hackathon", or asks about hackathon grants and Superteam Earn.

Files · 1

View on GitHub

SKILL.md

1	<!-- Adapted from sendaifun/solana-new (submit-to-hackathon, apply-grant), MIT © 2026 SendAI and Superteam. Telemetry removed. -->
2
3	# Hackathon Submission
4
5	Track choice → scannable description → <3-min demo script → checklist. Optimize for a judge who has 90 seconds, not a reader who has 10 minutes.
6
7	## Context handoff
8
9	At start, read `.claude/context/idea.md` and `.claude/context/build.md` if present — pull the pitch, wedge, and what actually works from them instead of asking again.
10
11	## Workflow
12
13	### 1. Pick the least-crowded track
14
15	Winning a thin track beats placing in a fat one. Per candidate track: estimate entry volume, fit with what's actually built, and judge appetite (sponsor tracks often have the fewest serious entries).
16
17	- Winner patterns + track history: [hackathon-winners.md](../ext/solana-new/skills/data/colosseum/hackathon-winners.md) — every Colosseum grand champion and track winner, with what they built
18	- Live crowdedness check: [ext/colosseum](../ext/colosseum/skills/colosseum-copilot/SKILL.md) — query 5,400+ past submissions for cluster density and gaps (requires `COLOSSEUM_COPILOT_PAT`)
19
20	### 2. Write a scannable description
21
22	Judges read 100+ submissions. Yours gets one skim deciding whether it gets a real read:
23
24	- Tagline: what it does, one sentence, no jargon
25	- First paragraph: problem + who has it
26	- Bold the one thing that's novel
27	- "What works today" list — demo-able claims only, never roadmap dressed as product
28	- Why Solana (one concrete reason: speed, fees, composability with X)
29
30	Full structure (200–500 words, paragraph-by-paragraph): [hackathon-submission-guide.md](../ext/solana-new/skills/launch/submit-to-hackathon/references/hackathon-submission-guide.md). Score the draft against [judging-criteria.md](../ext/solana-new/skills/launch/submit-to-hackathon/references/judging-criteria.md) before submitting.
31
32	### 3. Demo script (<3 minutes)
33
34	\| Time \| Beat \|
35	\|------\|------\|
36	\| 0:00–0:20 \| Problem — one user, one pain, no market-size slides \|
37	\| 0:20–0:40 \| What you built, one sentence + UI first appears \|
38	\| 0:40–2:10 \| The demo — one happy path, real data, on-chain proof (explorer tx) \|
39	\| 2:10–2:40 \| The novel part — the thing competitors don't have \|
40	\| 2:40–3:00 \| Traction/team one-liner + the ask \|
41
42	Shot-by-shot template and recording tips: [demo-video-script.md](../ext/solana-new/skills/launch/submit-to-hackathon/references/demo-video-script.md). Rule: if the demo can fail live, record it.
43
44	### 4. Submission checklist
45
46	- [ ] Track chosen by crowdedness, not vanity
47	- [ ] Tagline passes the "non-crypto friend" test
48	- [ ] Description scannable in 90 seconds (bold claims, short paragraphs)
49	- [ ] Demo video <3 min, real transaction shown
50	- [ ] Repo public, README quickstart actually works from clone
51	- [ ] Deployed link (devnet OK) + program ID listed
52	- [ ] Team and contact info complete
53	- [ ] Pitch deck attached if track requires one — use [pitch-deck](../pitch-deck/SKILL.md)
54
55	## After the hackathon: grants
56
57	Losing the track doesn't mean losing the funding. Same artifacts (description, demo, deck) feed grant applications:
58
59	- Superteam Earn (earn.superteam.fun) — bounties + grants up to ~$10k USDC equivalent, fast cycles, regional Superteams
60	- Solana Foundation grants — milestone-based, public-good angle; reuse the scannable description with an ecosystem-benefit paragraph
61	- Grant-shaped ideas dataset: [superteam-ideas.json](../ext/solana-new/skills/data/ideas/superteam-ideas.json)
62
63	Note: upstream `apply-grant` ships no inert reference files (SKILL.md only — excluded from routing), so grant guidance lives here.

People who liked this also viewed

6 picks

Type

hackathon

93stars58forks

View on GitHub

How to install hackathon?

solanabr/solana-ai-kit/hackathon

$npx -y skills add solanabr/solana-ai-kit --skill hackathon

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	<!-- Adapted from sendaifun/solana-new (submit-to-hackathon, apply-grant), MIT © 2026 SendAI and Superteam. Telemetry removed. -->
2
3	# Hackathon Submission
4
5	Track choice → scannable description → <3-min demo script → checklist. Optimize for a judge who has 90 seconds, not a reader who has 10 minutes.
6
7	## Context handoff
8
9	At start, read `.claude/context/idea.md` and `.claude/context/build.md` if present — pull the pitch, wedge, and what actually works from them instead of asking again.
10
11	## Workflow
12
13	### 1. Pick the least-crowded track
14
15	Winning a thin track beats placing in a fat one. Per candidate track: estimate entry volume, fit with what's actually built, and judge appetite (sponsor tracks often have the fewest serious entries).
16
17	- Winner patterns + track history: [hackathon-winners.md](../ext/solana-new/skills/data/colosseum/hackathon-winners.md) — every Colosseum grand champion and track winner, with what they built
18	- Live crowdedness check: [ext/colosseum](../ext/colosseum/skills/colosseum-copilot/SKILL.md) — query 5,400+ past submissions for cluster density and gaps (requires `COLOSSEUM_COPILOT_PAT`)
19
20	### 2. Write a scannable description
21
22	Judges read 100+ submissions. Yours gets one skim deciding whether it gets a real read:
23
24	- Tagline: what it does, one sentence, no jargon
25	- First paragraph: problem + who has it
26	- Bold the one thing that's novel
27	- "What works today" list — demo-able claims only, never roadmap dressed as product
28	- Why Solana (one concrete reason: speed, fees, composability with X)
29
30	Full structure (200–500 words, paragraph-by-paragraph): [hackathon-submission-guide.md](../ext/solana-new/skills/launch/submit-to-hackathon/references/hackathon-submission-guide.md). Score the draft against [judging-criteria.md](../ext/solana-new/skills/launch/submit-to-hackathon/references/judging-criteria.md) before submitting.
31
32	### 3. Demo script (<3 minutes)
33
34	\| Time \| Beat \|
35	\|------\|------\|
36	\| 0:00–0:20 \| Problem — one user, one pain, no market-size slides \|
37	\| 0:20–0:40 \| What you built, one sentence + UI first appears \|
38	\| 0:40–2:10 \| The demo — one happy path, real data, on-chain proof (explorer tx) \|
39	\| 2:10–2:40 \| The novel part — the thing competitors don't have \|
40	\| 2:40–3:00 \| Traction/team one-liner + the ask \|
41
42	Shot-by-shot template and recording tips: [demo-video-script.md](../ext/solana-new/skills/launch/submit-to-hackathon/references/demo-video-script.md). Rule: if the demo can fail live, record it.
43
44	### 4. Submission checklist
45
46	- [ ] Track chosen by crowdedness, not vanity
47	- [ ] Tagline passes the "non-crypto friend" test
48	- [ ] Description scannable in 90 seconds (bold claims, short paragraphs)
49	- [ ] Demo video <3 min, real transaction shown
50	- [ ] Repo public, README quickstart actually works from clone
51	- [ ] Deployed link (devnet OK) + program ID listed
52	- [ ] Team and contact info complete
53	- [ ] Pitch deck attached if track requires one — use [pitch-deck](../pitch-deck/SKILL.md)
54
55	## After the hackathon: grants
56
57	Losing the track doesn't mean losing the funding. Same artifacts (description, demo, deck) feed grant applications:
58
59	- Superteam Earn (earn.superteam.fun) — bounties + grants up to ~$10k USDC equivalent, fast cycles, regional Superteams
60	- Solana Foundation grants — milestone-based, public-good angle; reuse the scannable description with an ecosystem-benefit paragraph
61	- Grant-shaped ideas dataset: [superteam-ideas.json](../ext/solana-new/skills/data/ideas/superteam-ideas.json)
62
63	Note: upstream `apply-grant` ships no inert reference files (SKILL.md only — excluded from routing), so grant guidance lives here.

People who liked this also viewed

6 picks

Type