3 ms·
i see it as skills being logical grouping of a set of prompts, which achieve a goal. Like my optimize-critical-path skill. It's more than a single prompt, but
by ryanthedev 9mo ago
i see it as skills being logical grouping of a set of prompts, which achieve a goal. Like my optimize-critical-path skill.
It's more than a single prompt, but less than an entire agent. I find skills to be the tools you use on the fly. Like how I might have a wrench,screw-driver, hammer in my tool box.
tools vs skills is all about context efficiency from what I see. and yes, this isn't novel of claude. but they are the first to offer this abstraction.
- oooyay 9mo ago> they are the first to offer this abstraction. My point is that Skills are not the first to do this. Well written MCPs are dynamic workflow engines. Skills are like a more user focused and slimmed down version of MCPs. It'd be interesting to see a comparison of a well written MCP compared to a skill in terms of task competency.
- ryanthedev 9mo agoAhhhh. I see now. Now that you mention it, i can see a future where claude may offer a "skills" feature and codex offers a "talent" feature. where they are essentially the same things, but specific to that vendor. reminds me how each cloud has the same offerings but different products.
- joshuacc 9mo agoCodex added skills support recently. It appears to work exactly the same as Claude Code.
- ryanthedev 9mo agoohhh! I'm gonna have to try that out. Thankfully everybody is still playing nice hahah!