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 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