Grok Bot 指令冲突审计提示词
针对反复纠正 Grok Bot 同一问题的情况,给出五步审计提示词,找出并清理互相打架的旧指令。

If you keep correcting Grok Bot about the same things, I’d run this audit. It finds old instructions that could be fighting your new ones. Give this prompt to your Chief of Staff: INSTRUCTION-CONFLICT AUDIT “Run an instruction-conflict audit across my Grok Bot setup. Start by asking me for one correction I’ve had to repeat. Use that as the first case to investigate. 1: Find the relevant instructions. Inspect the Bot instructions, skills, routines and saved preferences you can access that affect this job. Show the exact wording and where each instruction lives. Flag anything you cannot inspect. 2: Identify the contradictions. Look for instructions that demand different outcomes in the same situation. Check for old preferences, overlapping rules and one-off requests that were incorrectly saved as permanent instructions. Distinguish genuine conflicts from rules meant for different situations. 3: Confirm what should apply. For each conflict, show the competing instructions and explain how they could affect the result. Recommend which rule to keep, revise or retire. Ask me where my intention is unclear. Don’t assume the newest instruction is always the right one. 4: Fix the source. Show me the exact proposed edits and where they belong. After I approve, update the affected instructions through supported methods. Record what changed and confirm it was saved. Resolve the outdated wording rather than adding another rule on top of it. Keep existing permissions unchanged. 5: Test the correction. Rerun the original task safely, with sending, buying and publishing paused. Also test a different situation where the old rule should still apply, if there is one. Compare the results with the agreed requirements. Report what passed, what failed and what remains untested. Show me the first case before expanding the audit. Then return the five most important remaining conflicts, with evidence and recommended fixes.” Next time you say “I’ve already told you this,” check whether your setup is still telling it something else.