Agent Skills: Why They Matter More Than You Think

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3864419) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Rian O'Leary Posted on Apr 28 Agent Skills: Why They Matter More Than You Think #ai #opensource #agentskills #programming The biggest change in AI this year isn't a new model. So what is it, and how can you take advantage of it? Every time a major AI company has announced a product in the last six months, there's been a feature buried in the announcement that nobody in the tech press seems to have noticed. In October, Anthropic published an engineering blog post describing a new architecture for giving AI agents installable, reusable capabilities. The headline coverage was about Claude getting better at specialised tasks. But buried underneath was the actual news: Anthropic had just created a standard that would let any AI agent, on any platform, load permanent new capabilities. By December 2025, Anthropic had open-sourced it. Within weeks, OpenAI had adopted it for Codex and ChatGPT, GitHub Copilot had added it to VS Code, and Vercel had built an entire distribution layer for it, which is now quietly doing a quarter of a million installs a week. Anthropic called these shippable capabilities "agent skills". And it's the most important architectural shift in how AI gets used since OpenAI's ChatGPT release in 2022. This post covers what a skill is, why the change matters more than it sounds, how fast the market around it has formed, and how to install your first one this afternoon. What a Skill Actually Is It's easiest to think about a skill as an app for your agent. In the same way you download an app for your phone on a marketplace (the app store), your agent can now install its own app (a skill) through a dedicated skill marketplace/registry (ClawHub). Mechanically, a skill is a small bundle of files. It usually includes a text file called SKILL.md that tells the agent what the skill does, when to use it, and how it works. Some skills are just detailed instructions while others include code the agent can run, an API the agent can call, or a set of rules for handling specific kinds of input. A skill for reading invoices might include a Python script that parses PDFs. A skill for calendar management might include the logic for connecting to Google Calendar, checking your availability, and proposing meeting slots. A skill for summarising Slack threads might be detailed instructions on how to read a thread and produce a clean summary of your conversations. Skills live in registries. The biggest public one is ClawHub, which currently hosts over 52,000 of them. When you install a skill from ClawHub, its files get added to a folder your agent reads from. The next time the agent is doing work and encounters a task the skill covers, it uses it. Why the Architectural Change Matters Before skills, an AI agent's capabilities were functionally fixed at whatever the model had been trained on, plus whatever you explained to it in the moment. If you wanted it to handle your invoicing, you had to write a careful prompt describing your invoice format, your accounting categories, where things should be filed, and how to handle edge cases. You had to do that every session, because the model forgot everything between conversations. If you wanted a…

This excerpt is published under fair use for community discussion. Read the full article at DEV Community.