Plugins

Path(s) to agent files or directories

Author info: `name` (required), `email` (optional)

Path(s) to command files or directories

Brief plugin description

URL to plugin homepage

Path to hooks config file, or inline hook config

Tags for discovery and categorization

License identifier (e.g., `MIT`)

Relative path to a logo file in the repo (e.g., `assets/logo.svg`), or an absolute URL. Relative paths resolve to `raw.githubusercontent.com` URLs. Preferred: commit the logo to your repo and use a relative path.

Path to MCP config file, inline MCP server config, or an array of either. Overrides default `mcp.json` discovery.

Plugin identifier. Lowercase, kebab-case (alphanumerics, hyphens, and periods). Must start and end with an alphanumeric character. Examples: `my-plugin`, `prompts.chat`

URL to plugin repository

Path(s) to rule files or directories

Path(s) to skill directories

JSON Schema that declares variable **names** (tokens, connection strings). The plugin does not store secret values; users set them in the dashboard (**Plugins** → **Configure**). Substituted into `${VAR}` placeholders. See Variables.

Semantic version (e.g., `1.0.0`)