Shipped Clients Turn Skills Over MCP into a Real Delivery Seam

·https://x.com/mxstbr/status/2092681822551544246?s=46&t=uRyCCtjktRI5TQXbSKdTLw
articleaimcpagent-skillsskill-distributionauthorizationfitness-devcodexchatgpt

fitness.dev can deliver its workflow skills through the same MCP connection as its tools while keeping canon and authorization as separate contracts.

Max Stoiber says OpenAI has shipped early Skills over MCP support in ChatGPT and Codex. SEP-2640 is still in review, but the delivery path is no longer draft-only speculation. An MCP server can keep its skills beside its tools, and supported clients can consume both through one connection.

The clever part is what this does not combine. Agent Skills remain the canonical workflow format. MCP Resources provide transport and discovery. Authorization still decides who can run tools, execute scripts, or mutate data. Keeping those contracts separate means the transport can change without rewriting the canon or quietly expanding trust.

For fitness.dev, this changes the seam described in MCP Servers Can Ship Their Own Operating Manuals. The service can ship current workflow instructions with its MCP tools instead of asking users to install and update a second package. Product support makes the distribution model usable now; it does not make remote instructions inherently authorized.

Key Ideas

  • OpenAI has shipped early Skills over MCP support in ChatGPT and Codex, according to Max Stoiber.
  • SEP-2640 binds the existing Agent Skills specification to MCP Resources; it does not define a second skill format.
  • Co-locating skills with an MCP server lets the server owner update tools and their operating instructions together.
  • A shipped client turns a protocol proposal into a usable product seam even while the underlying specification remains in review.
  • Workflow canon, skill delivery, and tool authorization are separate contracts; combining their installation path should not combine their trust boundaries.
  • fitness.dev can use one MCP connection for tools and current workflow instructions without making transport responsible for policy.

Links

← All discoveries