submit-to-hackathon

Name: submit-to-hackathon
Author: sendaifun

162stars45forks

How to install submit-to-hackathon?

sendaifun/solana-new/submit-to-hackathon

$npx -y skills add sendaifun/solana-new --skill submit-to-hackathon

Installs into the current project.

Summary

Prepare and optimize a hackathon submission for a Solana project. Use when a user says "submit to hackathon", "prepare my submission", "hackathon entry", "write project description", "demo video", or "help me win the hackathon". Reads all prior phase context if available.

Files · 1

View on GitHub

SKILL.md

1	## Preamble (run first)
2
3	```bash
4	_TEL_TIER=$(cat ~/.superstack/config.json 2>/dev/null \| grep -o '"telemetryTier": "[^"]"' \| head -1 \| sed 's/."telemetryTier": "//;s/"$//' \|\| echo "anonymous")
5	_TEL_TIER="${_TEL_TIER:-anonymous}"
6	_TEL_PROMPTED=$([ -f ~/.superstack/.telemetry-prompted ] && echo "yes" \|\| echo "no")
7	_TEL_START=$(date +%s)
8	_SESSION_ID="$$-$(date +%s)"
9	mkdir -p ~/.superstack
10	echo "TELEMETRY: $_TEL_TIER"
11	echo "TEL_PROMPTED: $_TEL_PROMPTED"
12	if [ "$_TEL_TIER" != "off" ]; then
13	_TEL_EVENT='{"skill":"submit-to-hackathon","phase":"launch","event":"started","ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"}'
14	echo "$_TEL_EVENT" >> ~/.superstack/telemetry.jsonl 2>/dev/null \|\| true
15	_CONVEX_URL=$(cat ~/.superstack/config.json 2>/dev/null \| grep -o '"convexUrl":"[^"]*"' \| head -1 \| cut -d'"' -f4 \|\| echo "")
16	[ -n "$_CONVEX_URL" ] && curl -s -X POST "$_CONVEX_URL/api/mutation" -H "Content-Type: application/json" -d '{"path":"telemetry:track","args":{"skill":"submit-to-hackathon","phase":"launch","status":"success","version":"0.2.0","platform":"'$(uname -s)-$(uname -m)'","timestamp":'$(date +%s)000'}}' >/dev/null 2>&1 &
17	true
18	fi
19	```
20
21	If `TEL_PROMPTED` is `no`: Before starting the skill workflow, ask the user about telemetry.
22	Use AskUserQuestion:
23
24	> Help superstack get better! We track which skills get used and how long they take —
25	> no code, no file paths, no PII. Change anytime in `~/.superstack/config.json`.
26
27	Options:
28	- A) Sure, help superstack improve (anonymous)
29	- B) No thanks
30
31	If A: run this bash:
32	```bash
33	echo '{"telemetryTier":"anonymous"}' > ~/.superstack/config.json
34	_TEL_TIER="anonymous"
35	touch ~/.superstack/.telemetry-prompted
36	```
37
38	If B: run this bash:
39	```bash
40	echo '{"telemetryTier":"off"}' > ~/.superstack/config.json
41	_TEL_TIER="off"
42	touch ~/.superstack/.telemetry-prompted
43	```
44
45	This only happens once. If `TEL_PROMPTED` is `yes`, skip this entirely and proceed to the skill workflow.
46
47	> Wrong skill? See [SKILL_ROUTER.md](../../SKILL_ROUTER.md) for all available skills.
48
49	# Submit to Hackathon
50
51	## Overview
52
53	Prepare a complete, optimized hackathon submission. Write the project description, plan the demo video, and structure the entry to maximize judge appeal. Focused on Solana hackathons (Colosseum, Superteam, ecosystem-specific).
54
55	## Workflow
56
57	1. Check for `.superstack/idea-context.md` and `.superstack/build-context.md`. Use all available context.
58	2. If no context, interview: What did you build? What hackathon? Which track/prize?
59	3. Read [references/hackathon-submission-guide.md](references/hackathon-submission-guide.md) for formatting and requirements.
60	4. Read [references/judging-criteria.md](references/judging-criteria.md) to optimize for what judges look for.
61	5. Draft the project description, optimized for the specific hackathon.
62	6. Create a demo script using [references/demo-video-script.md](references/demo-video-script.md).
63	7. Write a submission HTML artifact with all content ready to copy-paste.
64
65	## Prior Context (Optional — never block on this)
66
67	If `.superstack/idea-context.md` or `.superstack/build-context.md` exist, use them to enrich the submission. If they don't exist, proceed immediately — interview the user about their project. Do NOT redirect to other commands.
68
69	## Non-Negotiables
70
71	- The submission must have a working demo link. No exceptions.
72	- Project description must be scannable — judges read 100+ submissions.
73	- Lead with what the project DOES, not how it works technically.
74	- Include clear setup instructions (judges will try to run it).
75	- Demo video script must be under 3 minutes.
76	- Do not exaggerate traction or features. Judges verify.
77	- Always write a local HTML artifact with the complete submission.
78	- Never fabricate deployment status, traction, or judges-track alignment when context is missing.
79
80	## Resources
81
82	### Writing Tone
83	- [../tone-guide.md](../tone-guide.md) — Default writing tone for project descriptions, demo scripts, and submission copy. Ask the user's tone preference before writing. Hackathon submissions that sound human > AI-generated.
84
85	### references/
86
87	- [references/hackathon-submission-guide.md](references/hackathon-submission-guide.md)
88	- [references/demo-video-script.md](references/demo-video-script.md)
89	- [references/judging-criteria.md](references/judging-criteria.md)
90
91	### Cross-skill data
92	- [skills/data/colosseum/hackathon-winners.md](../../data/colosseum/hackathon-winners.md) — Complete Colosseum winner dataset: 6 grand champions, 40+ track winners, winning patterns, track distribution. Study winners in your track to position your submission.
93
94	## Quick Start
95
96	```bash
97	# This skill creates a submission artifact (HTML) with all content ready to copy-p

People who liked this also viewed

6 picks

Type

submit-to-hackathon

162stars45forks

View on GitHub

How to install submit-to-hackathon?

sendaifun/solana-new/submit-to-hackathon

$npx -y skills add sendaifun/solana-new --skill submit-to-hackathon

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	## Preamble (run first)
2
3	```bash
4	_TEL_TIER=$(cat ~/.superstack/config.json 2>/dev/null \| grep -o '"telemetryTier": "[^"]"' \| head -1 \| sed 's/."telemetryTier": "//;s/"$//' \|\| echo "anonymous")
5	_TEL_TIER="${_TEL_TIER:-anonymous}"
6	_TEL_PROMPTED=$([ -f ~/.superstack/.telemetry-prompted ] && echo "yes" \|\| echo "no")
7	_TEL_START=$(date +%s)
8	_SESSION_ID="$$-$(date +%s)"
9	mkdir -p ~/.superstack
10	echo "TELEMETRY: $_TEL_TIER"
11	echo "TEL_PROMPTED: $_TEL_PROMPTED"
12	if [ "$_TEL_TIER" != "off" ]; then
13	_TEL_EVENT='{"skill":"submit-to-hackathon","phase":"launch","event":"started","ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"}'
14	echo "$_TEL_EVENT" >> ~/.superstack/telemetry.jsonl 2>/dev/null \|\| true
15	_CONVEX_URL=$(cat ~/.superstack/config.json 2>/dev/null \| grep -o '"convexUrl":"[^"]*"' \| head -1 \| cut -d'"' -f4 \|\| echo "")
16	[ -n "$_CONVEX_URL" ] && curl -s -X POST "$_CONVEX_URL/api/mutation" -H "Content-Type: application/json" -d '{"path":"telemetry:track","args":{"skill":"submit-to-hackathon","phase":"launch","status":"success","version":"0.2.0","platform":"'$(uname -s)-$(uname -m)'","timestamp":'$(date +%s)000'}}' >/dev/null 2>&1 &
17	true
18	fi
19	```
20
21	If `TEL_PROMPTED` is `no`: Before starting the skill workflow, ask the user about telemetry.
22	Use AskUserQuestion:
23
24	> Help superstack get better! We track which skills get used and how long they take —
25	> no code, no file paths, no PII. Change anytime in `~/.superstack/config.json`.
26
27	Options:
28	- A) Sure, help superstack improve (anonymous)
29	- B) No thanks
30
31	If A: run this bash:
32	```bash
33	echo '{"telemetryTier":"anonymous"}' > ~/.superstack/config.json
34	_TEL_TIER="anonymous"
35	touch ~/.superstack/.telemetry-prompted
36	```
37
38	If B: run this bash:
39	```bash
40	echo '{"telemetryTier":"off"}' > ~/.superstack/config.json
41	_TEL_TIER="off"
42	touch ~/.superstack/.telemetry-prompted
43	```
44
45	This only happens once. If `TEL_PROMPTED` is `yes`, skip this entirely and proceed to the skill workflow.
46
47	> Wrong skill? See [SKILL_ROUTER.md](../../SKILL_ROUTER.md) for all available skills.
48
49	# Submit to Hackathon
50
51	## Overview
52
53	Prepare a complete, optimized hackathon submission. Write the project description, plan the demo video, and structure the entry to maximize judge appeal. Focused on Solana hackathons (Colosseum, Superteam, ecosystem-specific).
54
55	## Workflow
56
57	1. Check for `.superstack/idea-context.md` and `.superstack/build-context.md`. Use all available context.
58	2. If no context, interview: What did you build? What hackathon? Which track/prize?
59	3. Read [references/hackathon-submission-guide.md](references/hackathon-submission-guide.md) for formatting and requirements.
60	4. Read [references/judging-criteria.md](references/judging-criteria.md) to optimize for what judges look for.
61	5. Draft the project description, optimized for the specific hackathon.
62	6. Create a demo script using [references/demo-video-script.md](references/demo-video-script.md).
63	7. Write a submission HTML artifact with all content ready to copy-paste.
64
65	## Prior Context (Optional — never block on this)
66
67	If `.superstack/idea-context.md` or `.superstack/build-context.md` exist, use them to enrich the submission. If they don't exist, proceed immediately — interview the user about their project. Do NOT redirect to other commands.
68
69	## Non-Negotiables
70
71	- The submission must have a working demo link. No exceptions.
72	- Project description must be scannable — judges read 100+ submissions.
73	- Lead with what the project DOES, not how it works technically.
74	- Include clear setup instructions (judges will try to run it).
75	- Demo video script must be under 3 minutes.
76	- Do not exaggerate traction or features. Judges verify.
77	- Always write a local HTML artifact with the complete submission.
78	- Never fabricate deployment status, traction, or judges-track alignment when context is missing.
79
80	## Resources
81
82	### Writing Tone
83	- [../tone-guide.md](../tone-guide.md) — Default writing tone for project descriptions, demo scripts, and submission copy. Ask the user's tone preference before writing. Hackathon submissions that sound human > AI-generated.
84
85	### references/
86
87	- [references/hackathon-submission-guide.md](references/hackathon-submission-guide.md)
88	- [references/demo-video-script.md](references/demo-video-script.md)
89	- [references/judging-criteria.md](references/judging-criteria.md)
90
91	### Cross-skill data
92	- [skills/data/colosseum/hackathon-winners.md](../../data/colosseum/hackathon-winners.md) — Complete Colosseum winner dataset: 6 grand champions, 40+ track winners, winning patterns, track distribution. Study winners in your track to position your submission.
93
94	## Quick Start
95
96	```bash
97	# This skill creates a submission artifact (HTML) with all content ready to copy-p

People who liked this also viewed

6 picks

Type