Codex 自我审计提示词教程:一键沉淀 Skill 与自动化

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

回顾我最近 30 天的工作记录(若历史较短则回顾全部可用记录),找出值得沉淀打包的、重复性的手动工作流程。

按以下优先级使用可用证据:
- 最近的 Codex 会话和任务摘要。
- Codex Memories 和 rollout 摘要,用于发现跨会话重复出现的模式。
- Chronicle(如果已启用),用于发现 Codex 之外的重复工作。Chronicle 仅用于「发现线索」,重要细节应尽可能在相应的源系统中核实。
- 已有的 skills、自定义 agents 和 automations,以便复用或扩展现有资产,而不是重复创建。

广泛地寻找那些重复、耗时、易出错、上下文负担重,或能从一致流程中受益的工作。涵盖编码、研究、写作、规划、沟通、运营、分析和个人事务管理等各类工作流。

只有当一个候选项满足以下全部条件时才采取行动:
- 至少发生过两次,或明显很可能再次发生且重复成本高;
- 有稳定的输入、可重复的流程,以及明确的产出或终止条件;
- 能在速度、质量、一致性或可靠性上带来实质性提升;
- 尚未被现有资产充分覆盖。

选择最小的合适形态:
- Skill:可复用的工作流或操作手册。
- 自定义 Subagent:边界清晰、适合委派的专项角色或调查任务。
- Automation:按计划或周期执行的检查、报告、提醒或监控。
- 跳过:过于一次性、含糊、敏感或证据不足、不适合打包的工作。

首先生成一份精简的候选清单,包含:
- 重复出现的工作流
- 支撑证据及日期
- 频率／置信度
- 推荐形态:skill、subagent、automation、扩展现有资产,或跳过
- 为什么值得或不值得创建

然后只创建那些高置信度且尚不存在的项目。保持它们窄小、实用、来源清晰、易于验证。不要创建投机性的、相互重叠的或过于宽泛的资产。

最后给出总结:
- 你创建或扩展了什么
- 你刻意跳过了什么
- 哪些还需要更多证据才能打包