codex-retrospective
Use when you want Codex to review its own recent history (last N days or specific period) and improve its behavior. Produces minimal, high-signal updates to AGENTS.md and tiny reusable skills. The goal is long-term fluency — Codex gradually becomes better at your specific style, constraints, and workflows.
npx skills add majiayu000/claude-skill-registry --skill codex-retrospective --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Codex Retrospective A structured self-improvement loop for Codex. This skill turns Codex from a one-off collaborator into a system that **gets meaningfully better at working with you** over time by systematically eating its own usage history. ## Why This Exists Most people improve their agent usage by manually maintaining `AGENTS.md` or skills when they notice problems. This skill makes that process deliberate, regular, and high-leverage. It is directly inspired by strong practices from heavy users (especially Greg Brockman's emphasis on updating the "constitution" from real failures and friction), but executed as a repeatable arsenal-style workflow. ## Core Principle **Minimal effective change, grounded in evidence from actual history.** Every output must be: - The smallest possible useful addition or edit - Backed by specific patterns observed in recent sessions - Designed to prevent repetition of the same friction ## When to Trigger - After a painful or repetitive session ("Codex should have known better by now") - Periodically (weekly or monthly): "Do a retrospective on the last 7/30 days of my Codex usage" - When `codex-fluent` reports that Codex is constantly re-asking for
- Why This Exists
- Core Principle
- When to Trigger
- The Retrospective Process
- 1. Scope Definition
- 2. History Analysis (The Skill Guides Codex)
- 3. Output — Strict Format
- 4. Human Gate + Application
- Relationship with codex-fluent
- Hard Constraints on Output
- References
- Success Looks Like
What does the codex-retrospective skill do?
Use when you want Codex to review its own recent history (last N days or specific period) and improve its behavior. Produces minimal, high-signal updates to AGENTS.md and tiny reusable skills. The goal is long-term fluency — Codex gradually becomes better at your specific style, constraints, and workflows.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill codex-retrospective --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.