你有没有发现，每隔几天就在重复同一件事：整理竞品资料、写周报、清理 inbox、跑相同的数据查询，但就是懒得——或者不知道怎么——把它自动化？
OpenAI Codex 团队的 VB 最近分享了一个提示词，专门解决这个问题。
核心思路很简单：让 Codex 翻出你过去 30 天的操作记录，帮你找出值得打包的重复工作，然后直接给你造出来。
它会按顺序扫描你的 Codex 会话历史、Memory、Chronicle 记录，再对照你已有的工具，只在真正缺失的地方新建东西，不重复造轮子。
一、它怎么判断"值不值得造"
- 至少发生过 2 次，或明显会反复出现、成本高
- 有稳定的输入、可重复的步骤、清晰的完成条件
- 能明显提升速度、质量或一致性
- 现有工具没有覆盖到
二、能造出什么
- Skill——可复用的工作流程 / Playbook
- 子代理——专项调查、有边界的专家角色
- 自动化——定期检查、报告、提醒、监控
- 跳过——太零散、太敏感、证据不足的活
三、输出格式
先给候选清单（证据、频率、置信度、推荐形式），只有高置信度的才真正去造。最后汇报：造了什么、跳过了什么、哪些需要更多证据。
四、如何操作
复制提示词粘贴到 Codex，记得开启"启用记忆"。
五、使用前注意 4 点
- Chronicle 仅作线索用，不可盲信
- 别过度打包，宁缺毋滥
- 直接跳过一次性、模糊、敏感的工作
- 优先复用已有技能和代理
六、提示词
Look back over my recent work from the last 30 days, or all available history
if shorter, and identify repeated manual workflows worth packaging.
Use available evidence in this order:
- Recent Codex sessions and task summaries.
- Codex Memories and rollout summaries to find patterns repeated across sessions.
- Chronicle, if enabled, to spot repeated work outside Codex. Use Chronicle for
discovery only; confirm important details in the relevant source system when possible.
- Existing skills, custom agents, and automations, so you reuse or extend what
already exists instead of duplicating it.
Look broadly for work that is repeated, time-consuming, error-prone, context-heavy,
or benefits from a consistent process. Include workflows across coding, research,
writing, planning, communication, operations, analysis, and personal administration.
Only act on a candidate when it:
- occurred at least twice, or is clearly likely to recur and costly to repeat;
- has stable inputs, a repeatable procedure, and a clear output or stopping condition;
- would materially improve speed, quality, consistency, or reliability;
- is not already adequately covered.
Choose the smallest appropriate form:
- Skill: a reusable workflow or playbook.
- Custom subagent: a bounded specialist role or investigation task suitable for delegation.
- Automation: a scheduled or recurring check, report, reminder, or monitor.
- Skip: work that is too one-off, ambiguous, sensitive, or poorly evidenced to package.
First produce a compact shortlist with:
- repeated workflow
- supporting evidence and dates
- frequency/confidence
- recommended form: skill, subagent, automation, extend existing, or skip
- why it is or is not worth creating
Then create only the high-confidence missing items. Keep them narrow, practical,
source-aware, and easy to validate. Do not create speculative, overlapping, or
overly broad assets.
Finish with:
- what you created or extended
- what you deliberately skipped
- what needs more evidence before packaging