用一份 GROKBOT.md 给 Grok Bot 定工程契约
作者主张别再每次手写指令,而是把状态存本地、缺变量直接报错、重试两次即终止,做成 Grok Bot 的固定技能文件。
A SINGLE MARKDOWN FILE JUST REPLACED THE ENTIRE PROMPTING ERA FOR GROK BOT writing custom instructions for every session is manual labor that does not scale. instead of treating the model like a chat interface, you bind it to a strict engineering contract. the GROKBOT.md protocol: > shift all state to the local disk so if the session dies the agent reads the four core files and resumes exactly where it left off > force a hard failure on missing variables instead of letting the model invent plausible hallucinated values to fill the gaps > cap execution at two retries before writing the failure to a log and terminating the run to protect your production data the real test is the install: paste the contract as a skill and ask the bot to name the rules it cannot enforce. that answer alone is worth the setup time. the full configuration 👇
这条是引用着另一条写的:x.com/irongiantxbt/status/2109293672495784029