Plugins
Bundle skills, slash commands, subagents, MCP servers, and hooks into a single installable plugin.
Anatomy
A plugin is a repository with a manifest at .deyin-plugin/plugin.json. Components auto-discover from skills/, commands/, agents/, hooks/hooks.json, mcp.json (or .mcp.json), and a root SKILL.md works as a single-skill plugin. Bundled first-party plugins ship inside the desktop app: browser, computer-use, chrome, visualize, and security.
Installing
Install from GitHub with owner/repo (optionally @ref) or a direct URL. The official catalog is the DeYinAI/registry repository. Plugin cards expose interface metadata — display name, category, default prompts, brand color.
Secrets
Manifest variables marked secret are entered during setup, encrypted with the OS keychain, and substituted as ${VAR} into the plugin's MCP configuration at runtime.
Manifest
A plugin bundles any mix of skills, commands, agents, and MCP servers under one versioned manifest.
Each component type uses the same format it would as a loose directory — plugins are packaging, not a new runtime.
plugin.json
{
"name": "my-plugin",
"version": "0.1.0",
"skills": ["skills/"],
"commands": ["commands/"],
"agents": ["agents/"],
"mcp": "mcp.json"
}Packaging & distribution
Install from a tarball, a git URL, or a local path during development. Installed plugins land in ~/.deyin/plugins and can be toggled per project in Settings → Plugins.
deyin plugin pack ./my-plugin # → my-plugin-0.1.0.tgz
deyin plugin install ./my-plugin-0.1.0.tgz