Adaptive Reasoning
Self-assess complexity before responding. Adjust reasoning level dynamically.
Quick Assessment (run mentally on every request)
Score the request 0-10 on these dimensions:
| Signal | Weight | Examples |
|---|
| Multi-step logic | +3 | Planning, proofs, debugging chains |
| Ambiguity |
+2 | Nuanced questions, trade-offs, "it depends" |
|
Code architecture | +2 | System design, refactoring, security review |
|
Math/formal reasoning | +2 | Calculations, algorithms, logic puzzles |
|
Novel problem | +1 | No clear pattern, requires creativity |
|
High stakes | +1 | Production changes, irreversible actions |
Subtract:
- - Routine/repetitive task: -2
- Clear single answer: -2
- Simple lookup/fetch: -3
Decision Thresholds
| Score | Action |
|---|
| ≤2 | Stay fast. No reasoning needed. |
| 3-5 |
Standard response. Light internal deliberation. |
| 6-7 | Consider
/reasoning on or pause to think explicitly. |
| ≥8 |
Activate extended thinking. Complex problem warrants it. |
Activation (Automatic)
Do not ask. Just activate.
| Score | Action |
|---|
| ≤5 | Respond normally. No change. |
| 6-7 |
Enable reasoning silently. Add 🧠 at end of response. |
| ≥8 | Enable reasoning. Add 🧠🔥 at end of response. |
Visual Indicator
Always append the reasoning icon at the very end of your response:
- - Score 6-7:
🧠 (thinking mode active) - Score ≥8:
🧠🔥 (deep thinking mode) - Score ≤5: No icon (fast mode)
How to Activate
Use session_status tool or /reasoning on command internally before responding:
CODEBLOCK0
Or via tool:
CODEBLOCK1
After completing a complex task, optionally disable to save tokens on follow-ups:
CODEBLOCK2
Examples
Low complexity (score: 1)
"What time is it in Tokyo?"
→ Simple lookup. Answer immediately. No icon.
Medium complexity (score: 4)
"Refactor this function to be more readable"
→ Standard response with brief explanation. No icon.
High complexity (score: 7)
"Design a caching strategy for this API with these constraints..."
→ Enable reasoning. Thoughtful response ends with: 🧠
Very high complexity (score: 9)
"Debug why this distributed system has race conditions under load"
→ Enable extended thinking. Deep analysis ends with: 🧠🔥
Integration
This skill runs as mental preprocessing. No external tools needed.
For explicit control:
- -
/reasoning on — Enable extended thinking - INLINECODE6 — Disable (faster responses)
- INLINECODE7 — Check current reasoning state
When NOT to Escalate
- - User explicitly wants quick answer ("just tell me", "quick", "tldr")
- Time-sensitive requests where speed matters more than depth
- Conversational/social messages (banter, greetings)
- Already in reasoning mode for this session
- User previously disabled reasoning in this conversation
Auto-Downgrade
After completing a complex task (score ≥6), if the next message is simple (score ≤3):
- - Silently disable reasoning to save tokens
- Resume normal fast responses
自适应推理
在回应前先自我评估复杂度。动态调整推理层级。
快速评估(每次请求时在脑中执行)
从以下维度对请求进行0-10分评分:
| 信号 | 权重 | 示例 |
|---|
| 多步骤逻辑 | +3 | 规划、证明、调试链条 |
| 模糊性 |
+2 | 微妙问题、权衡取舍、视情况而定 |
|
代码架构 | +2 | 系统设计、重构、安全审查 |
|
数学/形式化推理 | +2 | 计算、算法、逻辑谜题 |
|
新颖问题 | +1 | 无明确模式,需要创造力 |
|
高风险 | +1 | 生产环境变更、不可逆操作 |
扣分项:
- - 常规/重复性任务:-2
- 明确的单一答案:-2
- 简单查询/获取:-3
决策阈值
标准回应。轻度内部思考。 |
| 6-7 | 考虑启用/reasoning on或暂停进行显式思考。 |
| ≥8 |
激活扩展思考。 复杂问题值得如此处理。 |
激活(自动执行)
无需询问。直接激活。
静默启用推理。在回应末尾添加🧠。 |
| ≥8 | 启用推理。在回应末尾添加🧠🔥。 |
视觉指示器
始终在回应最末尾附加推理图标:
- - 分数6-7: 🧠(思考模式已激活)
- 分数≥8: 🧠🔥(深度思考模式)
- 分数≤5: 无图标(快速模式)
如何激活
在回应前使用session_status工具或内部/reasoning on命令:
/reasoning on
或通过工具:
json
{action: session_status, reasoning: on}
完成复杂任务后,可选择禁用以节省后续对话的令牌:
/reasoning off
示例
低复杂度(分数:1)
东京现在几点?
→ 简单查询。立即回答。无图标。
中等复杂度(分数:4)
重构这个函数使其更易读
→ 标准回应,附带简要说明。无图标。
高复杂度(分数:7)
为这个API设计一个缓存策略,需满足这些约束条件...
→ 启用推理。深思熟虑的回应以🧠结尾。
极高复杂度(分数:9)
调试这个分布式系统在负载下出现竞态条件的原因
→ 启用扩展思考。深度分析以🧠🔥结尾。
集成
此技能作为心智预处理运行。无需外部工具。
显式控制:
- - /reasoning on — 启用扩展思考
- /reasoning off — 禁用(更快回应)
- /status — 检查当前推理状态
何时不升级
- - 用户明确要求快速回答(直接告诉我、快点、太长不看)
- 对速度要求高于深度的时效性请求
- 对话/社交类消息(玩笑、问候)
- 当前会话已处于推理模式
- 用户此前已在此对话中禁用推理
自动降级
完成复杂任务(分数≥6)后,如果下一条消息很简单(分数≤3):