[{"data":1,"prerenderedAt":357},["ShallowReactive",2],{"article-skill-vs-mcp":3},{"id":4,"title":5,"body":6,"cover":67,"date":319,"description":320,"draft":321,"extension":322,"faq":323,"featured":321,"meta":336,"navigation":337,"path":338,"readingTime":339,"seo":340,"seoKeywords":341,"stem":349,"summary":15,"tags":350,"type":354,"updated":355,"video":355,"__hash__":356},"articles\u002Farticles\u002Fskill-vs-mcp.md","我用 Skill 做出了自己的 AI 分身，MCP 做不到这个",{"type":7,"value":8,"toc":304},"minimark",[9,16,21,24,31,37,44,50,55,61,68,73,76,79,84,90,97,110,116,122,125,129,136,142,145,149,152,178,184,190,193,196,201,207,213,218,220,224,230,233,244,247,258,264,275,280,286,290,296,299,301],[10,11,12],"blockquote",{},[13,14,15],"p",{},"MCP 只是给 AI 一个工具，Skill 则给 AI 一整套人设+工具+流程+素材。当 AI 需要理解业务逻辑而非简单调用接口时，Skill 才是正确答案。",[17,18,20],"h2",{"id":19},"怎么一直有人在问我要数据","怎么一直有人在问我要数据！",[13,22,23],{},"我们团队有一个后端系统。最近，我发现自己被\"数据需求\"淹没了。",[13,25,26,30],{},[27,28,29],"strong",{},"同事 A："," \"嘿，我需要最近 30 天登录用户的年龄分布，按地区分组。\"",[13,32,33,36],{},[27,34,35],{},"我："," \"好的，我查一下...不过需求有点复杂，给我一小时。\"",[13,38,39,43],{},[40,41,42],"em",{},"（1 小时后）"," 数据给了，但同事提出新问题...",[13,45,46,49],{},[27,47,48],{},"同事 B："," \"对了，能不能也看看用户留存率的趋势？\"",[13,51,52,54],{},[27,53,35],{}," \"又来？...\"",[13,56,57,58],{},"这样的对话每天都在上演。每次都是我手工写 SQL、加工数据、发回去。",[27,59,60],{},"我发现自己把大量时间花在\"翻译需求 → 查询数据\"这种重复劳动上，根本没有时间做更重要的事。",[13,62,63],{},[64,65],"img",{"alt":66,"src":67},"数据需求困境","\u002Fa\u002Fskill-vs-mcp\u002Fdata-overwhelm.png",[69,70,72],"h3",{"id":71},"不是有-ai-吗试试-mcp","不是有 AI 吗，试试 MCP？",[13,74,75],{},"我记得之前用过 MCP（Model Context Protocol）。我想，能不能用 MCP 让 AI 来做这件事？",[13,77,78],{},"我给 AI 定义了一个\"调用数据库查询接口\"的工具。理论上，别人可以问 AI 数据问题，AI 会自动调用这个工具。",[13,80,81],{},[27,82,83],{},"结果呢？",[13,85,86,89],{},[27,87,88],{},"同事再问一次："," \"帮我查用户年龄分布。\"",[13,91,92,93,96],{},"AI 调用了工具，但还是返回了错误的结果。因为 ",[27,94,95],{},"AI 不知道","：",[98,99,100,104,107],"ul",{},[101,102,103],"li",{},"不同表，不同字段可以怎么配合使用",[101,105,106],{},"同事每次的需求差别很大，怎么组合查询才能满足不同场景",[101,108,109],{},"怎么二次加工数据才能符合需求",[13,111,112,115],{},[27,113,114],{},"每次 AI 都需要我手工\"教\"它。"," 相当于没解决问题，反而多了一个中间环节。",[13,117,118],{},[64,119],{"alt":120,"src":121},"MCP 的局限","\u002Fa\u002Fskill-vs-mcp\u002Fmcp-limitation.png",[123,124],"hr",{},[17,126,128],{"id":127},"我为什么转而制作自己的-skill","我为什么转而制作自己的 Skill？",[13,130,131,132,135],{},"就在我快放弃的时候，我发现了 ",[27,133,134],{},"Agent Skills","。",[13,137,138,139,135],{},"和 MCP 不同，Skill 不只是定义一个工具，而是定义一整套 ",[27,140,141],{},"工作流程和人设",[13,143,144],{},"我决定试试，给这个\"数据查询\"的事制作一个 Skill。",[69,146,148],{"id":147},"skill-里我做了什么","Skill 里我做了什么？",[13,150,151],{},"就像写一个标准的文章创作流程一样，我在这个 Skill 里定义了：",[98,153,154,160,166,172],{},[101,155,156,159],{},[27,157,158],{},"我是谁？"," 这个 Agent 是一个\"数据分析专家\"，理解我们的业务逻辑",[101,161,162,165],{},[27,163,164],{},"我怎么做事？"," 我定义了常见的数据查询场景、加工规则、输出格式",[101,167,168,171],{},[27,169,170],{},"我有什么工具？"," 我给了它调用后端 API 的脚本",[101,173,174,177],{},[27,175,176],{},"我有什么素材？"," 我给了它数据字典、模版文件、素材资料",[13,179,180],{},[64,181],{"alt":182,"src":183},"Skill 的四层架构","\u002Fa\u002Fskill-vs-mcp\u002Fskill-architecture.png",[13,185,186,187],{},"简单说： ",[27,188,189],{},"我不仅给了 AI 一个人设，还给了它一组工具和使用说明书，甚至还定义了完成工作的流程。",[69,191,192],{"id":192},"神奇的事发生了",[13,194,195],{},"现在同事直接问我的 AI Agent：",[13,197,198,200],{},[27,199,29],{}," \"最近 30 天登录用户的年龄分布，按地区分组。\"",[13,202,203,206],{},[27,204,205],{},"AI Agent："," 通过技能和流程，加工数据后，返回正确的结果。",[13,208,209,210],{},"没有错误，没有\"需要教它\"的过程。 ",[27,211,212],{},"因为 Agent 已经\"知道\"可以上手什么工具，手搓代码解决需求了。",[13,214,215],{},[27,216,217],{},"我的数据运营工作彻底解放了。",[123,219],{},[17,221,223],{"id":222},"这篇文章真是用-skill-写出来的吗","这篇文章真是用 Skill 写出来的吗？",[13,225,226,227],{},"有趣的是，",[27,228,229],{},"这篇文章本身就是用我自己制作的公众号文章 Skill 写出来的。",[13,231,232],{},"我之前写文章特别低效：",[98,234,235,238,241],{},[101,236,237],{},"一个人想选题，想半天",[101,239,240],{},"写框架时要反复调整",[101,242,243],{},"正文写到一半又要改思路",[13,245,246],{},"所以我制作了一个公众号文章创作 Skill，定义了整个微信文章的创作流程：",[98,248,249,252,255],{},[101,250,251],{},"如何分析读者和选题",[101,253,254],{},"如何梳理论点、设计框架",[101,256,257],{},"如何撰写正文、调整节奏",[13,259,260,261,96],{},"现在，",[27,262,263],{},"我和这个 AI Agent 一起写文章",[98,265,266,269,272],{},[101,267,268],{},"我提出想法 → Agent 帮我梳理框架",[101,270,271],{},"Agent 提出角度 → 我选择或反驳",[101,273,274],{},"Agent 生成初稿 → 我快速审阅调整",[13,276,277],{},[27,278,279],{},"效率提升 3-5 倍，质量还更好。",[13,281,282],{},[64,283],{"alt":284,"src":285},"文章创作协作流程","\u002Fa\u002Fskill-vs-mcp\u002Fwriting-workflow.png",[69,287,289],{"id":288},"这才是释放-ai-潜力的方式","这才是释放 AI 潜力的方式",[13,291,292,293],{},"2026 年，AI Agent 产品为什么出现？",[27,294,295],{},"因为 AI 不再只活在对话框里，而是开始成为能实际干活的 Agent。",[13,297,298],{},"而 Skill，就是让每个人都能为自己的工作打造一个 AI Agent。",[123,300],{},[13,302,303],{},"最后，你工作中有什么繁琐重复的事，可以交给 AI Agent 去做吗？",{"title":305,"searchDepth":306,"depth":306,"links":307},"",3,[308,312,316],{"id":19,"depth":309,"text":20,"children":310},2,[311],{"id":71,"depth":306,"text":72},{"id":127,"depth":309,"text":128,"children":313},[314,315],{"id":147,"depth":306,"text":148},{"id":192,"depth":306,"text":192},{"id":222,"depth":309,"text":223,"children":317},[318],{"id":288,"depth":306,"text":289},"2026-02-11","对比 MCP 和 Agent Skills 的差异：Skill 通过人设+工具+流程+素材四层架构，解决 MCP 解决不了的复杂场景",false,"md",[324,327,330,333],{"q":325,"a":326},"MCP 和 Agent Skill 有什么本质区别？","MCP 只定义了一个工具接口，AI 知道怎么调用但不知道何时、为什么调用。Skill 则定义了完整的四层架构：人设（AI 是什么角色）、流程（怎么做事）、工具（用什么）、素材（参考什么）。相当于 MCP 只给了一把锤子，Skill 给了一个懂装修的师傅。",{"q":328,"a":329},"什么场景适合用 Skill 而不是 MCP？","当任务涉及业务理解、多步骤流程、动态判断时，Skill 远优于 MCP。比如数据查询需要理解不同表和字段的组合方式，文章创作需要遵循特定的写作流程。简单说：一次性调用用 MCP，需要'懂行'的复杂任务用 Skill。",{"q":331,"a":332},"Agent Skill 的四层架构具体包含什么？","四层分别是：1）人设——定义 Agent 是什么角色，理解什么业务；2）流程——定义常见场景的处理步骤、加工规则、输出格式；3）工具——提供可调用的脚本和 API 接口；4）素材——附带数据字典、模版文件、参考资料。这四层让 AI 不只是有工具，还知道何时、为何、怎样使用工具。",{"q":334,"a":335},"普通人可以自己制作 Skill 吗？","完全可以。Skill 的本质是把你的工作流程和专业知识结构化地写下来，让 AI 按照你的方式做事。比如作者就用 Skill 搞定了数据运营工作，还制作了公众号文章创作 Skill。只要你能把自己做事的方法说清楚，就能做成一个 Skill。",{},true,"\u002Farticles\u002Fskill-vs-mcp",10,{"title":5,"description":320},[342,343,344,345,346,347,348],"Agent Skill vs MCP","AI Agent 开发","MCP 局限性","AI 工作流","AI 自动化","Agent 人设","AI 分身","articles\u002Fskill-vs-mcp",[351,352,353],"AI 洞察","AI 应用","产品思考","article",null,"13k0p4ig7SoI2ui_ZS-3X-MkrYEUeB7FVBiiIELCZbA",1782881825200]