I don't understand MCP still? What can MCP do that a skill + cli can't? I've been using hax (<a href="https://usehax.dev" rel="nofollow">https://usehax.dev) and haven't missed skills at all to be honest.
As a provider, I can add a tool or change instructions on my MCP server, and you'll get it on your next connection, sometimes even mid-session.
With a skill, updates depend on whatever channel delivered it to you. Whichever channel that is, it's out of my hands as a provider.
So, MCP solves the problem of coordinated distribution of updates to a larger subscriber base. Think inside of a company, for example. I don't have to go around and tell people to `git pull` their skills folder.
Because why should you have to load "here's how to update this skill!" information into the context window every time you use it? Would you expect the agent to go to that URL and look for more recent skill files every time you use it? Is this a real question?
Nothing says that agents can't read skills, interpret them and fetch stuff. Needing to agent to pass things off to powerful LLMs to interpret doesn't have to be done for everything.
CamilleScholtz · · focus · HN ↗
fnordsensei · · focus · HN ↗
With a skill, updates depend on whatever channel delivered it to you. Whichever channel that is, it's out of my hands as a provider.
So, MCP solves the problem of coordinated distribution of updates to a larger subscriber base. Think inside of a company, for example. I don't have to go around and tell people to `git pull` their skills folder.
charcircuit · · focus · HN ↗
jun_lung · · focus · HN ↗
charcircuit · · focus · HN ↗
newtwilly · · focus · HN ↗
charcircuit · · focus · HN ↗