<?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>Skill on KbWen Blog</title>
    <link>https://www.kbwen.com/tags/skill/</link>
    <description>Recent content in Skill on KbWen Blog</description>
    <image>
      <title>KbWen Blog</title>
      <url>https://www.kbwen.com/images/og-default.png</url>
      <link>https://www.kbwen.com/images/og-default.png</link>
    </image>
    <generator>Hugo</generator>
    <language>zh-TW</language>
    <lastBuildDate>Thu, 16 Apr 2026 00:00:00 +0800</lastBuildDate>
    <atom:link href="https://www.kbwen.com/tags/skill/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What Makes an AI Skill Different from a Prompt?</title>
      <link>https://www.kbwen.com/what-makes-an-ai-skill-different-from-a-prompt/</link>
      <pubDate>Thu, 16 Apr 2026 00:00:00 +0800</pubDate>
      <guid>https://www.kbwen.com/what-makes-an-ai-skill-different-from-a-prompt/</guid>
      <description>Most teams treat AI skills as saved prompt templates. They&amp;#39;re not. A proper Skill is a capability contract—with input schemas, tool bindings, validation, and retry logic. Here&amp;#39;s what that distinction means for production system design.</description>
    </item>
  </channel>
</rss>
