Introducing Skills Over MCP – the better way to share and distribute skills

A new Skills charter is rolling out. Sharing them is still a mess.

Anthropic's new Skills charter is the best packaging format Claude has had so
far. A folder, a SKILL.md, maybe some supporting files, a client that knows
how to load them. Clean.

The thing nobody's solved yet: how do you actually share a skill with someone?

Today the answer is, you don't. You copy folders around, paste .claude/skills/
between projects, fork someone's repo and forget which version you forked. I've
been doing the copy-paste dance for months. It's dumb.

So I built the distribution layer I wanted.

Skills Over MCP

Skills Over MCP takes a public GitHub repo full of
SKILL.md files and serves it as a remote MCP server. You get a personal URL.
Anyone you hand it to can mount your whole pack with one line of config.

No hosting, no build step. The repo is the source of truth. Push to GitHub, the
server updates.

It works in Claude Code, Cursor, and Claude Desktop today, anything that speaks
MCP. You don't have to wait for the charter to land in your client. When it
does, the SKILL.md files you already shipped keep working.

Setup, about 30 seconds

Public GitHub repo. One folder per skill, each with a SKILL.md.
Connect it at skillsovermc
Drop it into your client config:

{
  "mcpServers": {
    "my-skills": {
      "url": "https://skillsovermcp.com/your-handle/skills"
    }
  }
}

Skills show up as skill_<nameserver picks it up.

What's already up there

I seeded the catalog with my

50+ marketing skills (SEO a, email sequences, customerresearch)
A few dev utilities I use d_grill_me (interview your ownplan until it falls over), skill_triage_bug, skill_write_like_a_human

Fork any of them, edit, point your MCP URL at the fork. Done.

Why publish a pack this week

The packs that go up early get copied. That's how awesome-* repos worked in