What problem does it solve? Teams waste hackathon hours building features that an existing library, framework, or free-tier API already delivers, and pitch ideas that dozens of past teams already shipped. This Skill provides a fast, evidence-linked verdict before any non-trivial build. ## Core Features & Use Cases - Component Check (5 minutes): Runs a decision ladder — framework capability, installed dependency, maintained library, free-tier API, then build — and outputs a structured verdict with cost, links, and risk. - Winner Archaeology: Searches Devpost and past hackathon editions to identify winning patterns, overdone categories, and open gaps for ideation sessions. - Sponsor Intel: Mines sponsor docs, launches, and devrel posts to surface adoption targets, under-loved APIs, and judge-relevant pitch angles. - Use Case: Before hand-rolling a rich text editor during a hackathon, run the component check to discover a maintained library covers 90% of the need, then wrap it in 20 minutes instead of building for 4 hours. ## Quick Start Ask the agent to run a prior-art check on the component you are about to build, such as "run a prior-art check before I build a PDF generation feature."
