让 Grok Bot 记住工具用法以省额度的提示词
给出六条规则提示词：服务速查表、最轻路由优先、改前先读、失败日志、不许猜、每周效率评分。
Want to make your Grok Bot more efficient and burn less of your usage limits? Every time Grok Bot needs to get something done, it has to decide which route to use: - What it already knows - A direct connector - Web search - The browser - Or you The problem is it can waste tokens retrying failed paths, guessing field names or rediscovering service details it already learned. You can fix that by making it remember what works. Here’s the prompt to use to get more from your Grok Bot usage limits: From now on, improve how you pick and use tools. Follow these rules: 1 - Service cheat sheets. For every connected service or website you use, keep a short saved note with: - what it’s for - exact database, field and label names - the query or steps that worked - known gotchas Read the cheat sheet before using that service and update it whenever you learn something new. 2 - Choose the lightest route first. Use this order: What you already know or have saved → direct connection → public web search → browser → me. Before opening the browser, explain why a direct connection can’t do the job. If a connection is broken, tell me. Don’t quietly work around it. 3 - Look before you change. Before any update, send or delete, do a read-only check first. Confirm: - the record exists - the field names are correct - the values are what you expect After the change, read it back and confirm it saved correctly. 4 - Keep a failure log. Whenever something fails, record: - what you tried - why it failed - what worked instead Check this log before attempting the same kind of job again. 5 - No guessing. If you don’t know a field name, ID, page, database or label, look it up. Don’t keep trying different names until one works. 6 - Weekly efficiency scorecard. Every Monday, tell me: - how many jobs finished first try - how many needed retries - which service caused the most retries - the most common reason for wasted attempts Then suggest one fix for the next week. The goal isn’t just to make Grok Bot smarter. It’s to stop it wasting usage relearning things it already figured out.