Add native OpenClaw support for the winui plugin

CHANGELOG.md

@@ -23,6 +23,11 @@ The `version-bump` and `changelog-entry` CI jobs enforce this.
 
 ### Added
 
+- OpenClaw support: the `winui` plugin now ships a native OpenClaw manifest
+  (`openclaw.plugin.json`) and `package.json` entry point so all eight skills
+  load in OpenClaw (`Format: openclaw`). README documents the marketplace and
+  local-clone install routes.
+
 ### Changed
 
 ### Fixed

README.md

@@ -69,6 +69,28 @@ Add the `microsoft/win-dev-skills` marketplace, then enable the `winui` plugin f
 > **Note:** Codex doesn't have an "agents" concept, so the orchestrator agent isn't exposed there. The skills still work - invoke them by name (e.g. `/winui-setup`, `/winui-design`) and Codex will load them on demand.
 </details>
 
+<details>
+<summary><strong>OpenClaw</strong></summary>
+
+Install straight from this repo - no marketplace pre-registration needed. The explicit `--marketplace` source clones the repo on demand, reads its marketplace manifest, and installs the `winui` plugin natively (`Format: openclaw`):
+
+```powershell
+openclaw plugins install winui --marketplace microsoft/win-dev-skills
+openclaw gateway restart
+```
+
+Or from a local clone:
+
+```powershell
+git clone https://github.com/microsoft/win-dev-skills
+openclaw plugins install ./win-dev-skills/plugins/winui
+```
+
+Verify the eight skills loaded with `openclaw skills list` (each shows `✓ ready`).
+
+> **Note:** OpenClaw maps skills, not agents, so the `winui-dev` orchestrator agent isn't exposed there. The skills still work - ask the agent for a WinUI task and it loads the relevant skill on demand.
+</details>
+
 Then start a new session and run the `winui-setup` skill with `/winui-setup`.
 
 Once setup is done, try a real task:

plugins/winui/index.js

@@ -0,0 +1,13 @@
+import { definePluginEntry } from "openclaw/plugin-sdk/plugin-entry";
+
+// win-dev-skills is a content plugin: it ships WinUI 3 skills (and agents) only,
+// with no runtime tools, providers, or channels. OpenClaw native plugins require
+// a code entry point, so this registers nothing and lets the manifest's `skills`
+// field drive skill discovery.
+export default definePluginEntry({
+  id: "winui",
+  name: "WinUI",
+  description:
+    "Agents and skills for WinUI 3 app development. Create new WinUI 3 desktop apps, convert from other frameworks to WinUI 3, or add features to existing WinUI 3 applications.",
+  register() {},
+});

plugins/winui/openclaw.plugin.json

@@ -0,0 +1,13 @@
+{
+  "id": "winui",
+  "name": "WinUI",
+  "description": "Agents and skills for WinUI 3 app development. Create new WinUI 3 desktop apps, convert from other frameworks to WinUI 3, or add features to existing WinUI 3 applications.",
+  "skills": [
+    "skills"
+  ],
+  "configSchema": {
+    "type": "object",
+    "additionalProperties": false,
+    "properties": {}
+  }
+}

plugins/winui/package.json

@@ -0,0 +1,21 @@
+{
+  "name": "winui",
+  "type": "module",
+  "private": true,
+  "description": "Agents and skills for WinUI 3 app development. Create new WinUI 3 desktop apps, convert from other frameworks to WinUI 3, or add features to existing WinUI 3 applications.",
+  "license": "MIT",
+  "files": [
+    "index.js",
+    "openclaw.plugin.json",
+    "skills",
+    "agents"
+  ],
+  "peerDependencies": {
+    "openclaw": ">=2026.3.24-beta.2"
+  },
+  "openclaw": {
+    "extensions": [
+      "./index.js"
+    ]
+  }
+}