Platform compatibility
Nuclexa packages target one open format, but each platform consumes them slightly differently — some install in place, others export to a tool's native file. A package declares its supported platforms in the platforms field of agent.json, which drives the compatibility table shown on its page.
Supported platforms
| Platform | How it's consumed | Lands at | Method |
|---|---|---|---|
| Claude Code | Skill / agent | .claude/skills/[slug] | install |
| Claude Desktop | Desktop skill / MCP server | per-OS path (detected by CLI) | install |
| Cursor | Rule file | .cursor/rules/[slug].mdc | install |
| Windsurf | Rule / workflow | .windsurf/rules/[slug].md | install |
| OpenAI Agents | Agents SDK definition | agent.json | export |
| Gemini CLI | CLI extension | ~/.gemini/extensions/[slug] | install |
| GitHub Copilot | Instructions file | .github/copilot-instructions.md | export |
| Replit Agent | Agent template | .replit/agents/[slug] | install |
| MCP-compatible | MCP server | MCP client config | install |
Install vs. export
- Install copies the package into a tool's local directory so the tool loads it directly.
- Export translates the package into a tool's native format (an
agent.jsonfor OpenAI Agents, acopilot-instructions.mdfor GitHub Copilot). Use it when the target tool doesn't read Nuclexa packages natively.
Reading the compatibility table
On every package page, the Compatibility table shows a row per platform with its status (Supported / Exportable / Partial) and install method. A package only lists platforms it has been built and tested against — if a platform is missing, assume it is unsupported rather than untested.
Choosing where to install? See Installation targets for the exact commands per platform.