Plugins bundle rules, skills, agents, commands, MCP servers, and hooks into distributable packages. Use plugins to extend Qoder's capabilities — from code review and automated deployment to connecting enterprise systems.
All directories except
Located at
The
If pointing to a directory (e.g.
Each skill is an independent directory containing a
Key fields:
The MCP config file is
Hook configuration file is
This file helps users quickly understand which external connections need to be configured after installing the plugin, along with each connection's permissions and security boundaries.
When
Plugins are distributed as
Correct structure:
Standalone skills are for single-project use (placed in
It must be at
Use declarative Connector configuration (
Supported Coming Soon N/A
What Plugins Contain
| Component | Description |
|---|---|
| Skills | Atomic AI execution units defining "how to do something". Each skill is a SKILL.md file |
| Rules | Directives injected into AI context to constrain behavior and style |
| Agents | Sub-agent definitions that can be dispatched by the main agent |
| Commands | Slash commands (/command-name) — user-triggered shortcuts |
| MCP Servers | Configuration for external service connections via MCP |
| Hooks | Event hooks that automatically execute scripts at specific moments |
Directory Structure
.qoder-plugin/ are optional. Paths can be explicitly declared in plugin.json to override defaults.
Plugin Manifest (plugin.json)
Located at .qoder-plugin/plugin.json, this is the only required file.
| Field | Type | Required | Description |
|---|---|---|---|
| name | string | Yes | Plugin identifier, must be kebab-case |
| version | string | Yes | Semantic version, e.g. 1.0.0 |
| description | string | No | Brief description |
| displayName | string | No | Display name (supports CJK), for UI and marketplace |
| author | object | No | Author info |
| keywords | string array | No | Search keywords |
| homepage | string | No | Homepage or documentation URL |
| repository | string | No | Source repository URL |
| license | string | No | SPDX license identifier |
Component Path Declarations
| Field | Type | Description |
|---|---|---|
skills | string or string array | Skill directory paths |
rules | string or string array | Rule directory paths |
agents | string or string array | Agent file paths |
commands | string, string array, or object | Command file/directory paths, or command object map |
hooks | string | Hook config JSON file path |
mcpServers | string | MCP server config JSON file path |
skills field supports explicit declaration of which skills to load:
"./skills"), all subdirectories containing SKILL.md are loaded.
Minimal Configuration
Full Example
Skills (SKILL.md)
Each skill is an independent directory containing a SKILL.md file with YAML frontmatter + Markdown body:
| Field | Description |
|---|---|
| description | The most important field — Qoder uses it to decide when to invoke the skill |
| name | Skill name, defaults to directory name |
MCP Server Configuration
The MCP config file is mcp.json (or .mcp.json), using the top-level mcpServers field.
- Local Process Mode
- Remote Service Mode (Declarative Connector)
Hooks
Hook configuration file is hooks/hooks.json, executing commands automatically on specific events.
matcher: Filters which tool names trigger the hook${QODER_PLUGIN_ROOT}: Absolute path to the plugin's installation directory. Use it to reference internal plugin resources (scripts, configs, etc.) — paths resolve correctly regardless of where the plugin is installed
Project Instructions (qoder.md)
qoder.md is the plugin-level project instructions file, defining the agent persona, workflow orchestration, and guardrails. It is injected as the core system prompt when the plugin is activated. File name is qoder.md.
Connector Dependencies (CONNECTORS.md)
CONNECTORS.md documents connector dependencies for plugin users — which skills depend on which connections, what resources are accessed, and how to configure them.
Example:
Commands Object Format
When commands is an object, each command can have detailed configuration:
| Field | Type | Description |
|---|---|---|
source | string | Command Markdown file path |
description | string | Command description |
argumentHint | string | Argument hint, e.g. "[env]" |
Packaging and Distribution
Package Format
Plugins are distributed as .zip files:
1
The zip root IS the plugin root
No extra nesting — the manifest sits directly under the zip root.
2
plugin.json must exist
.qoder-plugin/plugin.json is required.3
Use the recommended filename
Recommended filename:
{name}-{version}.zip.Path Rules
- All relative paths must start with
./ ..is not allowed (no path traversal)- JSON paths must end with
.json - Markdown paths must end with
.md
FAQ
What's the difference between a plugin and a standalone skill?
Standalone skills are for single-project use (placed in .qoder/skills/). Plugins are for cross-project sharing and enterprise distribution — bundling multiple skills and configurations as one unit.
Where does plugin.json go?
It must be at .qoder-plugin/plugin.json.
How to handle MCP Servers requiring personal credentials?
Use declarative Connector configuration ({{USER_CONFIG}} placeholder + _setup guidance). Each user fills in their own credentials during installation.
Client Support Matrix
Supported Coming Soon N/A
| Component | Qoder IDE | Qoder CLI | JetBrains Plugin |
|---|---|---|---|
| Skills (SKILL.md) | |||
| Rules (.md) | |||
| Agents (.md) | |||
| Commands | |||
| MCP Servers | |||
| Hooks (hooks.json) | |||
| Project Instructions (qoder.md) |