Six-bot mobile game studio: Rank'em
六个 Bot 分工跑一款手游，从发行到修缺陷。 Six Bots split a mobile game, from release work through bug fixes.
Ryan Perry 用六个 Grok Bot 分工跑手游 Rank'em 生命周期：Mobile Orchestrator、Rankem Engineer、Creatives、GCS、Analytics、Bug fix。每个 Bot 有独立电脑、例行任务与技能，互相交接而不经过人。编码工具覆盖构建与基建，Grok Bot 接住发行、QA、买量和素材。文章写清角色、交接与真实踩坑。 Ryan Perry staffed Rank'em with six Grok Bots — Mobile Orchestrator, Rankem Engineer, Creatives, GCS, Analytics, Bug fix — each with its own computer, routines, and skills, handing off without routing through him. Coding tools cover build/infra; Grok Bot covers release, QA, UA, and creative. The post spells out roles, handoffs, and what they caught.
为什么推荐Why we recommend it 可复现的多 Bot 工作室搭法，付款/投放变更仍需人审。 A reproducible multi-bot studio pattern; still review spend and store changes.
社区完整案例研究（HN item 49447324）：六个窄角色 + 真实手游下载过千。Full community case study (HN item 49447324): six narrow seats on a live game past 1k downloads.
不直接改广告预算、不提交商店上架、不推生产；只起草与交接，花钱与发布留给人。 Do not change ad spend, submit store listings, or ship production; draft and hand off — humans own money and release.
先在可撤回、不外发的范围内试跑。本条未批准前：不直接改广告预算、不提交商店上架、不推生产；只起草与交接，花钱与发布留给人。。 Try it first in a reversible, non-outbound scope. Until approved: Do not change ad spend, submit store listings, or ship production; draft and hand off — humans own money and release..
这条用法已包含可复用 Skill。跑通安全范围后，立刻把步骤固化下来。 This use already includes a reusable Skill. After the safe pass, lock the steps in.
输出稳定后再打开例行 / 定时。本条已有例行形态，不要一上来就无人值守外发。 Turn on the routine / schedule only after output is stable. This item already has a routine shape — do not start unattended outbound.
