omarchy-plugin-submit

Runs pre-submission checks and generates the marketplace issue title and body for Omarchy plugins.

3|Updated Sep 12, 2026
One-click install
npx skills add https://github.com/mtolhuys/omakit --skill omarchy-plugin-submit-mtolhuys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: omarchy-plugin-submit
Source: https://github.com/mtolhuys/omakit/tree/main/skills/omarchy-plugin-submit
Command: npx skills add https://github.com/mtolhuys/omakit --skill omarchy-plugin-submit-mtolhuys

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires omakit.

What problem does it solve? Submitting an Omarchy Quattro plugin to the marketplace requires passing many checks and producing an exact issue title and body; doing this by hand risks refusals, stale-commit validation, and typos in the submission form. ## Core Features & Use Cases - Pre-submission check run: Executes every blocking check via omakit submit, reporting READY, REFUSED, or LISTED outcomes with remedies for each failure. - Exact issue content generation: Produces the submission issue title and body from the pinned marketplace form, with the Repository URL taken from origin so it is never typed by hand. - Retry edit protocol: Regenerates the body with --body-out, diffs it against the current issue, and verifies with omakit watch after an owner-approved edit. - Use Case: A plugin owner asks whether their repository is ready to list; the skill runs the checks, explains any refusal such as a taken id or unpushed commit, and produces the paste-ready issue content without posting anything. ## Quick Start Ask the assistant to check whether the plugin in this repository is ready to submit to the Omarchy marketplace and to produce the submission issue title and body.

Frequently Asked Questions about omarchy-plugin-submit

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

FAQPage Schema
How do I submit an Omarchy plugin to the marketplace?▼

Run `omakit submit <plugin-repo> --category <category> --tags <a,b>` after `omakit pin`. It runs every blocking check and prints the exact issue title and body; creating the issue is a separate act requiring the plugin owner's explicit approval.

How do I check if my plugin is ready to submit?▼

Run the submit command and read the outcome: READY means all blocking checks passed and the body was produced, REFUSED means a blocking check failed with a printed remedy, and LISTED means the plugin is already listed by its own repository.

Why was my Omarchy plugin submission refused?▼

Common refusals include an id already listed by a different repository, a Repository URL mismatch with origin, or an unpushed local commit. Each failing check prints the failing paths, a remedy, and the measured reason the rule exists.

Does pushing a fix update my marketplace validation?▼

No. The marketplace validates the pushed default-branch HEAD only when the issue is opened or edited. After pushing, regenerate the body with `omakit submit --body-out` and edit the issue following the retry edit protocol.

Can I submit a plugin that ships AGENTS.md or CLAUDE.md files?▼

Yes, agent-control files trigger a warning, not a refusal, and the body is still produced. The recommended remedy is moving guidance to a non-agent filename like DEVELOPMENT.md and untracking the originals, but the owner decides.