<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>AI Agents on Shin Li</title><link>https://shin13.github.io/tags/ai-agents/</link><description>Recent content in AI Agents on Shin Li</description><generator>Hugo</generator><language>en-US</language><copyright>Shin Li</copyright><lastBuildDate>Wed, 13 May 2026 13:08:20 +0800</lastBuildDate><atom:link href="https://shin13.github.io/tags/ai-agents/index.xml" rel="self" type="application/rss+xml"/><item><title>The 7 Skills You Need to Build AI Agents</title><link>https://shin13.github.io/notes/the-7-skills-you-need-to-build-ai-agents/</link><pubDate>Wed, 13 May 2026 10:42:46 +0800</pubDate><guid>https://shin13.github.io/notes/the-7-skills-you-need-to-build-ai-agents/</guid><description>&lt;p&gt;IBM Technology&amp;rsquo;s &lt;em&gt;The 7 Skills You Need to Build AI Agents&lt;/em&gt; makes a point that feels increasingly true: if an agent can act in the real world, then prompt writing is only the starting point.&lt;/p&gt;</description></item><item><title>[Dev] Following a Goal with Codex (/goal)</title><link>https://shin13.github.io/notes/following-a-goal-with-codex/</link><pubDate>Tue, 12 May 2026 06:00:00 +0800</pubDate><guid>https://shin13.github.io/notes/following-a-goal-with-codex/</guid><description>&lt;p&gt;I have been looking for a clean way to explain what &lt;code&gt;/goal&lt;/code&gt; really does in Codex.&lt;/p&gt;
&lt;p&gt;The most useful mental model I found is simple: &lt;code&gt;/goal&lt;/code&gt; is not a prettier prompt. It is a working contract for long-running agent work. You are telling the agent what success looks like, what the boundary is, and how to know when to stop.&lt;/p&gt;
&lt;p&gt;That framing matters because the feature is built for work that outlives one turn. If the objective is durable enough, the agent can keep making progress, validate its own steps, and come back to you with a result instead of a half-finished thought.&lt;/p&gt;</description></item><item><title>[Dev] Learning from Matt Pocock’s Agent Skills</title><link>https://shin13.github.io/notes/learning-from-matt-pocock-agent-skills/</link><pubDate>Thu, 07 May 2026 08:53:00 +0800</pubDate><guid>https://shin13.github.io/notes/learning-from-matt-pocock-agent-skills/</guid><description>&lt;p&gt;I recently read Matt Pocock’s article, &lt;a href="https://www.aihero.dev/5-agent-skills-i-use-every-day"&gt;“5 Agent Skills I Use Every Day”&lt;/a&gt;. It resonated with my experience using coding agents such as Claude Sonnet and Claude Opus.&lt;/p&gt;
&lt;p&gt;The article gave me a clearer language for something I have been feeling: good agent work depends on good engineering process. We need better questions, written context, small slices, tests, and codebases that agents can understand.&lt;/p&gt;</description></item></channel></rss>