<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Prompt Design on Top AI Skills</title><link>https://topaiskills.com/tags/prompt-design/</link><description>Recent content in Prompt Design on Top AI Skills</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 28 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://topaiskills.com/tags/prompt-design/index.xml" rel="self" type="application/rss+xml"/><item><title>writing-for-agents: How to Write Docs Agents Actually Read</title><link>https://topaiskills.com/skills/writing/writing-for-agents/</link><pubDate>Fri, 28 Aug 2026 00:00:00 +0000</pubDate><guid>https://topaiskills.com/skills/writing/writing-for-agents/</guid><description>&lt;p&gt;Your agent skips half of &lt;code&gt;AGENTS.md&lt;/code&gt; and still follows a 40-line skill to the letter. The difference is writing, not packaging. Matt Pocock&amp;rsquo;s &lt;code&gt;writing-for-agents&lt;/code&gt; skill (158,238 installs, #263 on the skills.sh all-time board) is the reference document behind that difference — it codifies how to write any file an agent consumes: skills, &lt;code&gt;AGENTS.md&lt;/code&gt;, &lt;code&gt;CLAUDE.md&lt;/code&gt;, or a doc reached by a pointer. I read its 81-line SKILL.md plus SKILL-MECHANICS.md and scraped the live leaderboard on 2026-08-28. What surprised me: the file never mentions output format. It teaches one idea — an agent reads what the &lt;em&gt;wording&lt;/em&gt; makes reachable, not what you intended to say.&lt;/p&gt;</description></item></channel></rss>