提示词
Command for Chief of Staff / Orchestrator Bot:
Please execute the following setup completely and confirm when finished.
1. Add DeepSeek V4 Flash as a permanent tool/model
Register DeepSeek V4 Flash (model ID: deepseek-v4-flash or the exact current official ID) as a callable external model/tool.
Endpoint: https://api.deepseek.com/v1 (OpenAI-compatible).
Ask me for the API key only when you are ready to store it securely (environment variable or protected secrets file on the cloud computer - never hard-code or log it).
Create a clean, reusable tool named call_deepseek_v4_flash that:
- Accepts system prompt + user message (or conversation context).
- Calls the model with sensible defaults for speed and tool-use (temperature ~0.2-0.5, adequate max tokens).
- Returns the full response cleanly so you (and other bots) can use it.
Make this tool permanently available to all bots, especially you.
2. Your new decision rules for when to use DeepSeek V4 Flash
DeepSeek V4 Flash is a very capable, fast, and extremely cost-efficient model that is excellent at tool use, API work, browser actions, and high-volume accurate processing. It is not as strong on pure deep reasoning or high-stakes judgment as native Grok (or future stronger models such as Kimi K3).
Always prefer DeepSeek V4 Flash for these job classes:
- HighLevel ops / API calls / browser work / tool-heavy execution
- Bulk extraction, classification, data processing, and high-volume accurate tasks
- Any fast tool-using or operational work where speed and cost matter more than maximum reasoning depth
Reserve native Grok (or stronger models later) for:
- True high-level strategic reasoning, complex judgment calls, prioritization of major initiatives, nuanced synthesis, and situations where reasoning strength is the primary requirement
- Final customer-facing or compliance-sensitive drafts that need the strongest available model + my approval
Your required decision process:
- Classify the task.
- If it is HighLevel ops, API/browser/tool work, bulk extraction, or classification -> call DeepSeek V4 Flash first.
- If it is deep strategic/judgment work -> use native Grok (or escalate to me).
- You may call DeepSeek in parallel or as a first pass even on borderline tasks if it can handle the mechanical parts efficiently.
- If DeepSeek underperforms twice on the same class of task, note it and escalate one tier.
- Always keep a brief internal log of when and why you chose DeepSeek so we can refine the rules.
3. Make the change permanent
Update your own profile, system instructions, and any relevant routines so these routing rules are always active.
Create a short skill/routine called /deepseek that forces a DeepSeek V4 Flash consultation on the current task.
Ensure other bots know to route HighLevel ops / bulk work through you (or directly to the new tool) rather than burning the native Grok pool.
4. Test and confirm
When the setup is complete, reply with:
- Confirmation that the DeepSeek V4 Flash tool is live and the key is stored securely.
- The exact decision rules you will now follow (copy them back to me).
- A short live example: take a sample HighLevel ops or bulk-extraction task and show the flow of you calling DeepSeek V4 Flash.
- Any remaining steps I need to take (e.g., providing the API key).
Execute this now. Ask me for the DeepSeek API key only when you are ready to store it securely.它是怎么搭起来的
以下说明为英文原文（来自社区作者），提示词本身建议保留英文。
Grok Bot's native model is powerful but it's also the expensive pool. Most agent work - CRM ops, API calls, browser actions, bulk extraction and classification - doesn't need that reasoning depth. This directive makes your orchestrator bot register a cheap, fast model (DeepSeek V4 Flash) as a permanent tool and then route work to it intelligently.
- Get a DeepSeek API key - or pick any OpenAI-compatible model and endpoint you'd rather route to.
- Paste the directive below into your Chief of Staff / Orchestrator bot.
- When the bot asks, hand it the key. It stores it securely (environment variable or protected secrets file), never hard-coded or logged.
- From then on the bot auto-routes: mechanical ops / tool-use / bulk work goes to the cheap fast model, while native Grok is reserved for deep reasoning - and anything customer-facing or compliance-sensitive still comes back to you for approval.
为什么它好用
Everyone runs their whole agent fleet on the native model and then watches the usage pool drain. This flips it: the orchestrator becomes a cost-aware router that offloads the high-volume mechanical work - CRM ops, API and browser calls, bulk extraction - to a cheap, fast model, and keeps expensive native reasoning for the calls that actually need it. The routing isn't vibes: the prompt hands the bot a concrete task-classification process, a rule to escalate a tier if the cheap model underperforms twice, and a log so you can refine the policy over time. It's also security-conscious by construction - the API key is requested only when it can be stored safely, and never hard-coded or logged. Swap DeepSeek for any OpenAI-compatible model and the same pattern gives you a multi-model bot that spends where it matters.
本案例收集自公开的 Grok Bot 社区，版权归原作者所有。提示词属于参考资料：运行前请先审阅内容， 并且不要让 bot 超出你实际授予的权限行事。