Post

I want portable skills. Fine. Seventy platforms is a press release until one skill fires the same way in Claude Code, Copilot and Cursor. Name what fired in each one. Then I'll cheer.

The folder is portable. Whether it fires is the tool's call. Instructions travel, scripts don't. A script inherits the harness's permission model, so the same skill loads in all three and stalls in one. When porting I watch what gets read and what's allowed to run, not just that it loads.

Shared Spring conventions could become a team's memory rather than a prompt everyone rewrites. I'd be interested in how teams test that the same skill produces comparable results across different coding agents.

Really nice to see Agent Skills land next to MCP — that shared home should stop every platform inventing its own glue. Your Spring example says it plainly: one skill working in Claude Code, Copilot and Cursor is exactly the portability people have been waiting for.

Worth keeping the skill small and pinning down the conventions that are easy to check, like naming and test layout. Vague guidance tends to get interpreted differently by each agent, so concrete rules should carry over better.

Nice that one skill file works across all of them. Keeping it short and adding a couple of real examples from your own codebase helps the agents actually follow it.