Build Omarchy Plugins

Twelve skills teach an agent to build Omarchy 4 Quattro shell plugins: surface choice, QML, debugging, tests and release.

  • 128 ★ on the repository
  • Last commit
  • MIT
Plugin

Extended access

Why this level

  • Plugins built for Omarchy run as unsandboxed code inside the desktop shell.
  • The skill installer writes files into the user's agent directories.
All reasons and checks

tcballard/build-omarchy-plugins

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add plugins/build-omarchy-plugins

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Plugins built for Omarchy run as unsandboxed code inside the desktop shell.
  • The skill installer writes files into the user's agent directories.

This is third-party code. Review the repository files before installing.

What it does

Twelve agent skills help build a plugin for the Omarchy 4 Quattro desktop shell. The agent picks a suitable shell surface, creates a working starting point, writes hosted QML, debugs failures, verifies the result and prepares a release or marketplace submission. The skills are `omarchy-plugin-design`, `omarchy-plugin-scaffold`, `omarchy-bar-widget`, `omarchy-panel-overlay`, `omarchy-qml-patterns`, `omarchy-service-ipc`, `omarchy-plugin-debug`, `omarchy-plugin-test`, `omarchy-plugin-demo`, `omarchy-plugin-migrate`, `omarchy-plugin-release` and `omarchy-plugin-publish`. Generators and deterministic checks come with them.

Who it is for. Omarchy owners who write their own bar widgets and overlays and want an agent to know the rules of a long-running shell.

Good fit when

  • A widget for the Omarchy bar is needed, but the plugin lifecycle rules are unknown.
  • A plugin breaks when monitors or the theme change and the cause must be found.
  • An old integration with install hooks is moved to the Quattro model.
  • A finished plugin goes to the marketplace under its exact submission contract.

Not a fit when

  • Omarchy is not installed or its version is below 4.0.0.
  • A plugin for another desktop shell is needed.
  • The result would ship without testing on your own desktop.

Example request

Use the Build Omarchy Plugins skills: build the smallest working bar widget, enable it locally and verify the interaction.

Limitations

The toolkit targets Omarchy 4.0.0 and later with Quattro plugin support, and `omarchy-version` reports the version. Plugins run as unsandboxed user code inside the shell, and the static checks are advisory and prove no safety. A generated plugin must be tested separately on the target desktop. Installation uses a clone of release v0.9.0, while the next version v0.11.0 is still in preparation.

How to disable. Remove the installed skills with the `scripts/install_agent_skills.py` tooling from the README or the `/plugin` command in Claude Code. The Omarchy plugin itself is disabled in the shell.

FAQ

How do I install the skills in Claude Code?

Add the marketplace with `/plugin marketplace add tcballard/build-omarchy-plugins` and run `/plugin install build-omarchy-plugins@tcballard-omarchy`. Do not install both the plugin and the installer skills, or they duplicate.

Which agents does the installer support?

The `agents`, `codex`, `cursor`, `gemini`, `claude` and `opencode` targets are set with `--target`. For another host use `--target generic --destination PATH`.

Can I install only some skills?

Yes. The `--skill NAME` flag selects individual skills, and `--scope project` installs them into the current repository. Existing directories are not overwritten without `--force`.

What does the Plugin button in the Omarchy Agents panel do?

It launches your agent with Omarchy's built-in guide but does not load this skill set by itself. Ask the agent to use the installed skills alongside that guide.

Does it need model API access?

No. The skills call no model API and need no service, because the agent host chooses the model.

Discussion

No questions or reviews yet.

Plugins

A skill that teaches an agent to write Obsidian plugins to ESLint and community review rules and scaffolds a new plugin.

SkillExtended access196Repository stars

A set of 21 skills for Odoo addon development, OCA migration, reports, web security and architecture review.

PluginExtended access64Repository stars

Agentic Plugin Marketplace by wshobson

Agentic Plugin Marketplace

94 plugins, 202 agents, 183 skills and 105 commands for Claude Code, generated for Codex, Cursor, OpenCode and Copilot

PluginExtended access42.5KRepository stars

Softaworks Agent Toolkit

Softaworks Agent Skills

A marketplace of skills, subagents and commands for coding agents: development, documentation, planning and workplace communication

PluginExtended access2.7KRepository stars

Nine skills turn a repository of agent workflows into a validated, deterministically packaged ChatGPT or Codex plugin

SkillExtended access143Repository stars

A Claude Code and Codex plugin with skills for code research, tests, refactoring and independent review of finished changes

PluginExtended access454Repository stars

README in short

The README explains why a long-running shell needs dedicated skills, lists the twelve skills and deterministic tools, and describes installation for different agents and the safety boundary. A workflow guide and behavioural evaluation cases are included.

README badge

Report a problem