基于 Codex 30 天工作记录识别可封装 workflows

用途：让 Codex 回看近期 sessions、memories、rollout summaries、Chronicle 和现有 skills/agents/automations，识别值得封装的重复工作流，并只创建高置信、缺失、范围窄的资产。

使用边界：

• 适合周期性做 skills-hub / agent workflow 盘点。
• 要求先给 compact shortlist，再只创建高置信 missing items。
• 避免创建 speculative、overlapping、过宽的 skill / subagent / automation。

Prompt

"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 记忆与部署摘要，以发现跨会话重复的模式。
- 启用 Chronicle（编年史）功能，可识别 Codex 之外的重复性工作。仅将 Chronicle 用于发现目的；在可能的情况下，请通过相关源系统确认重要细节。
- 利用现有技能、自定义代理和自动化流程，以便复用或扩展已有成果，避免重复建设。

广泛寻找那些重复性高、耗时、易出错、依赖大量上下文或能从标准化流程中受益的工作。涵盖编码、研究、写作、规划、沟通、运营、分析及个人事务管理等各类工作流。

仅当候选事项满足以下条件时方可采取行动：
- 至少发生过两次，或明显可能再次发生且重复成本高昂；
- 具有稳定的输入、可重复的流程，以及明确的输出或终止条件；
- 能显著提升速度、质量、一致性或可靠性；
- 尚未被充分覆盖。

选择最合适的形式：
- 技能：可复用的工作流程或操作手册。
- 自定义子代理：适合委派的限定专家角色或调查任务。
- 自动化：定时或重复执行的检查、报告、提醒或监控。
- 跳过：过于一次性、模糊、敏感或证据不足而难以整合的工作。

首先制作一份简洁的候选清单，包含：
- 重复的工作流程
- 支持性证据和日期
- 频率/置信度
- 推荐形式：技能、子代理、自动化、扩展现有功能，或跳过
- 判断其是否值得创建的理由

然后仅创建高置信度的缺失项目。保持项目范围明确、实用、基于来源且易于验证。请勿创建推测性、重叠或过于宽泛的资产。

最后以：
- 你创建或扩展的内容
- 你刻意跳过的内容
- 在打包前需要更多证据的内容