There's apparently a bit of mess regarding intersection of what options you have enabled on your account (as in, workspace license) and country availability
Ha yes. I just spent 36 Australian dollars upgrading myself on our workspace account.... now I have a model called "Carbon", I still have "Hydrogen" but not "Neon".
Ever worked in a big company where internal nomenclature becomes an obstacle for external participation? This is that.
And this product launch is a failed activation for me
Looking at the comments here it's clear that there's a lack of understanding about what skills fundamentally are, they're process or procedure.
The latest frontier models exhibit good process that was trained into them during the RL phase, and whilst that might make them massively more capable in terms of one-shot, or general coding ability, models without skills simply don't have a durable process.
If you have a need for procedure in your use of agents, you absolutely need skills like this. I'm not commenting on the relative merits of this or superpowers, but rather the seemingly religious debate, "skills are good" vs "skills are bad" discussion that keeps coming up.
Most of the comments here seem to focus on specific things people were trying to get out of skills, and whether those are still needed.
That is going to vary a lot.
If your goal with something like superpowers was to have a process that made your model work "properly" on tasks, sure that's probably not needed anymore.
If your goal with something like superpowers was to get a consistent set of artifacts alongside what was developed (quality varying, so i mean consistent here as "one design plan, one implementation plan", not "good"), nothing has changed, models do not do this consistently, in a durable fashion, without something telling them to do this.
Yes, for example, newer Opus will often decide to write a spec. But not always, and not with any consistent format or ...
If you want that to happen, you'd still need a skill making it happen.
If you don't care about that, then sure, you don't need the skill anymore.
People seem to have used various skills to achieve different things, and so have wildly different views on what is still necessary.
I think I don't understand what you mean by process. I just tell the LLM what process I want it to follow, e.g. follow the plan document, use cheaper subagents when appropriate, respond to PR comments before merging, etc. It's usually a short paragraph.
I do use skills for other things, I don't believe that skills are bad. I'm just not sure what they add in this case.
They're about half a gen behind. Very impressive to get this kind of utility from a flash series model... the impact of RL seems to be behind much of the coding and agentic improvements lately.
Can I ask what kind of tooling you use around the model and for the UI layer? I’ve been looking for a well designed knowledge work harness to give nontechnical users but I haven’t really found one that I like. (I personally just use coding harness for this stuff, but that’s a poor fit for non-devs.)
I started using it last week when copilot started acting up against the Deepseek models. It's fast, solid, I love the architecture but be warned: it submits very very many input tokens against the LLM endpoint, so robust & cheap token caching is a must.
Hello, apologies for the self-promotion but I’m building a tool called Radix which is a knowledge work harness. Please email or message me if you would like to give it a try for free instead of paying the subscription price.
I can’t speak for your tool, but I wanted to appreciate your privacy page
https://radix-os.com/privacy
It points out concrete details (e.g. “where on my Mac does your folder live?”), it is comprehensive and understandable for a layperson. Kudos!
reply