推文

@kasong2048 · 2026-10-14 10:52

There are mature open-source skill workflows out there. Is it still worth building your own? 2 facts: 1. Skills are written in natural language, so their quality is hard to measure and improve. 2. You'll definitely hit business cases open-source workflows can't cover. Given 1, how do you judge a workflow's quality? Usage is the best signal. Skills lots of people use are usually better. So pick a widely used open-source workflow instead of building your own. Once you've picked one, start reworking it. Easiest first step: if the skill is in English and English isn't your native language, rewrite it in your own. What about when the open-source skill ships a new version? Have your agent compare it with your reworked version, figure out the thinking behind the new features, then add them to your skill. This deliberate, step-by-step reworking is how you learn to design skills. By the time you hit a case the open-source workflow can't handle, all these tedious-looking steps will have taught you how to design good skills, and you can build a workflow for the new case without breaking a sweat.

曝光 38 · 评论 0 · 点赞 0 · 书签 0