wox-plugin-creator
Provides scaffolding and official SDK templates for creating and publishing Wox plugins in Node.js or Python.
Install
mkdir -p .claude/skills/wox-plugin-creator && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4484" && unzip -o skill.zip -d .claude/skills/wox-plugin-creator && rm skill.zipInstalls to .claude/skills/wox-plugin-creator
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Create, scaffold, implement, and package Wox plugins (nodejs, python, script-nodejs, script-python). Use when cloning official SDK templates, generating script plugin templates, editing plugin.json metadata, defining SettingDefinitions and validators, wiring i18n, implementing plugin APIs, or preparing plugin repositories for local packaging. If the user wants to publish a plugin to the official Wox store or check whether it is already listed, prefer wox-plugin-submit2store.Key capabilities
- →Scaffold Node.js and Python Wox plugins
- →Generate single-file script plugins
- →Replace metadata placeholders in templates
- →Search and fetch Iconify SVG constants
- →Validate plugin settings and requirements
How it works
It clones official SDK templates or copies local script templates, then populates metadata placeholders based on user-provided configuration.
Inputs & outputs
When to use wox-plugin-creator
- →Creating a new Wox plugin
- →Scaffolding a Python Wox plugin
- →Setting up a Node.js script plugin
- →Preparing a plugin for distribution
About this skill
Wox Plugin Creator
Quick Start
- Scaffold a Node.js plugin (clones template repo):
python3 scripts/scaffold_wox_plugin.py --type nodejs --output-dir ./MyPlugin --name "My Plugin" --trigger-keywords my
- Scaffold a Python plugin (clones template repo):
python3 scripts/scaffold_wox_plugin.py --type python --output-dir ./MyPlugin --name "My Plugin" --trigger-keywords my
- Scaffold a script plugin (uses local templates; plugin-id auto-generated; single file output):
python3 scripts/scaffold_wox_plugin.py --type script-nodejs --output-dir ./Wox.Plugin.Script.MyScript.js --name "My Script" --trigger-keywords my
Workflow
1) Scaffold plugin files
- Use
scripts/scaffold_wox_plugin.pyfornodejs,python,script-nodejs, orscript-python. - Pass
--nameand--trigger-keywordsfor every runtime. The scaffold exits without them. - For Node.js and Python, the scaffold clones the official template repos and replaces placeholders like
{{.ID}},{{.Name}},{{.Description}},{{.TriggerKeywordsJSON}},{{.Author}}. - Before starting work in a new SDK plugin project, run
make initin the project root when the project has not been initialized yet. - Script plugins are single-file plugins. Prefer filenames like
Wox.Plugin.Script.<Name>.<ext>(e.g.,Wox.Plugin.Script.Memos.py). - For script plugins, the scaffold copies Wox script templates from
~/.wox/ai/skills/wox-plugin-creator/assets/script_plugin_templates/and fills metadata placeholders. - Prefer standard library features; avoid third-party dependencies unless absolutely necessary.
- For SDK usage and API details, read
references/sdk_nodejs.mdorreferences/sdk_python.md. - For
plugin.json,SettingDefinitions,QueryRequirements, validators, dynamic settings, and feature flags, readreferences/plugin_json_schema.mdfirst. - When authoring
SettingDefinitions, always decide whether each setting is platform-specific before shipping it. Wox cloud sync replicates normal plugin settings across devices, so local paths, executable paths, shell commands, hotkeys, system integrations, browser profiles, and application paths should usually setIsPlatformSpecific: true. Account IDs, API keys, remote service hosts, and cross-platform user preferences should usually keepIsPlatformSpecific: false. - Use
DisabledInPlatformsonly to disable a setting on selected platforms. It does not isolate stored values; useIsPlatformSpecificwhen the value must differ per platform after cloud sync. - When a plugin cannot run a query without required settings such as access keys, declare those requirements in metadata
QueryRequirementsinstead of returning ad hoc setup results fromquery(). - For ready-to-copy patterns such as validated textbox/select fields, editable tables, AI model selectors, and dynamic preview settings, read
references/settings_patterns.md. - For Python settings APIs, note that helper builders are limited; advanced settings are often created by constructing
PluginSettingDefinitionItemand value objects directly.
2) Author result and action icons
- Read
references/icons.mdfor icon selection, inline SVG patterns, and placement rules. - When the requested icon semantics already match a bundled generic icon under
assets/iconify/, prefer reusing that local reference before searching for a new one. - Use
scripts/search_iconify.pyto search Iconify collections and fetch ready-to-inline SVG constants foricons.tsoricons.py.
3) Package and submit plugin
- For SDK plugins cloned from templates, run
make packageinside the template repo. - For submitting a plugin to the official Wox store, prefer
wox-plugin-submit2storeskill. - Script plugins do not use
plugin.json; they embed a JSON metadata block in the script header comments.
Resources
- scripts:
scripts/scaffold_wox_plugin.py,scripts/search_iconify.py - references:
references/plugin_overview.md,references/scaffold_nodejs.md,references/scaffold_python.md,references/sdk_nodejs.md,references/sdk_python.md,references/plugin_json_schema.md,references/settings_patterns.md,references/plugin_i18n.md,references/icons.md - assets:
assets/script_plugin_templates/,assets/iconify/
When not to use it
- →When the user wants to submit a plugin to the official store
- →When the user is editing an existing plugin without scaffolding
Prerequisites
Limitations
- →Requires --name and --trigger-keywords for all runtimes
- →Script plugins are limited to single-file implementations
How it compares
It automates the creation of standard plugin structures and metadata, ensuring consistency compared to manual file creation.
Compared to similar skills
wox-plugin-creator side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| wox-plugin-creator (this skill) | 1 | 1mo | Review | Intermediate |
| telegram-bot-builder | 106 | 6mo | Review | Intermediate |
| copilot-sdk | 7 | 4mo | Review | Intermediate |
| reddit-api | 3 | 4mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
telegram-bot-builder
davila7
Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategies, and scaling bots to thousands of users. Use when: telegram bot, bot api, telegram automation, chat bot telegram, tg bot.
copilot-sdk
github
Build agentic applications with GitHub Copilot SDK. Use when embedding AI agents in apps, creating custom tools, implementing streaming responses, managing sessions, connecting to MCP servers, or creating custom agents. Triggers on Copilot SDK, GitHub SDK, agentic app, embed Copilot, programmable agent, MCP server, custom agent.
reddit-api
alinaqi
Reddit API with PRAW (Python) and Snoowrap (Node.js)
adk-engineer
jeremylongshore
Execute software engineer specializing in creating production-ready ADK agents with best practices, code structure, testing, and deployment automation. Use when asked to "build ADK agent", "create agent code", or "engineer ADK application". Trigger with relevant phrases based on skill purpose.
agent-v3-performance-engineer
ruvnet
Agent skill for v3-performance-engineer - invoke with $agent-v3-performance-engineer
llm-application-dev
skillcreatorai
Building applications with Large Language Models - prompt engineering, RAG patterns, and LLM integration. Use for AI-powered features, chatbots, or LLM-based automation.