频繁使用 Codex 的开发者可以靠这个提示自动发现并打包重复工作流，省去手动梳理的麻烦，直接提升自动化效率。
VB Srivastav 分享了一个改进版的 Codex 自我改进提示，让 Codex 跨会话、记忆和 Chronicle 查找重复的手动工作流，并自动创建最小的实用技能、子代理或自动化。提示要求 Codex 优先复用已有资产，只对高频、稳定、可重复的任务进行打包，避免创建重复或过于宽泛的内容。最终输出包括创建了什么、跳过了什么以及需要更多证据的项目。这个提示能显著提升 Codex 用户的自动化效率，减少重复劳动。
self improvement prompt for codex
self improvement prompt for codex Vaibhav (VB) Srivastav @reach_vb UPDATE: Came up with an even better version of this prompt after the feedback Ask Codex to look across your sessions, Memories, and Chronicle, identify patterns, reuse what already exists, and only create the smallest useful skill, subagent, or automation. "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" 🔗 View Quoted Tweet 💬 64 🔄 145 ❤️ 2086 👀 214812 📊 620 ⚡