Skills, plugins, apps, connectors, MCPs, agents - anyone else getting a bit lost?
They’re all bandaids
Skills Officially Comes to Codex
41–50 of 133 posts
Re: Skills Officially Comes to Codex
#42Re: Skills Officially Comes to Codex
#43Yes! I was raving about Claude Skills a few days ago (vide https://quesma.com/blog/claude-skills-not-antigravity/ ), and excited they come to Codex as well!
Thanks for that! You mentioned Antigravity seemed slow, I just started playing with it too (but not really given it a good go yet to really evaluate) but I had the model set to Gemini Flash, maybe you get a speed up if you do that?
That said, for many tasks (summaries and data extraction) I do use Gemini 2.5 Flash, as it cheap and fast. So excited to try Gemini 3 Flash as well.
Re: Skills Officially Comes to Codex
#44Earlier quoted context omitted.
It's like JS frameworks. Just wait until a React emerges and get up to speed with that later.
React itself took a few years for react to decide how it should work (hooks not classes etc).
Re: Skills Officially Comes to Codex
#45Earlier quoted context omitted.
Perhaps you could help me. I'm having a hard time figuring out how could I leverage skills in a medium size web application project. It's python, PostgreSQL, Django. Thanks in advance. I wonder if skills are more useful for non crud-like projects. Maybe data science and DevOps.
Skills are the matrix scene where neo learns kungfu. Imagine they are a database of specialized knowledge that can an agent can instantly tap into _on demand_. The key here is “on demand”. Not every agent or convention needs to know kung fu. But when they do, a skill is waiting to be consumed. This basic idea is “progressive disclosure” and it composes nicely to keep context windows focused. Eg i have a metabase skil…
Re: Skills Officially Comes to Codex
#46What are your favourite skills?
I do also like to make skills on things that are more niche tools, like marimo (a very nice jupyter replacement). The model probably does known some stuff about it, but not enough, and the agent could find enough online or in context7, but it will waste a lot of time and context in figuring it out every time. So instead I will have a deep thinking agent do all that research up front and build a skill for it, and I might customize it to be more specific to my environment, but it's mostly the condensed research of the agent so that I don't need to redo that every time.
Re: Skills Officially Comes to Codex
#47Re: Skills Officially Comes to Codex
#48This is great. At my startup, we have a mix of Codex/CC users so having a common set of skills we can all use for building is exciting. It’s also interesting to see how instead of a plan mode like CC, Codex is implementing planning as a skill.
I’m probably missing it, but I don’t see how you can share skills across agents, other than maybe symlinking .claude/skills and .codex/skills to the same place?
Re: Skills Officially Comes to Codex
#49If there was a marketplace or directory of skills.md files that were ranked with comments, it would be a good idea for the propagating of this tech
Re: Skills Officially Comes to Codex
#50If there was a marketplace or directory of skills.md files that were ranked with comments, it would be a good idea for the propagating of this tech
it feels like people keep attempting this idea, largely because its easy to build, but in practice people aren't interested using others' prompts because the cost to create a customized skill/gpt/prompt/whatever is near zero
More like a gallery than a marketplace