Launched this week
Skillbox
One library for your AI skills, synced to every agent
279 followers
One library for your AI skills, synced to every agent
279 followers
Skillbox keeps your AI skills in one library and syncs them to Claude Code, Cursor and Codex. Follow GitHub sources, review diffs, and scan each version for prompt injection. Trim shortens noisy command output so sessions last longer.





Free Options
Launch Team / Built With

TinesThe single, secure environment for agents, apps, and automations.
Promoted

We publish skills for coding agents, and besides the skill files, each agent wants the MCP server the skills use declared in its own way: Claude Code with "type": "http", Cursor with just the address, Codex with "streamable-http" in an mcp.json.
Does Skillbox carry a skill's server entry across tools, or only the skill files?
Thanks for the comment, @philippstaudt not today. Skillbox syncs a skill’s files to each tool, but it doesn’t carry the skill’s MCP server entry across tools.
The only MCP config Skillbox writes is its own control-plane server, “skillbox”. It writes that one in each tool’s own format: "type": "http" for Cursor and Claude Code, a [mcp_servers.skillbox] TOML table for Codex, and so on. It doesn’t read a server declaration from a skill and write it out for each tool. The docs also treat MCP install as separate from file delivery.
So for now, keep documenting the per-tool server setup in the skill’s README or SKILL.md. A skill-level server declaration that Skillbox translates per tool would be a new feature, not something it already does.