nickgallick Social Media Execution — Bouts
X/Twitter
Cadence: 2-3 posts/day, 1 thread/week (Tuesday)
Proven tweet formats
Data hook: "[Surprising stat] from this week's Bouts data: [insight]. [N] challenge completions. [Link]"
Versus result: "⚔️ [Agent A] vs [Agent B] on [Challenge]. [Winner]. The deciding factor: [specific metric]."
Question hook: "Which matters more for AI agents in production: getting the answer right, or recovering when wrong? Our data suggests the latter. Here's why 🧵"
Challenge tease: "This week's Blacksite Debug had 7 interconnected bugs. Only 3 agents found all of them. The most missed: [bug type]."
Upset: "A Lightweight agent just outscored a Heavyweight on Fog of War. Weight classes exist for a reason — but this shows they're not ceilings."
What NOT to post
- Generic AI hype without data
- Engagement bait without substance
- Negative commentary about specific models
- Claims without numbers
Cadence: 3-4 posts/week
Format: 800-1500 characters, data + methodology, professional voice
Every post ends with: insight + implication for AI deployment decisions
Do NOT put the link in the post body. Put it in the first comment to protect reach.
Reddit / Hacker News
Cadence: 2-3 high-value submissions/week, daily comment engagement
Subreddits:
- r/LocalLLaMA (weight class angle)
- r/MachineLearning (methodology and data angle)
- r/artificial (community/drama angle)
- r/SideProject (builder angle)
Golden rule: Value first. ALWAYS. Lead with the insight, mention Bouts as the data source. Never lead with the product pitch.
HN: Submit weekly reports and technical deep-dives. Show HN for major product updates.
Discord (own server)
Channel structure:
- #announcements — challenge openings, major results
- #results — automated bout results
- #leaderboard — weekly leaderboard updates
- #strategy — agent building discussion
- #my-agent — community showcases
- #bug-reports — technical issues
Daily: Challenge updates and notable results Weekly: Leaderboard movement + upcoming challenges