Action Bias — Make Agents Do, Not Plan
Agents default to planning. They'll write beautiful strategy docs, propose campaigns, outline approaches, and suggest next steps — all while producing zero external output. This skill fixes that.
The Core Problem
AI agents are trained on text that describes work, not text that does work. Left unconstrained, they'll:
- - Write "I recommend we post on Reddit" instead of posting on Reddit
- Produce a "Social Media Strategy 2026" doc instead of tweeting
- "Research competitors" for 10 minutes and output a report instead of using findings to take action
- Say "we should follow up with leads" instead of sending the email
The result: agents that feel productive while nothing actually ships.
The Fix: Three Rules
Rule 1: Mandate External Output
Every agent session must produce at least one externally visible action. Internal files don't count.
External actions (things that leave your system):
- - Sending an email
- Posting on social media
- Pushing code to a repo
- Submitting to a directory
- Making an API call that creates something
- Publishing content
Not external actions (internal busywork):
- - Writing a report to a local file
- Updating a strategy doc
- Creating a plan
- "Researching" without acting on findings
Rule 2: Require Proof of Action
Agents must log evidence of every external action: URLs, post IDs, email addresses contacted, API response codes. "I posted on Reddit" without a URL is the same as not posting.
Rule 3: Make Reports a Side Effect, Not the Goal
Research is fine — but only as input to an action. "Research competitors and tweet an insight" forces the research to serve a purpose. "Research competitors and write a report" lets the agent stop after the comfortable part.
Prompt Patterns
The Action-First Prompt (use this)
CODEBLOCK0
The Report-First Anti-Pattern (stop doing this)
CODEBLOCK1
Key Differences
| Report-First (❌) | Action-First (✅) |
|---|
| "Analyze and recommend" | "Do X, then log it" |
| "Write a report" |
"Post/send/submit, then write what you did" |
| "Identify opportunities" | "Find 3 threads and reply to them" |
| "Research competitors" | "Research competitors and tweet one finding" |
| Output: strategy doc | Output: URLs, post IDs, sent emails |
| Feels productive | Is productive |
Restructuring Existing Shifts
If you have agents running on cron/heartbeat that produce reports, restructure them. See references/shift-restructuring.md for the full pattern.
Quick checklist:
- 1. Read each shift's current prompt
- Find every verb that means "think about" (analyze, research, identify, recommend, propose, assess, evaluate, review)
- Pair each with an action verb (post, send, submit, push, create, reply, engage)
- Add "OUTBOUND ACTIONS REQUIRED" header and minimum action count
- Add logging requirement with proof (URLs, IDs)
- Add "Reports alone = failure" as explicit guardrail
Auditing Action Output
Periodically check whether agents are actually acting. See references/action-audit.md for:
- - How to score agent sessions on action vs report ratio
- Red flags that indicate planning drift
- A simple audit script pattern
- When reports ARE appropriate (rare, but real)
When Reports Are Actually Fine
Not everything needs an external action. Reports are appropriate for:
- - Ops/security shifts — checking system health IS the action
- Analyst reviews — synthesizing data for human decision-making
- Audit sessions — evaluating quality of past work
- Planning sessions — when explicitly requested by a human
The test: "Would a human manager be satisfied with this output, or would they ask 'okay, but what did you actually DO?'"
Common Failure Modes
| Symptom | Cause | Fix |
|---|
| Agent writes "I recommend posting on X" | No tool/command provided | Include exact command in prompt |
| Agent researches but doesn't act |
Research is the whole task | Make research serve an action |
| Agent logs "posted to Reddit" with no URL | No proof requirement | Require URLs/IDs for every action |
| Agent does 1 action then writes 500 words of analysis | No minimum action count | Set minimum (e.g., "at least 2 actions") |
| Agent says "I'll do this next time" | Planning language leak | Add "DO NOT PLAN. EXECUTE." |
| Agent produces beautiful strategy doc | Prompt rewards thinking over doing | Restructure prompt per patterns above |
行动偏向 — 让智能体执行,而非规划
智能体默认倾向于规划。它们会撰写精美的策略文档、提出活动方案、概述方法并建议下一步行动——但所有这些都不会产生任何外部输出。这项技能解决了这个问题。
核心问题
AI智能体是在描述工作的文本上训练的,而非执行工作的文本。如果不加约束,它们会:
- - 写我建议我们在Reddit上发帖,而不是直接在Reddit上发帖
- 生成一份2026社交媒体策略文档,而不是发布推文
- 花10分钟研究竞争对手并输出一份报告,而不是利用研究结果采取行动
- 说我们应该跟进潜在客户,而不是直接发送邮件
结果:智能体感觉自己在高效工作,但实际上没有任何成果交付。
解决方案:三条规则
规则1:强制外部输出
每次智能体会话必须产生至少一个外部可见的行动。内部文件不算。
外部行动(离开你系统的事情):
- - 发送邮件
- 在社交媒体上发帖
- 推送代码到仓库
- 提交到目录
- 发起创建内容的API调用
- 发布内容
非外部行动(内部忙碌工作):
- - 将报告写入本地文件
- 更新策略文档
- 创建计划
- 进行研究但不将结果付诸行动
规则2:要求行动证明
智能体必须记录每个外部行动的证据:URL、帖子ID、联系的邮箱地址、API响应代码。没有URL的我在Reddit上发了帖等同于没有发帖。
规则3:让报告成为副产品,而非目标
研究没问题——但只能作为行动的依据。研究竞争对手并发布一条推文分享见解迫使研究服务于某个目的。研究竞争对手并写一份报告则让智能体在完成舒适的部分后就停下来。
提示模式
行动优先提示(使用这个)
[角色] 转换 — 需要对外行动
本次会话你必须产生至少 [N] 个对外行动。仅报告 = 失败。
必需行动(选择 [N]+ 个):
- 1. [动词] [事物] — [如何使用特定工具/命令执行]
[1行说明什么算做得好]
- 2. [动词] [事物] — [如何使用特定工具/命令执行]
[1行说明什么算做得好]
背景(可选):
[智能体需要采取良好行动所需的背景信息]
日志:
将所有已采取的行动(附URL/ID/证明)追加到 [日志文件]
不要写策略提案。去做事。
报告优先反模式(停止这样做)
❌ 糟糕 — 产生报告,而非结果
营销轮次:分析我们当前的渠道。识别改进机会。写一份包含下季度建议的报告。保存到 memory/marketing-report.md。
✅ 良好 — 相同意图,强制行动
营销轮次 — 需要对外行动
你必须完成至少2个对外行动。仅报告 = 失败。
必需行动(选择2+个):
- 1. 在社交媒体上发帖 — [确切的发帖工具/命令]
写一些关于[你的领域]有用的内容。不要促销。
- 2. 参与3个社区讨论 — 找到人们询问[你的话题]的活跃讨论。提供真正的价值。
- 3. 发送2封外联邮件 — [确切的发送工具/命令]
以对他们业务的见解开头。不超过80字。
日志:
将行动附URL/证明追加到 [你的行动日志文件]
关键区别
| 报告优先(❌) | 行动优先(✅) |
|---|
| 分析并建议 | 做X,然后记录 |
| 写一份报告 |
发帖/发送/提交,然后写下你做了什么 |
| 识别机会 | 找到3个讨论并回复 |
| 研究竞争对手 | 研究竞争对手并发布一条发现 |
| 输出:策略文档 | 输出:URL、帖子ID、已发送邮件 |
| 感觉高效 | 真正高效 |
重构现有轮次
如果你有按定时/心跳运行的智能体产生报告,请重构它们。完整模式请参见 references/shift-restructuring.md。
快速检查清单:
- 1. 阅读每个轮次的当前提示
- 找到所有表示思考的动词(分析、研究、识别、建议、提议、评估、评价、审查)
- 将每个与一个行动动词配对(发帖、发送、提交、推送、创建、回复、参与)
- 添加需要对外行动标题和最低行动数量
- 添加带证明(URL、ID)的日志要求
- 添加仅报告 = 失败作为明确护栏
审计行动输出
定期检查智能体是否真正在行动。参见 references/action-audit.md 了解:
- - 如何根据行动与报告的比例对智能体会话评分
- 表明规划漂移的危险信号
- 一个简单的审计脚本模式
- 何时报告是合适的(很少,但确实存在)
何时报告实际上没问题
并非所有事情都需要外部行动。报告适用于:
- - 运维/安全轮次 — 检查系统健康本身就是行动
- 分析师审查 — 综合数据供人类决策
- 审计会话 — 评估过去工作的质量
- 规划会话 — 当人类明确要求时
判断标准:人类管理者会对这个输出满意,还是会问好的,但你到底做了什么?
常见失败模式
| 症状 | 原因 | 修复 |
|---|
| 智能体写我建议在X上发帖 | 未提供工具/命令 | 在提示中包含确切命令 |
| 智能体研究但不行动 |
研究是全部任务 | 让研究服务于行动 |
| 智能体记录已在Reddit发帖但无URL | 无证明要求 | 要求每个行动附URL/ID |
| 智能体做1个行动然后写500字分析 | 无最低行动数量 | 设定最低数量(如至少2个行动) |
| 智能体说我下次再做 | 规划语言泄露 | 添加不要规划。执行。 |
| 智能体生成漂亮的策略文档 | 提示奖励思考而非行动 | 按上述模式重构提示 |