submit-to-hackathon

Generates hackathon submission descriptions, demo video scripts, and judge-optimized entry content for Solana projects.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/RavitejaKarra24/dotfiles --skill submit-to-hackathon-ravitejakarra24
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: submit-to-hackathon
Source: https://github.com/RavitejaKarra24/dotfiles/tree/main/agents/.agents/skills/submit-to-hackathon
Command: npx skills add https://github.com/RavitejaKarra24/dotfiles --skill submit-to-hackathon-ravitejakarra24

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Preparing a competitive hackathon submission requires writing a scannable project description, planning a demo video, and aligning content with judging criteria, which is time-consuming and easy to get wrong under deadline pressure. ## Core Features & Use Cases - Submission Drafting: Writes a structured project description (problem, solution, why Solana, technical highlights, roadmap) optimized for judges who review 100+ entries. - Demo Video Planning: Produces a 3-minute demo video script with a proven structure (hook, solution, live demo, technical highlight, wrap-up). - Judge Optimization: Applies judging criteria from Colosseum, ETHGlobal, and Superteam patterns, plus a dataset of past Colosseum winners, to position the entry and pick the least competitive fitting track. - Use Case: After building a Solana project for a Colosseum hackathon, ask the skill to prepare the submission and receive a complete HTML artifact with description, demo script, and copy-paste-ready content. ## Quick Start Ask the assistant to prepare your Colosseum hackathon submission with a project description and a 3-minute demo video script.

Frequently Asked Questions about submit-to-hackathon

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a Solana hackathon project description?

Structure it in five short paragraphs: the problem, the solution, why Solana is required, technical highlights, and what's next. Lead with what the project does rather than how it works, and keep it scannable since judges review over 100 submissions.

How long should a hackathon demo video be?

Keep the demo video under 3 minutes. Use a structure of a 20-second problem hook, 20-second solution overview, 100-second live product demo, 30-second technical highlight, and a 10-second wrap-up with a call to action.

Which hackathon track should I submit my project to?

Pick the least competitive track that genuinely fits your project rather than the most prestigious one. DeFi tracks are typically overcrowded, while infrastructure and tooling tracks tend to have fewer entries.

Does my hackathon demo need to be on Solana mainnet?

No, devnet is acceptable for hackathon submissions and makes it easier for judges to test without spending real SOL. The demo must be live and accessible, clearly labeled as devnet, with test credentials or a pre-funded wallet.

What do hackathon judges look for in submissions?

Judges weight functionality at about 30%, innovation 25%, technical execution 20%, potential impact 15%, and presentation 10%. A working demo is the single biggest differentiator since judges spend only 2-5 minutes per initial review.