wox-plugin-submit2store

Submits a Wox plugin to the official store via a fork-based pull request workflow.

27.3k|2.4k|Updated Dec 19, 2013
One-click install
npx skills add https://github.com/Wox-launcher/Wox --skill wox-plugin-submit2store
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wox-plugin-submit2store
Source: https://github.com/Wox-launcher/Wox/tree/main/.agents/skills/wox-plugin-submit2store
Command: npx skills add https://github.com/Wox-launcher/Wox --skill wox-plugin-submit2store

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Publishing a Wox plugin to the official store requires forking the Wox repository, checking store-plugin.json for duplicate IDs, building a correctly formatted store entry, and opening a pull request — a manual process prone to formatting errors and duplicate submissions.

Core Features & Use Cases

  • Fork Management: Reuses an existing fork of Wox-launcher/Wox or creates one via GitHub CLI, with a web fork fallback.
  • Duplicate Detection: Checks upstream store-plugin.json for the plugin ID and stops the submission when the plugin is already listed.
  • Store Entry Generation: Builds a validated store entry from local plugin.json metadata, release asset URLs, and raw GitHub icon and screenshot URLs.
  • Use Case: After publishing a release of your Wox plugin, run this Skill to verify it is not yet listed, add the entry to store-plugin.json on a branch in your fork, and open a PR against Wox-launcher/Wox.

Quick Start

Use the wox-plugin-submit2store skill to check whether my plugin is already in the Wox store and submit a store PR if needed.

Frequently Asked Questions about wox-plugin-submit2store

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

FAQPage Schema
How do I submit a Wox plugin to the official store?

Fork the Wox-launcher/Wox repository, add your plugin entry to store-plugin.json on a branch, and open a pull request upstream. This Skill automates that flow by reading your plugin.json, checking for duplicates, and preparing the PR.

How do I check if my Wox plugin is already listed in the store?

The Skill searches the upstream store-plugin.json for your exact plugin ID from plugin.json. If the ID exists, it stops, reports the plugin as already listed, and shows the matching entry.

What metadata is required for a Wox store plugin entry?

The entry needs Id, Name, Author, Version, MinWoxVersion, Runtime, Description, IconUrl, Website, DownloadUrl, ScreenshotUrls, SupportedOS, and timestamps. Values come from plugin.json, the repository URL, and the latest release asset.

Do I need a fork of Wox-launcher/Wox to submit a plugin?

Yes, unless you have direct write access to Wox-launcher/Wox. The Skill reuses an existing fork, creates one with GitHub CLI when authenticated, or directs you to the web fork flow before continuing.

Why is my Wox plugin store submission blocked?

Submission is blocked when plugin.json still contains template placeholders, the repository URL cannot be determined, no public .wox release asset exists, or icons and screenshots lack stable public URLs. Fix these in your repository first.