# Marketplace form map

This reference records the official GitHub issue templates observed on 2026-09-01. Refresh the live templates before use; labels, options, helper text, and required acknowledgments may change.

## Form chooser

The marketplace issue chooser currently presents:

1. **Submit a plugin** — “Propose a public Omarchy plugin repository for the marketplace.”
2. **Verify or update a listed plugin** — “Verify the recorded snapshot or validate and publish a newer exact commit.”

Use the first only for a new listing. Use the second for an existing listing.

## Submit a plugin

Issue title prefix: `[Plugin]: ` followed by the human-readable plugin name. GitHub pre-fills the prefix.

| Field | Control | Required | Guidance |
| --- | --- | --- | --- |
| Title | Text input | Yes | Append the human-readable `manifest.json` name to the prefilled prefix. Example: `[Plugin]: Hacker Typer`. Never leave only `[Plugin]:`. |
| Repository URL | Text input | Yes | Public GitHub repository root containing the plugin manifest. No trailing slash or `/tree/...` path. |
| Category | Single-select dropdown | Yes | Defaults to **Appearance** with no blank choice. Deliberately select the correct category; do not treat the default as a recommendation. |
| Tags | Multi-select dropdown | Yes | Displays **None** initially. Select one to three reusable tags; more than three are rejected. |
| Suggest a missing tag | Text input | No | Suggest one reusable missing tag; reviewers decide whether to add it. |
| Maintainer notes | Text area | No | Installation, permissions, dependencies, or other reviewer context. |
| Submission checklist | Checkboxes | All five | Confirm each statement with the owner before checking it. |

Categories currently appear in this order. The dropdown marks the current choice with a check; **Appearance** is initially selected.

- Appearance
- Desktop
- Developer Tools
- Hardware
- Productivity
- System
- Widgets
- Other

Tags appear in a scrollable multi-select menu in this order. The closed control shows **None** before any tag is selected.

- AI
- Bar
- Hyprland
- Launcher
- Media
- Power management
- Quickshell
- Security
- System
- Workspaces

Exact checklist:

- The repository is public and contains installation and removal instructions.
- I have documented the plugin license and any external dependencies.
- I confirm that I own or have permission to submit this plugin and its preview assets.
- The plugin does not overwrite user configuration without explicit consent.
- I understand that approval is for listing and is not a security review.

## Verify or update a listed plugin

Issue title prefix: `[Verify]: `. GitHub pre-fills the prefix.

| Field | Control | Required | Guidance |
| --- | --- | --- | --- |
| Title | Text input | Yes | Append a concise existing-listing identifier. The current template prescribes only the `[Verify]:` prefix; the exact plugin ID is the clearest suffix. |
| Verification action | Single-select dropdown | Yes | Defaults to **Verify the currently listed snapshot** with no blank choice. Deliberately choose the action that matches the requested commit. |
| Plugin ID | Text input | Yes | Exact marketplace plugin ID. Multi-plugin sources are handled source-wide. |
| Repository URL | Text input | Yes | Existing public GitHub repository root URL for the listing. |
| Target commit | Text input | Yes | Full 40-character listed snapshot SHA or current repository HEAD, depending on the action. |
| Verification acknowledgment | Checkbox | Yes | Confirm the exact-commit and non-audit statement below. |
| Standard installation acknowledgment | Checkbox | Conditional | Required only when requesting removal of a manual-installation override. Leave unchecked for an ordinary verification or update even when the sentence itself is true. |

Verification actions appear in this order. The dropdown marks the current choice with a check.

- **Verify the currently listed snapshot**
- **Verify and publish a newer upstream commit**

Exact required acknowledgment:

> I understand that only the exact target commit can become a verified marketplace snapshot and that verification is not a security audit.

Conditional acknowledgment:

> I confirm that this listed root plugin supports the standard Omarchy installation path and does not require manual setup.

Do not check the conditional acknowledgment unless the request is specifically asking the marketplace to remove a manual-installation override.

## Optional screenshot protocol

Guide the user from the refreshed official template and repository facts without requiring screenshots. Provide known values—including Title—immediately.

Use a screenshot only when the user requests visual guidance, reports a mismatch, a field is ambiguous, or the authoritative form cannot be fetched. Reuse any screenshot already present in the conversation.

When a screenshot is genuinely needed:

1. State the specific uncertainty it will resolve.
2. Ask for only the next unresolved visible section.
3. Compare its labels and helper text against the refreshed issue template.
4. Resolve the mismatch, then return to direct field guidance.

Screenshots are optional supporting evidence, not authorization to submit. Final approval is based on the complete text summary of fields and acknowledgments, not a required screenshot.