omarchy-plugin-check

Runs marketplace security baseline and submission checks on Omarchy plugins before committing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires omakit.

What problem does it solve? Omarchy plugin authors risk pushing commits that the marketplace's security baseline or submission checks would refuse, causing stale reviews and wasted human review rounds. This Skill runs those exact checks locally, read-only, before any commit or push. ## Core Features & Use Cases - Marketplace Baseline Verification: Runs omakit verify to get the marketplace's own security result for the exact commit, verbatim, with no wrapper checks. - Pre-Submission Checks: Runs omakit submit with category and tags to execute every pre-submission check and report blocking failures with remedies. - Tree Inspection: Runs omakit inspect to list processes, hosts, writes, and timers alongside the review classes human reviewers raise most, with measured finding shares. - Use Case: After refactoring an Omarchy plugin's shell script, run the verify and submit commands to confirm the marketplace would not refuse the commit, then inspect the tree to see whether a new curl call lacks a timeout before pushing. ## Quick Start Check my Omarchy plugin in the current repository for marketplace readiness before I commit and push it.

Frequently Asked Questions about omarchy-plugin-check

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

FAQPage Schema
How do I check if my Omarchy plugin is marketplace-ready?▼

Run `omakit verify <plugin-repo> --json` for the security baseline and `omakit submit <plugin-repo> --category <category> --tags <a,b> --json --offline` for all pre-submission checks. Both run locally and read-only against your exact commit.

What does omakit inspect report about a plugin tree?▼

It lists every process with its argv and deadline status, every host with timeout and size-cap flags, every write path, and every timer interval. It also maps observed patterns to review classes human reviewers raise most, with measured finding shares.

Why does omakit submit fail without category and tags?▼

A run without `--category` and `--tags` prompts a person at a terminal, which an agent must never wait on. Running once without them returns a usage error listing the controlled values read from the pinned marketplace form.

Does a passing baseline result mean my plugin is secure?▼

No. The baseline performs no data-flow analysis and is not a security review; `passed` only means nothing in the baseline holds the plugin back. A `review-required` result means a maintainer must examine capabilities in that commit.

What if omakit is not installed on my Omarchy system?▼

Install it with `npm install --global omakit`, then run `omakit doctor` to check node, git, the pin, and PATH. The first verify or submit needs `omakit pin` to fetch a sparse read-only marketplace checkout.

When should I use --offline with omakit submit?▼

Use `--offline` only in the local check loop; it skips the one network-dependent check and reads listed ids from the pin. Drop it for the real submission, which is handled by the separate submit skill.