plugin-workbench

Scaffold, build, pack, and install Vetta desktop plugins through a guided end-to-end pipeline.

154|27|Updated Aug 3, 2026
One-click install
npx skills add https://github.com/openvetta/open-vetta --skill plugin-workbench-openvetta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-workbench
Source: https://github.com/openvetta/open-vetta/tree/main/packages/plugins/presets/plugin-workbench/agent/skills/plugin-workbench
Command: npx skills add https://github.com/openvetta/open-vetta --skill plugin-workbench-openvetta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @vetta-org/plugin-sdk, @vetta-org/plugin-vite, and includes references (resource) components.

What problem does it solve? Building a Vetta desktop plugin normally requires reading SDK documentation, writing manifest and UI code, and running build and install steps correctly. This Skill automates that entire pipeline for non-developers: it reads the version-matched plugin handbook, scaffolds the project, implements the extension, builds and packs it, and guides installation into the local Vetta app. ## Core Features & Use Cases - End-to-end plugin pipeline: Clarify requirements, scaffold with the bundled CLI (init), implement against the SDK manual, then build and pack with build-and-pack.mjs into a versioned zip. - Version-matched documentation: Locates the plugin handbook shipped inside the project's own @vetta-org/plugin-sdk via the CLI docs --json command, so API contracts always match the compiled SDK version. - Extension point coverage: Supports activity tabs, workspace views, input-bar actions, file previews, agent tools, message cards, MCP servers, guiding words, and contributed agents/teams. - Hot-reload workflow: Detects devWatch state on installed plugins and uses hot update for iteration instead of reinstalling. - Use Case: A user says "make me a plugin that previews .xyz files." The Skill asks for the plugin id and name, reads the file-preview and styling chapters of the manual, scaffolds the project, implements the preview component with proper error notification, builds the zip, and tells the user to click "Apply to Vetta" in the workbench panel. ## Quick Start Ask the agent to create a Vetta plugin for your idea, for example: "Create a Vetta plugin that adds a sidebar panel showing my project notes, then build and install it."

Frequently Asked Questions about plugin-workbench

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Vetta desktop plugin without coding experience?▼

Enable the Plugin Workbench toggle in the input bar, then describe the plugin you want. The Skill asks for the plugin id, name, and permissions, reads the SDK handbook, scaffolds the project with the bundled CLI, implements the code, and builds an installable zip.

How do I install a built plugin into the Vetta app?▼

After the build-and-pack script produces a zip, open the Plugin Workbench activity panel and click "Apply to Vetta" on the project card. This installs, authorizes, and enables the plugin in one step without a confirmation dialog, and enables hot reload by default.

What extension points can a Vetta plugin use?▼

Vetta plugins can contribute activity tabs, workspace views, input-bar actions, file previews, global overlays, agent tools, message cards, MCP servers, guiding words, and declared agents or teams. Each extension point requires specific permissions declared in plugin.json.

Why is my installed Vetta plugin not showing any effect?▼

Check that the required permissions are granted, scope_use is declared for UI slots and tools, and the plugin is enabled. If you edited code, either rely on hot reload when devWatch is active or rebuild and reapply the plugin from the workbench panel.

How does hot reload work when developing Vetta plugins?▼

Once a plugin is installed, the workbench panel enables hot update by default, linking the plugin to your project directory with a persistent dev process. Saving source or plugin.json changes triggers automatic rebuild and reload, so no repacking or manual reload is needed.

What are the limitations of the Vetta plugin workbench?▼

It does not publish plugins to a marketplace, does not provide drag-and-drop no-code building, and cannot guarantee native C++ dependencies build under the managed Node runtime. User plugins should not enable hardIsolation unless explicitly required.