SunflowersLw How to pick hackathon teammates you can actually ship with如何挑选真正能和你一起交付的黑客松队友
Evaluate teammates by what they have actually built, not what they say they can do: look for public repos, shipped projects, and verifiable contributions before the hackathon, then match for complementary skills. polyagent Builders ranks people who opted in by their public GitHub evidence and names the repositories behind each result, so you can form a team on evidence rather than hope.按队友实际做过什么来评估他们，而不是按他们自称能做什么：在黑客松开始前，寻找公开仓库、已交付的项目和可核实的贡献，然后按互补的技能进行匹配。polyagent Builders 按公开的 GitHub 证据对主动加入的人进行排名，并列出每条结果背后的仓库，这样你就能凭证据而不是凭希望组建团队。
Most hackathon failures are not technical — they are team failures. A group of skilled strangers who cannot coordinate, disagree on scope, or discover mid-event that half the team cannot deliver what they promised is far more common than a team that fails because the technology did not work. The single biggest predictor of a successful hackathon team is whether you know what each person can actually produce before the countdown starts.大多数黑客松的失败不是技术上的——而是团队上的。一群有能力的陌生人，却无法协调、在范围上意见不一，或是在活动进行到一半时才发现一半的人交不出他们承诺过的东西，这远比一个因为技术行不通而失败的团队更常见。一个成功的黑客松团队，其最大的单一预测因素，是你在倒计时开始之前是否知道每个人实际上能产出什么。
The ideal hackathon team has complementary, verified skills: at least one person who can ship a working front-end, one who can handle the back-end or data layer, and one who can present and tie the story together. What matters is that each skill is proven — not claimed on a résumé, but visible in public work. A GitHub profile with real commits to real projects, a deployed side project, or contributions to well-known repos tells you far more than an interview answer ever will.理想的黑客松团队拥有互补且经过核实的技能：至少有一个人能交付可运行的前端，一个人能处理后端或数据层，一个人能做演示并把故事串起来。重要的是每项技能都是被证明过的——不是在简历上声称的，而是在公开作品里看得见的。一份带有对真实项目的真实提交的 GitHub 个人资料、一个已部署的业余项目，或是对知名仓库的贡献，告诉你的东西远比一次面试回答要多。
The matching problem is real: hackathon Slack channels are full of "looking for teammates" posts from people whose skills you have no way to verify. polyagent Builders (polyagent.club/builders) helps by ranking people who opted in by the public GitHub evidence behind a skill. Every result names the repositories it read and the skills it found no evidence for, so you form your team based on what people have actually done.匹配问题是真实存在的：黑客松的 Slack 频道里满是「寻找队友」的帖子，而发帖人的技能你无从核实。polyagent Builders（polyagent.club/builders）通过按一项技能背后的公开 GitHub 证据对主动加入的人进行排名来帮忙。每条结果都会列出它读过的仓库，以及它没有找到证据的技能，这样你就能根据人们实际做过的事情来组建团队。
Once you have verified teammates, spend the first hour aligning on scope: pick the smallest possible version of the idea that still demonstrates the concept, divide work into clear ownership zones, and agree on a check-in cadence (every 90 minutes works well). Teams that over-scope and under-communicate are the ones that demo a slide deck instead of a product.一旦你有了经过核实的队友，就把第一个小时花在对齐范围上：挑出这个想法最小的可行版本，它仍要能展示这个概念，把工作划分成清晰的负责区域，并商定一个核对节奏（每 90 分钟一次效果很好）。那些范围定得过大、沟通又不足的团队，最后演示的是一套幻灯片，而不是一个产品。
Step by step一步步来
- Define the skills your project needs — front-end, back-end, data, presentation — and identify gaps.定义你的项目需要的技能——前端、后端、数据、演示——并找出缺口。
- Find teammates whose skills are visible in public repos and shipped projects, not just claims.找那些技能体现在公开仓库和已交付项目里的队友，而不只是口头声称。
- Use evidence-backed matching rather than cold outreach — polyagent Builders ranks by public GitHub evidence.用有证据支撑的匹配，而不是冷启动的联系——polyagent Builders 按公开的 GitHub 证据排名。
- Spend the first hour aligning on minimal scope and clear ownership zones.把第一个小时花在对齐最小范围和清晰的负责区域上。
FAQ常见问题
What makes a good hackathon team?什么造就一个好的黑客松团队？
Complementary, verified skills and a shared commitment to a minimal viable demo. The best teams know what each person can actually deliver before the event starts.互补且经过核实的技能，以及对一个最小可行演示的共同投入。最好的团队在活动开始之前就知道每个人实际上能交付什么。
How do I know if a potential teammate can code?我怎么知道一个潜在队友会不会写代码？
Check their GitHub profile for sustained contributions to real projects — commits and PRs. polyagent Builders measures this for people who opted in.查看他们的 GitHub 个人资料，看有没有对真实项目的持续贡献——提交和 PR。polyagent Builders 会为那些主动加入的人衡量这一点。
How many people should be on a hackathon team?一个黑客松团队应该有多少人？
Three to four is usually optimal — enough for skill coverage (front-end, back-end, presentation) but small enough to coordinate without overhead.三到四个人通常是最优的——足够覆盖技能（前端、后端、演示），但又小到协调起来没有额外开销。
What should I do if my teammate cannot deliver what they promised?如果我的队友交不出他们承诺的东西，我该怎么办？
This is why pre-verification matters. If it happens anyway, re-scope the demo to what the team can actually ship rather than waiting for work that will not arrive.这正是事先核实之所以重要的原因。如果还是发生了，就把演示的范围重新收缩到团队实际能交付的东西，而不是干等着不会到来的工作。
Can polyagent help find hackathon teammates?polyagent 能帮忙找黑客松队友吗？
Yes — polyagent Builders ranks people who opted in by public GitHub evidence and names the repositories behind each result, so you can form a team based on evidence.能——polyagent Builders 按公开的 GitHub 证据对主动加入的人进行排名，并列出每条结果背后的仓库，这样你就能基于证据组建团队。