@YuLin807: This is a very valuable official Codex self-improvement prompt: Recommended use: "Review my recent work over the past 30 days (or all available history if shorter), and identify repetitive manual workflows worth packaging. Use available evidence in the following order: - Most...

X AI KOLs Timeline Tools

Summary

Shares an officially approved Codex self-improvement prompt that guides reviewing recent work and identifying repeatable manual workflows to create skills, sub-agents, or automations for improved efficiency.

This is a very valuable official Codex self-improvement prompt: Recommended use: "Review my recent work over the past 30 days (or all available history if shorter), and identify repetitive manual workflows worth packaging. Use available evidence in the following order: - Recent Codex session and task summaries. - Codex memory and rollout summaries to find patterns that repeat across sessions. - If enabled, chronicles to discover repetitive work outside Codex. Only use chronicles for discovery; confirm important details in relevant source systems whenever possible. - Existing skills, custom agents, and automations to reuse or extend what already exists, rather than recreating it. Broadly look for work that is repetitive, time-consuming, error-prone, context-heavy, or benefits from a consistent process. Include workflows across coding, research, writing, planning, communication, operations, analysis, and personal management. Only take action on a candidate when it meets the following criteria: - Has occurred at least twice, or is clearly likely to repeat with high cost of repetition; - Has stable inputs, repeatable procedures, and clear outputs or stopping conditions; - Would substantially improve speed, quality, consistency, or reliability; - Is not already adequately covered. Choose the smallest appropriate form: - Skill: reusable workflow or playbook. - Custom sub-agent: a well-defined expert role or investigative task suitable for delegation. - Automation: scheduled or recurring checks, reports, reminders, or monitoring. - Skip: work that is too one-off, vague, sensitive, or lacking sufficient evidence to package. First generate a concise shortlist including: - Repetitive workflow - Supporting evidence and dates - Frequency/confidence - Recommended form: skill, sub-agent, automation, extend existing, or skip - Why it is or is not worth creating Then only create high-confidence missing items. Keep them narrow, practical, source-aware, and easily verifiable. Do not create speculative, overlapping, or overly broad assets. Finally, end with: - What you created or extended - What you deliberately skipped - What needs more evidence before packaging"
Original Article
View Cached Full Text

Cached at: 05/26/26, 03:12 PM

This is a valuable officially recognized codex self improve prompt:

Recommended for use:

“Review my recent work from the past 30 days (or all available history if shorter), and identify repetitive manual workflows worth packaging.

Use available evidence in this order:

  • Recent Codex sessions and task summaries.
  • Codex memories and rollout summaries to find patterns across sessions.
  • If enabled, chronicles, to discover repetitive work outside of Codex. Use chronicles only for discovery; confirm key details in relevant source systems whenever possible.
  • Existing skills, custom agents, and automations, to reuse or extend what already exists rather than recreate.

Search broadly for work that is repetitive, time-consuming, error-prone, context-heavy, or benefits from consistent process. Include workflows spanning coding, research, writing, planning, communication, operations, analysis, and personal management.

Only act on candidates that meet all of the following:

  • Occurred at least twice, or is clearly likely to repeat and costly to repeat;
  • Has stable inputs, a repeatable procedure, and clear output or stop conditions;
  • Would materially improve speed, quality, consistency, or reliability;
  • Is not already adequately covered.

Choose the smallest appropriate form:

  • Skill: reusable workflow or playbook.
  • Custom sub-agent: well-defined expert role or investigation task suitable for delegation.
  • Automation: scheduled or recurring checks, reports, reminders, or monitoring.
  • Skip: work that is too one-off, vague, sensitive, or lacks sufficient evidence to package.

First generate a concise shortlist including:

  • Repetitive workflow
  • Supporting evidence and dates
  • Frequency / confidence
  • Recommended form: skill, sub-agent, automation, extend existing, or skip
  • Why it is or is not worth creating

Then only create high-confidence missing items. Keep them narrow, practical, source-aware, and easy to verify. Do not create speculative, overlapping, or overly broad assets.

Finally, conclude with:

  • What you created or extended
  • What you deliberately skipped
  • What needs more evidence before packaging

Greg Brockman @gdb · May 25: self improvement prompt for codex x.com/reach_vb/statu…

Similar Articles

@yoyo__AI: Automatically distill yourself with a single Codex prompt, fully automate daily repetitive tasks. Steps: Open Codex Settings → Personalization → Memory → Enable Chronicle. Enter the prompt: Review my Chronicle memory, find workflows I repeat multiple times, convert them into skills. Codex expands search...

X AI KOLs Timeline

Codex introduces a new feature that automatically analyzes user historical memory with a single prompt, extracts repetitive workflows, and converts them into evolvable skills, automating daily repetitive tasks.

@Luckyjudy666: 8 Tips to Make Codex Your Personal Assistant 1. Build a Shared Memory for Codex Core rules go in Agents.md, project background in Obsidian, repeated processes as skills, personal preferences and common questions in Memories. Otherwise, Codex is like a new colleague every time, having to explain everything from scratch...

X AI KOLs Timeline

This article shares 8 tips for using the Codex AI assistant effectively, including building shared memory, remote task execution, scheduled automation, file organization, and teaching new software operations, all aimed at improving work efficiency.

@xiangxiang103: Friends who just installed Codex, don't rush to use it—if you don't do these two things, it will only get dumber over time. This thread perfectly explains the "taming guide" I personally use: ① Let it first get to know you and your computer; list the 10 most important things to tell it in one sentence. ② Set up a dedicated workspace + two key documents (pitfall log / AGE…

X AI KOLs Timeline

This tweet provides a detailed Codex "taming guide", suggesting that you first let Codex get to know the user and the computer, set up a dedicated workspace and create a pitfall log and AGES behavior guidelines document to improve its usage and avoid getting dumber over time.

@Easycompany333: The Codex video officially named by OpenAI is worth collecting. In less than 2 hours, it thoroughly explains the Codex + GPT-5.5 combo: - How to configure skills. - How to use plugins. - How to build automation workflows. - How to run multiple tasks in parallel. - And most importantly, how to turn Codex into a development system that continuously works for you.

X AI KOLs Timeline

Recommends a Codex video tutorial officially named by OpenAI, detailing how to configure skills, use plugins, and build automation workflows to turn Codex into a continuously working development system.