Installable AI capabilities
An installable AI capability is any reusable unit of behavior you can add to an AI tool: an agent that reviews code, a skill that audits for vulnerabilities, an MCP server that connects to your database, a rule that shapes how your editor writes code, a workflow that ships a release. Nuclexa packages every one of these in the same standard format so it can be discovered, versioned, permission-scoped, and installed anywhere.
The unifying idea: a capability is content plus a manifest. The content is what the tool runs (instructions, a server, a set of rules). The manifest declares what it is, which platforms it targets, and what it is allowed to do.
Supported package types
Nuclexa supports ten capability types. The type field in agent.json determines how a package is categorized and installed.
| Type | type value | What it is |
|---|---|---|
| Agent | agent | An autonomous, multi-step agent with tools and instructions. |
| Claude Skill | claude-skill | A packaged Claude skill (SKILL.md + resources). |
| Cursor Rule | cursor-rule | Project rules and context for Cursor (.mdc). |
| MCP Server | mcp-server | A Model Context Protocol server exposing tools & resources. |
| Workflow | workflow | A multi-step or multi-agent orchestration. |
| Prompt Pack | prompt-pack | A curated, versioned collection of prompts and instructions. |
| Custom Mode | custom-mode | A reusable editor/assistant mode with its own behavior. |
| Tool Adapter | tool-adapter | A connector that wires an agent to an external tool or API. |
| Agent Template | agent-template | A starter scaffold for building a new agent. |
| Automation | automation | A triggered or scheduled task that runs without a human in the loop. |
Choosing a type
Pick the type that matches how the capability is consumed, not just what it does:
- If it runs autonomously and decides its own steps → Agent.
- If it's a Claude-specific skill bundle → Claude Skill.
- If it only shapes an editor's suggestions → Cursor Rule or Custom Mode.
- If it exposes tools over a protocol → MCP Server or Tool Adapter.
- If it's a fixed sequence of steps → Workflow or Automation.
- If it's a set of prompts, or a scaffold to fork → Prompt Pack or Agent Template.
Next: see which tools each type can install to in Platform compatibility.