fiftyone-develop-plugin
Develops custom FiftyOne plugins (operators and panels) from scratch. Use when creating plugins, extending FiftyOne with custom operators, building interactive panels, or integrating external APIs.
Install
With your agent
Install OMGSkills skill "voxel51/fiftyone-skills:skills/fiftyone-develop-plugin" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/voxel51/fiftyone-skills /tmp/fiftyone-skills && ln -s /tmp/fiftyone-skills/skills/fiftyone-develop-plugin ~/.claude/skills/fiftyone-develop-plugin
From README
Develop FiftyOne Plugins TL;DR — Read This First Step 1: Decide what you're building. | Goal | Type | Read next | |------|------|-----------| | Run a computation, process samples, trigger actions | Operator | PYTHON-OPERATOR.md | | Persistent panel in the grid, simple/form UI | Python Panel | PYTHON-PANEL.md | | Persistent panel in the grid, rich/interactive UI | Hybrid Panel | HYBRID-PLUGINS.md + JAVASCRIPT-PANEL.md | | Panel that opens inside the sample modal | JS Modal Panel | JAVASCRIPT-PANEL.md | Step 2: Read that file NOW — before generating any code. Each file contains patterns that are not in SKILL.md. Missing them causes the most common failures (wrong default= , handler binding errors, panel not appearing in App). If something isn't rendering or you hit an error: Read TROUBLESHOOTING.md for the one-shot diagnostic command, reload vs restart table, and the top 5 error patterns with exact fixes.
More from this repo
fiftyone-app-playwright
Used when driving the FiftyOne App via the Playwright MCP — plugin/operator verification, demo or screencast recording,...
fiftyone-code-style
Writes Python code following FiftyOne's official conventions.
fiftyone-dataset-curation
End-to-end dataset curation for FiftyOne: inspect schema and quality, audit annotations, analyze class distributions,...
