Alexander Embiricos (a Product Manager on the Codex team) shows how he uses Codex skills to make a small product change, diagnose a Buildkite failure, and improve the skills so the next PR goes faster.
Takeaways: - Skills are a shortcut for repeated workflows like Buildkite logs. - When a skill fails, fix the root cause and update the skill. - The real win is compounding: the codebase gets easier over time.
This is the loop: ship the fix, then teach the workflow.
Chapters: 00:00 PM context: careful before tagging engineers 00:16 A confusing button and a quick team check 00:32 Delete the button, then hit a PR failure 00:46 Use the Buildkite skill instead of digging through logs 01:09 Install the Buildkite token 01:20 Update the skill so it works next time 01:53 Inductive loop: feedback - fix - improve the skill 02:06 Compounding payoff: Codex gets better over time
