<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Codex on Work You Can Explain</title>
		<link>https://workyoucanexplain.com/tags/codex/</link>
		<description>Recent content in Codex on Work You Can Explain</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
			<copyright>Copyright © Work You Can Explain</copyright>
		
		
			<lastBuildDate>Mon, 24 Aug 2026 00:00:00 -0500</lastBuildDate>
		
			<atom:link href="https://workyoucanexplain.com/tags/codex/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Adapt Shared Agent Skills to Your Own Workflow</title>
				<link>https://workyoucanexplain.com/posts/adapt-shared-agent-skills-to-your-own-workflow/</link>
				<pubDate>Mon, 24 Aug 2026 00:00:00 -0500</pubDate>
				<guid>https://workyoucanexplain.com/posts/adapt-shared-agent-skills-to-your-own-workflow/</guid>
				<description>&lt;p&gt;An existing agent skill is a starting point, not an authority. Before you install, combine, or adapt one into a skill you already maintain, inspect what it assumes, compare it with your current workflow, and test the meaningful difference on a small safe task.&lt;/p&gt;&#xA;&lt;p&gt;Keep at most one bounded adaptation at a time. Preserve the source, version, license, rationale, rejected alternatives, and rollback path. A passing example is evidence about that task and environment. It is not proof that one skill is universally better.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Grow With Skills: Improve the Agent While You Work</title>
				<link>https://workyoucanexplain.com/posts/grow-with-skills/</link>
				<pubDate>Tue, 28 Jul 2026 00:00:00 -0500</pubDate>
				<guid>https://workyoucanexplain.com/posts/grow-with-skills/</guid>
				<description>&lt;p&gt;A completed task can reveal how a skill should improve, but the task is&#xA;evidence, not proof. Record the observed gap, separate the reusable lesson from&#xA;the task&amp;rsquo;s local context, and propose one bounded change. A shared skill can&#xA;supply another design to compare, but it is a source, not an upstream workflow&#xA;you must follow. Keep a local revision only when it addresses an observed need,&#xA;preserves attribution and boundaries, and passes fresh-task tests.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Package a Repeatable AI Workflow as a Skill</title>
				<link>https://workyoucanexplain.com/posts/package-a-repeatable-ai-workflow-as-a-skill/</link>
				<pubDate>Fri, 24 Jul 2026 00:00:00 -0500</pubDate>
				<guid>https://workyoucanexplain.com/posts/package-a-repeatable-ai-workflow-as-a-skill/</guid>
				<description>&lt;p&gt;Package a workflow as a skill when it recurs across tasks, contains several&#xA;steps, requires some agent judgment, and benefits from shared instructions,&#xA;references, scripts, templates, and a consistent output. Use ordinary code for&#xA;deterministic operations and &lt;code&gt;AGENTS.md&lt;/code&gt; for durable repository rules.&lt;/p&gt;&#xA;&lt;p&gt;OpenAI&amp;rsquo;s current&#xA;&lt;a href=&#34;https://developers.openai.com/codex/skills/&#34;&gt;Codex Build skills documentation&lt;/a&gt;&#xA;defines an agent skill as a directory with a required &lt;code&gt;SKILL.md&lt;/code&gt;. That file&#xA;supplies a name, a description that helps ChatGPT or Codex decide when to use&#xA;the skill, and the workflow instructions. The directory can also include&#xA;scripts, references, and assets. Follow the validation tools in the Codex&#xA;environment where the skill will run; other products may package or distribute&#xA;the same workflow differently.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Use `AGENTS.md` to Teach an AI About a Repository</title>
				<link>https://workyoucanexplain.com/posts/use-agents-md-to-teach-an-ai-about-a-repository/</link>
				<pubDate>Fri, 24 Jul 2026 00:00:00 -0500</pubDate>
				<guid>https://workyoucanexplain.com/posts/use-agents-md-to-teach-an-ai-about-a-repository/</guid>
				<description>&lt;p&gt;Use &lt;code&gt;AGENTS.md&lt;/code&gt; for durable guidance that should apply across many agent tasks in&#xA;a repository. Put project conventions, reliable setup and verification commands,&#xA;scope boundaries, and review expectations there. Keep the current objective,&#xA;temporary context, and one-time preferences in the task prompt.&lt;/p&gt;&#xA;&lt;p&gt;OpenAI&amp;rsquo;s current&#xA;&lt;a href=&#34;https://learn.chatgpt.com/docs/agent-configuration/agents-md&#34;&gt;&lt;code&gt;AGENTS.md&lt;/code&gt; documentation&lt;/a&gt;&#xA;explains that Codex reads instruction files before working. Instructions closer&#xA;to the current directory take precedence over broader repository guidance, and&#xA;an &lt;code&gt;AGENTS.override.md&lt;/code&gt; file can replace an &lt;code&gt;AGENTS.md&lt;/code&gt; file at the same level.&#xA;Confirm the files Codex actually loaded before relying on those rules.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
