Skills Over MCP

Describe what you need.

The right skill runs.

Skills are step-by-step agent workflows served as MCP resources.<br>Type your intent below and an LLM routes you to the matching skill,<br>then walks you through it with live tool execution.

SEP-2640 Spec<br>Interest Group<br>This repo

Why skills, not just tools?

Discovery. tools/list returns full schemas for every tool, all loaded into context at once. There is no tools/read. Resources have a two-step fetch: resources/list returns lightweight metadata, then resources/read loads one on demand.

tools/list = [full schema A, B, C, ...] // all in context<br>resources/list = [name A, name B, name C, ...] // just the index<br>resources/read = full content of A // one at a time<br>Wouldn't tool search or progressive loading solve this? That fixes the discovery problem (finding the right tool). But skills solve a different problem: process knowledge.

A tool says create_branch(name). A skill says:

Name it /-

Always branch from main unless the ticket says otherwise

Run run_tests before pushing

If integration tests fail but your change is frontend-only, that's acceptable

Open a PR using this specific template

That's team knowledge. Even with perfect tool discovery, the agent needs to know how your team uses those tools together . Tools are the verbs. Skills are the playbook.

Transport

Streamable HTTP

Router

Llama 4 Scout

Skills

Tools

Timeline

2025-12-20

Skills and MCP, Better Together blog post

2025-12-22

RFC: Remote Agent Skills, URL-based Skill Import

2026-02-01

MCP Interest Group formed; experimental repo created

2026-04-14

Initial charter formalized by MCP via SEP-2149

Create branch<br>Code review<br>Deploy service

Activity