Skip to content
Kodik Kodik

Installing items

The Kodik Marketplace lets you install several types of extensions: full plugins, individual components (skills, commands, rules), MCP servers, and project templates. Templates use a special scaffolding flow rather than a simple file copy.

Installing a plugin

Section titled “Installing a plugin”

A plugin is an extension bundle that can include MCP servers, skills, commands, rules, hooks, and sub-agent profiles in any combination. The catalog is served from the official open-source plugins repository — the marketplace/ folder of the Kodik repo — so every plugin’s source is publicly reviewable. Installation is a single click: open the Plugins tab, find the plugin you want, and press Install.

Kodik copies the complete plugin package (including any scripts and reference files it ships) into the plugins directory and updates the registry. See Plugins & Marketplace for details on how plugins are structured.

Install scope

Section titled “Install scope”

Plugins and individual components (skills, commands, rules) can be installed in two scopes:

ScopeLocationAvailability
Global~/.kodik/Skills, ~/.kodik/Commands, or ~/.kodik/RulesAvailable in all workspaces
Workspace.kodik/ inside the project folderAvailable only in the current project

Global installation suits general-purpose tools. Workspace installation is best for components specific to a project or team.

Installing individual components

Section titled “Installing individual components”

Beyond full plugins, you can install individual items from the dedicated Marketplace tabs:

  • Skills — from the “Skills” lane in Community; each skill is installed as its own package folder containing SKILL.md and marketplace metadata under ~/.kodik/Skills/<skill-name>/ (global) or .kodik/skills/<skill-name>/ (workspace).
  • Commands — from the “Prompts” lane in Community; written to ~/.kodik/Commands/ or .kodik/commands/.
  • Rules — from the “Rules” lane in Community; written to ~/.kodik/Rules/ or .kodik/rules/.

Skill and Rule cards in Browse or Community open a preview first, so you can inspect the item before choosing Global or Workspace installation.

Paid items use your Kodik credit balance before installation. When you click a paid item’s buy action, Kodik purchases access through the configured Marketplace backend; if your balance is too low, no local files are written and the item remains locked.

Installing an MCP server

Section titled “Installing an MCP server”

MCP servers ship inside plugins: install a plugin from the Plugins tab and any MCP servers it bundles are written to the plugin’s own .mcp.json and become available to chat immediately. There is no separate MCPs catalog anymore.

After installation, manage the servers from Settings → MCP Servers, where plugin-provided servers appear alongside your own. Deleting a plugin-provided server there removes only that server — the plugin and its other components stay installed, and the plugin’s Marketplace page can re-add it. You can also add or remove individual plugin items (a single skill, command, or MCP server) from the plugin’s detail page.

Installing a template

Section titled “Installing a template”

Templates work differently: instead of copying files directly from the Marketplace card, Kodik starts a guided /install-template flow in the native chat. Click Use this template or Install with Kodik and Kodik preloads the template’s scaffold payload, then the agent clarifies the target location and runs initial setup steps.

The template Download action writes a small manual setup package into the selected workspace folder. Use it when you want to inspect the marketplace metadata and scaffold command before asking the agent to install it. See Templates for details.

Section titled “Related pages”