skills is one of those tools that generates strong opinions—both positive and negative. After using it for real work, I understand why. The nuanced take is below.
The free tier of skills is genuinely useful for solo developers. You can do real coding—fix bugs, write tests, generate boilerplate—without paying. The paid plan unlocks team features, faster models, and higher limits, which matter for professional use but are not essential for learning or side projects.
What keeps me paying: the compound productivity effect. Each day I save 20-30 minutes on routine coding. Over a month, that is 10+ hours. At any reasonable hourly rate, the subscription pays for itself in the first week.
For specific languages and frameworks, quality is uneven. The AI is excellent at Python, TypeScript, and React. It is decent at Go, Rust, and Java. For niche frameworks like Phoenix (Elixir) or Rocket (Rust), suggestions are often incomplete or use outdated patterns. If you work primarily in a less popular stack, test thoroughly before subscribing.
Mobile development support is limited. The AI helps with logic but struggles with platform-specific APIs and layout code. For Swift/Android development, you will still write most of the UI code yourself.
Pricing transparency: skills has clear tiers on the pricing page. The free tier limits are documented (though you have to scroll). The jump from free to paid is about 10-20/month.
If you are a student or nonprofit, check for discounts. Many AI tools offer 50% off or free access for educational use that is not prominently advertised.
Who skills is for: developers who need a reliable open-source LLM and are willing to invest time in learning it properly. The learning curve is moderate—budget a week to find your workflow—but the payoff is consistent, high-quality output.
Who should look elsewhere: people who need a tool that works perfectly out of the box with zero configuration. skills rewards setup and customization. If you want plug-and-play simplicity, a simpler alternative may be a better fit.
skills earned its spot in my paid subscription list. That list is short—I cancel tools aggressively. The criteria: does it save me more time than it costs, and do I reach for it without thinking. skills passes both tests.
Rating: 3/5. Not a perfect score because no tool is perfect, but it is the score I would give if a colleague asked "should I try this?" and I had 30 seconds to answer.
If you only subscribe to one open source llm tool, make it this one—with the understanding that it covers 80% of what you need and you will supplement the other 20% with free alternatives or manual work.
The honest take on skills after daily use: it is good at the things it was designed for, mediocre at everything else. The marketing copy oversells. I keep it open for the 2-3 specific tasks where it shines and switch to other tools for the rest. That setup is where skills pays for itself.
I've been testing and reviewing AI tools for 2+ years. I run saas.pet as a side project while working as a software engineer. I buy every subscription I review. No vendor pitches, no free accounts. If a tool is in my rotation, I pay for it.
💬 Discussion
Have you used skills? Share your experience. Real comments are featured on the homepage each week.