WeakBot is a BattleBots matchup-intelligence prototype that turns public fight evidence into an explainable map of a combat robot's most vulnerable components. It pairs risk scores with source context, recommendations, and a pre-fight Pit Plan so teams can decide what to reinforce before a match.
- Interactive robot and opponent-type selectors
- Component-level vulnerability map with synchronized risk cards
- Overall risk and confidence scores for each matchup
- Evidence drawer linking findings to public team and BattleBots sources
- Generated Pit Plan checklist ordered by risk priority
- Downloadable plain-text vulnerability report
- Responsive English-language dashboard UI
WeakBot is designed to use Bright Data as the collection layer for public web evidence. A production pipeline would discover relevant robot profiles, match records, fight videos, transcripts, and team repair reports; normalize and deduplicate the observations; then pass structured failure events into the scoring layer used by the dashboard.
The current repository does not make live Bright Data API calls. Its source counts, incidents, confidence values, and risk results are curated demo data that demonstrate the intended product flow.
Public robot profiles, fight pages, videos, and team reports
|
v
Bright Data search and scraping APIs
|
v
Normalize sources and deduplicate failure events
|
v
Score component risk and attach evidence context
|
v
Risk map, evidence trace, report, and Pit Plan
Bright Data credentials should be kept in server-side environment variables. The browser should request an analysis from a server route rather than calling Bright Data directly.
- Next.js and React with TypeScript
- vinext and Vite for the Cloudflare-compatible build
- Lucide React icons
- Custom responsive CSS
Requires Node.js >=22.13.0.
npm install
npm run devOpen the local URL printed by the development server. To verify a production build:
npm run buildWeakBot is a hackathon prototype, not an engineering diagnosis tool. The next implementation step is a server-side analysis endpoint that connects Bright Data, converts collected pages and transcripts into a consistent event schema, and returns the same risk-report shape currently rendered from demo data.
