[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M698QKPXJ8ZG34MYHPPCAT4T":3,"skill-same:01M698QKPXJ8ZG34MYHPPCAT4T":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":45,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M698QKPXJ8ZG34MYHPPCAT4T","pr-simplify",null,"Simplify your own Windows-node change to its smallest complete fix while preserving distinct regressions, platform contracts, and required proof. Use after implementation before PR preparation, after large repairs, or when asked to shrink a change or remove slop.","openclaw\u002Fopenclaw-windows-node","openclaw","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F252820863?v=4","01M698P3FSAZ6B4R928ZF19KPT","01M698Q6SND6RHZDPP8ZM0NSP7",2197,"MIT","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpr-simplify\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"pr","simplify","pr simplify","use","when","slop","preparation","complete","proof","platform","contracts","implementation","remove","fix","node","windows","change","2026-11-10 10:12:30",false,"---\nname: pr-simplify\ndescription: \"Simplify your own Windows-node change to its smallest complete fix while preserving distinct regressions, platform contracts, and required proof. Use after implementation before PR preparation, after large repairs, or when asked to shrink a change or remove slop.\"\n---\n\n# Simplify a Windows-node change\n\nUse this author-side pass after implementing a change and before preparing a\nPR. After a large repair, simplify only the new changes and the owners they\ntouch. It precedes review and never replaces it. A review-only request produces\nfindings instead of edits. Inherit the task's scope, worktree ownership,\nmutation authority, and runtime restrictions.\n\nThe diff is a proposal. Passing tests show that it works, not that every new\nowner, abstraction, compatibility path, or test is necessary.\n\nRead the root [repository instructions](..\u002F..\u002F..\u002FAGENTS.md), the nearest scoped\n`AGENTS.md`, and only the architecture guides for the changed behavior.\n\n## 1. Re-derive the smallest complete fix\n\nRecord the target merge base, current HEAD, staged and unstaged changes, and\nrelevant untracked files. Read the complete candidate diff, the reported\nbehavior, retained proof, the production owner, and its existing tests.\n\nAsk:\n\n> Starting from the base, what is the smallest complete fix using the owners\n> already present? Would I still introduce this architecture?\n\nState the defect, required invariant, and smallest complete fix in one sentence\neach. Trace every changed hunk to that outcome. Remove unrelated cleanup or\nmove it to a separately authorized change.\n\nInspect the largest new classes, services, partials, state stores, adapters, DI\nregistrations, compatibility branches, and test fixtures first. Read their\ndirect callers and relevant history before treating them as redundant. When a\nchange moves hundreds of lines, crosses multiple owners, or combines product\nbehavior with infrastructure, identify the smallest coherent stage that can\nland independently and reduce the candidate to that stage.\n\nFor files named in the [architecture ledger](..\u002F..\u002F..\u002Fdocs\u002FARCHITECTURE.md),\npreserve every `authoritative` owner and never reintroduce a `closed`\nresponsibility. A real ownership transfer updates the ledger and protects the\nvacated boundary; moving code to another partial file is not a simplification.\n\nDone when every remaining hunk serves the stated fix and its preserved\ninvariant.\n\n## 2. Remove unnecessary architecture\n\nApply each supported simplification in the changed system:\n\n- **Keep one decision owner.** Move repeated caller policy into the existing\n  operation that owns the decision. Migrate affected callers and remove the old\n  implementation, export, cache, repair branch, and unreachable fallback.\n- **Use existing state and seams.** Challenge every new manager, schema, cache,\n  DTO, wrapper, and combined representation. Reuse an owner only when its\n  authority, lifetime, atomicity, thread affinity, and cleanup match.\n- **Delete forwarding machinery.** Remove wrappers that only rename or forward,\n  parallel projections of authoritative state, fake lifecycle operations used\n  only to obtain a result, and compatibility paths without a shipped contract.\n- **Preserve necessary migration.** Do not remove a migration, rollback,\n  identity, or cleanup path merely because a fresh profile passes.\n\nApply these Windows-node checks when their surface is in the diff:\n\n### WinUI state, thread, and lifetime\n\nFollow the [WinUI ownership guide](..\u002F..\u002F..\u002Fsrc\u002FOpenClaw.Tray.WinUI\u002FAGENTS.md).\nViews own layout, named-control application, and lifecycle forwarding.\nViewModels and presenters own observable state and pure projection. Services own\nIO, persistence, timers, processes, Gateway calls, and hosting. `App` remains\nthe composition root.\n\nPrefer the existing `IUiDispatcher` seam for presentation work. Do not simplify\naway dispatcher rejection, cancellation, generation checks, activation and\ndeactivation, event unsubscription, or disposal ordering when those guard\nwindow close, navigation replacement, shutdown, or stale async completion.\nDo not replace a page applicator with a presenter that merely wraps its named\ncontrols.\n\n### Packaged and unpackaged behavior\n\nTreat MSIX and unpackaged Inno\u002Fportable behavior as real product differences.\nBefore merging branches around package identity, startup, notifications,\nupdates, migration, or uninstall, inspect `PackageHelper`, `AppIdentity`, the\nmanifest, `installer.iss`, and the relevant tests. Preserve existing AUMIDs,\npackage identities, data locations, and migration compatibility.\n\nThe optional release updater remains admitted by channel before its backend is\nloaded. Packaged (MSIX), `DEV_BUILD`, and Debug builds skip it before\n`UpdateBackendLoader.Load()`. Removing that distinction or eagerly constructing\nthe vendor backend is not simplification.\n\n### Gateway, WSL, pairing, and commands\n\nUse the [connection architecture](..\u002F..\u002F..\u002Fdocs\u002FCONNECTION_ARCHITECTURE.md) for\nconnection, credential, pairing, and reconnect changes.\n`GatewayConnectionManager` remains the public lifecycle owner. Preserve\ndevice-token precedence for operator and node WebSockets, shared-token\nprecedence for interactive HTTP surfaces, explicit approval boundaries, active\ngateway generation fencing, and transaction rollback.\n\nFor an app-owned setup-managed WSL Gateway, keep supervision in the tray's\nmanaged-local owners, not in the connection layer. Never adopt, restart, stop,\nor clean an ambiguous localhost process or distro. Preserve operator stop and\ndisconnect intent, provenance gates, cancellation, rollback, and setup-owned\nstate. Read the [setup engine](..\u002F..\u002F..\u002Fdocs\u002FSETUP_ENGINE_REDESIGN.md) and\n[WSL administration boundary](..\u002F..\u002F..\u002Fdocs\u002FWSL_GATEWAY_ADMIN.md) when those\ncontracts are touched.\n\nEach command has one capability owner and authoritative registration seam.\nShared node capabilities are re-registered synchronously for every fresh\nGateway client, including reconnects, while local MCP reads the same capability\nset; `winnode` consumes the local MCP contract. Preserve deliberate transport\nexclusions: local-only `app.*` and `app.connection.*` capabilities must not be\nwidened to the remote Gateway transport, and `browser.proxy` remains\nconditionally registered. Do not add a parallel implementation or remove the\nregistry, MCP description, shipped skill, focused tests, or applicable live\ninvocation proof required by the\n[Windows node contract](..\u002F..\u002F..\u002Fdocs\u002FWINDOWS_NODE_TESTING.md#new-command-mcp-contract).\n\n### Installer, updater, and architecture\n\nInstaller, migration, cleanup, and updater paths preserve user state across\nupgrade and migration. Automatic cleanup requires positive ownership. An exact\ntarget may also be removed after explicit destructive confirmation; without\nthat override, uncertainty about migration, package presence, or ownership\nfails closed and preserves state. Keep source checks distinct from signed\ninstaller, Store, and migration runtime proof.\n\nTreat x64 and ARM64 as separate native artifact contracts. Preserve RID-specific\ndependencies, installer architecture gates, MSIX inputs, and output names. A\nhost-x64 pass does not justify deleting ARM64 handling. Use the\n[validation inventory](..\u002F..\u002F..\u002Fdocs\u002FTEST_COVERAGE.md#formal-validation-paths)\nand [release matrix](..\u002F..\u002F..\u002Fdocs\u002FRELEASING.md) for the affected packaging\nsurface.\n\n### Polish the remaining code\n\nKeep comments only for ownership, lifecycle, ordering, security, compatibility,\nor non-obvious constraints. Prefer repository types and helpers over casts,\nduplicate parsing, broad catches, arbitrary waits, and success-shaped fallback.\nKeep aliases, retries, and shims only when a named shipped contract needs them.\n\nWhen history leaves a path's purpose unclear, keep it and report the unresolved\ndecision. Do not turn simplification into a new product decision, breaking\ncontract, unrelated cleanup, or destructive state migration.\n\n## 3. Keep tests for distinct failures\n\nFor each added or changed test group and fixture helper, name the observable\nfailure it catches. Follow the\n[Windows test-audit skill](..\u002Ftest-audit\u002FSKILL.md).\n\nKeep regressions for the reported defect and distinct boundaries such as:\n\n- UI-thread access, navigation replacement, window close, cancellation, restart,\n  stale authority, disposal, and rendering;\n- packaged versus unpackaged identity, startup, migration, update, and cleanup;\n- operator versus node pairing, credential precedence, command discovery,\n  local MCP versus Gateway exposure, conditional registration, permissions,\n  invocation, and rejection;\n- WSL ownership, provenance, rollback, explicit stop intent, and process\n  cleanup;\n- x64 versus ARM64 native dependencies and packaging output.\n\nKeep source-shape or architecture guards that protect a concrete ledger closure\nor shipped package\u002Fcommand contract. A unit test does not replace distinct\nWinUI rendering, fixture transport, installer, architecture, or live Gateway\nproof.\n\nRemove duplicate same-path cases, mock echoes, incidental field-copy or wording\nassertions, tests of obsolete implementations, and scaffolding or production\nhooks used only by deleted logic. Consolidate useful cases into the existing\nowner suite without weakening assertions, real-boundary coverage, or baselines.\n\nDone when every remaining test group has a named failure and each removed test\nis demonstrably covered or obsolete.\n\n## 4. Reprove the reduced change\n\nBatch the simplification edits, inspect the complete diff again, and run the\noriginal reproduction plus the focused checks for every changed contract and\naffected consumer. Use the\n[validation planner](..\u002F..\u002F..\u002Fdocs\u002FTEST_COVERAGE.md#explain-the-validation-plan)\nand [proof skill](..\u002Fopenclaw-proof-validation\u002FSKILL.md).\n\nCode changes retain the repository's required build, Shared tests, and Tray\ntests plus targeted lanes. Documentation-only skill edits use the documentation\nand skill validators. Reuse earlier evidence only when its source, inputs,\nbinary, runtime, and asserted behavior remain unchanged. Check actual execution\ncounts and selected cases, not only exit code.\n\nDone when superseded paths are unreachable, the reduced behavior has current\nproof, and the full candidate diff has an explicit keep, simplify, remove, or\nunresolved verdict. No edit is a valid outcome when the existing shape is\njustified. Prefer net-negative code, not a deletion quota.\n\nReport:\n\n- the responsibility or machinery removed;\n- the behavior and distinct failures still protected;\n- production and test deltas against the merge base;\n- a reduction against an earlier candidate revision, reported separately from\n  the whole-change delta;\n- exact validation commands, outcomes, and proof limits;\n- necessary remaining growth and unresolved repository decisions.\n\nThen use [Windows PR preparation](..\u002Fwindows-pr-prepare\u002FSKILL.md) if a local PR\nbody or readiness handoff is requested. Do not commit, push, publish, update\nGitHub metadata, or alter a shared runtime without separate explicit authority.\n\n## Source and maintenance\n\nWindows-owned adaptation of the MIT-licensed OpenClaw\n[author-side simplification workflow](https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fdcfafb5c0016e0652771c239987baff8dbd09be0\u002F.agents\u002Fskills\u002Fpr-simplify\u002FSKILL.md).\nWindows retains its architecture ledger, WinUI lifetime rules, package and\ninstaller contracts, Gateway\u002FWSL ownership, command-surface obligations,\nmulti-architecture release behavior, and mandatory local validation.\n","# Simplify a Windows-node change\n\nUse this author-side pass after implementing a change and before preparing a\nPR. After a large repair, simplify only the new changes and the owners they\ntouch. It precedes review and never replaces it. A review-only request produces\nfindings instead of edits. Inherit the task's scope, worktree ownership,\nmutation authority, and runtime restrictions.\n\nThe diff is a proposal. Passing tests show that it works, not that every new\nowner, abstraction, compatibility path, or test is necessary.\n\nRead the root [repository instructions](..\u002F..\u002F..\u002FAGENTS.md), the nearest scoped\n`AGENTS.md`, and only the architecture guides for the changed behavior.\n\n## 1. Re-derive the smallest complete fix\n\nRecord the target merge base, current HEAD, staged and unstaged changes, and\nrelevant untracked files. Read the complete candidate diff, the reported\nbehavior, retained proof, the production owner, and its existing tests.\n\nAsk:\n\n> Starting from the base, what is the smallest complete fix using the owners\n> already present? Would I still introduce this architecture?\n\nState the defect, required invariant, and smallest complete fix in one sentence\neach. Trace every changed hunk to that outcome. Remove unrelated cleanup or\nmove it to a separately authorized change.\n\nInspect the largest new classes, services, partials, state stores, adapters, DI\nregistrations, compatibility branches, and test fixtures first. Read their\ndirect callers and relevant history before treating them as redundant. When a\nchange moves hundreds of lines, crosses multiple owners, or combines product\nbehavior with infrastructure, identify the smallest coherent stage that can\nland independently and reduce the candidate to that stage.\n\nFor files named in the [architecture ledger](..\u002F..\u002F..\u002Fdocs\u002FARCHITECTURE.md),\npreserve every `authoritative` owner and never reintroduce a `closed`\nresponsibility. A real ownership transfer updates the ledger and protects the\nvacated boundary; moving code to another partial file is not a simplification.\n\nDone when every remaining hunk serves the stated fix and its preserved\ninvariant.\n\n## 2. Remove unnecessary architecture\n\nApply each supported simplification in the changed system:\n\n- **Keep one decision owner.** Move repeated caller policy into the existing\n  operation that owns the decision. Migrate affected callers and remove the old\n  implementation, export, cache, repair branch, and unreachable fallback.\n- **Use existing state and seams.** Challenge every new manager, schema, cache,\n  DTO, wrapper, and combined representation. Reuse an owner only when its\n  authority, lifetime, atomicity, thread affinity, and cleanup match.\n- **Delete forwarding machinery.** Remove wrappers that only rename or forward,\n  parallel projections of authoritative state, fake lifecycle operations used\n  only to obtain a result, and compatibility paths without a shipped contract.\n- **Preserve necessary migration.** Do not remove a migration, rollback,\n  identity, or cleanup path merely because a fresh profile passes.\n\nApply these Windows-node checks when their surface is in the diff:\n\n### WinUI state, thread, and lifetime\n\nFollow the [WinUI ownership guide](..\u002F..\u002F..\u002Fsrc\u002FOpenClaw.Tray.WinUI\u002FAGENTS.md).\nViews own layout, named-control application, and lifecycle forwarding.\nViewModels and presenters own observable state and pure projection. Services own\nIO, persistence, timers, processes, Gateway calls, and hosting. `App` remains\nthe composition root.\n\nPrefer the existing `IUiDispatcher` seam for presentation work. Do not simplify\naway dispatcher rejection, cancellation, generation checks, activation and\ndeactivation, event unsubscription, or disposal ordering when those guard\nwindow close, navigation replacement, shutdown, or stale async completion.\nDo not replace a page applicator with a presenter that merely wraps its named\ncontrols.\n\n### Packaged and unpackaged behavior\n\nTreat MSIX and unpackaged Inno\u002Fportable behavior as real product differences.\nBefore merging branches around package identity, startup, notifications,\nupdates, migration, or uninstall, inspect `PackageHelper`, `AppIdentity`, the\nmanifest, `installer.iss`, and the relevant tests. Preserve existing AUMIDs,\npackage identities, data locations, and migration compatibility.\n\nThe optional release updater remains admitted by channel before its backend is\nloaded. Packaged (MSIX), `DEV_BUILD`, and Debug builds skip it before\n`UpdateBackendLoader.Load()`. Removing that distinction or eagerly constructing\nthe vendor backend is not simplification.\n\n### Gateway, WSL, pairing, and commands\n\nUse the [connection architecture](..\u002F..\u002F..\u002Fdocs\u002FCONNECTION_ARCHITECTURE.md) for\nconnection, credential, pairing, and reconnect changes.\n`GatewayConnectionManager` remains the public lifecycle owner. Preserve\ndevice-token precedence for operator and node WebSockets, shared-token\nprecedence for interactive HTTP surfaces, explicit approval boundaries, active\ngateway generation fencing, and transaction rollback.\n\nFor an app-owned setup-managed WSL Gateway, keep supervision in the tray's\nmanaged-local owners, not in the connection layer. Never adopt, restart, stop,\nor clean an ambiguous localhost process or distro. Preserve operator stop and\ndisconnect intent, provenance gates, cancellation, rollback, and setup-owned\nstate. Read the [setup engine](..\u002F..\u002F..\u002Fdocs\u002FSETUP_ENGINE_REDESIGN.md) and\n[WSL administration boundary](..\u002F..\u002F..\u002Fdocs\u002FWSL_GATEWAY_ADMIN.md) when those\ncontracts are touched.\n\nEach command has one capability owner and authoritative registration seam.\nShared node capabilities are re-registered synchronously for every fresh\nGateway client, including reconnects, while local MCP reads the same capability\nset; `winnode` consumes the local MCP contract. Preserve deliberate transport\nexclusions: local-only `app.*` and `app.connection.*` capabilities must not be\nwidened to the remote Gateway transport, and `browser.proxy` remains\nconditionally registered. Do not add a parallel implementation or remove the\nregistry, MCP description, shipped skill, focused tests, or applicable live\ninvocation proof required by the\n[Windows node contract](..\u002F..\u002F..\u002Fdocs\u002FWINDOWS_NODE_TESTING.md#new-command-mcp-contract).\n\n### Installer, updater, and architecture\n\nInstaller, migration, cleanup, and updater paths preserve user state across\nupgrade and migration. Automatic cleanup requires positive ownership. An exact\ntarget may also be removed after explicit destructive confirmation; without\nthat override, uncertainty about migration, package presence, or ownership\nfails closed and preserves state. Keep source checks distinct from signed\ninstaller, Store, and migration runtime proof.\n\nTreat x64 and ARM64 as separate native artifact contracts. Preserve RID-specific\ndependencies, installer architecture gates, MSIX inputs, and output names. A\nhost-x64 pass does not justify deleting ARM64 handling. Use the\n[validation inventory](..\u002F..\u002F..\u002Fdocs\u002FTEST_COVERAGE.md#formal-validation-paths)\nand [release matrix](..\u002F..\u002F..\u002Fdocs\u002FRELEASING.md) for the affected packaging\nsurface.\n\n### Polish the remaining code\n\nKeep comments only for ownership, lifecycle, ordering, security, compatibility,\nor non-obvious constraints. Prefer repository types and helpers over casts,\nduplicate parsing, broad catches, arbitrary waits, and success-shaped fallback.\nKeep aliases, retries, and shims only when a named shipped contract needs them.\n\nWhen history leaves a path's purpose unclear, keep it and report the unresolved\ndecision. Do not turn simplification into a new product decision, breaking\ncontract, unrelated cleanup, or destructive state migration.\n\n## 3. Keep tests for distinct failures\n\nFor each added or changed test group and fixture helper, name the observable\nfailure it catches. Follow the\n[Windows test-audit skill](..\u002Ftest-audit\u002FSKILL.md).\n\nKeep regressions for the reported defect and distinct boundaries such as:\n\n- UI-thread access, navigation replacement, window close, cancellation, restart,\n  stale authority, disposal, and rendering;\n- packaged versus unpackaged identity, startup, migration, update, and cleanup;\n- operator versus node pairing, credential precedence, command discovery,\n  local MCP versus Gateway exposure, conditional registration, permissions,\n  invocation, and rejection;\n- WSL ownership, provenance, rollback, explicit stop intent, and process\n  cleanup;\n- x64 versus ARM64 native dependencies and packaging output.\n\nKeep source-shape or architecture guards that protect a concrete ledger closure\nor shipped package\u002Fcommand contract. A unit test does not replace distinct\nWinUI rendering, fixture transport, installer, architecture, or live Gateway\nproof.\n\nRemove duplicate same-path cases, mock echoes, incidental field-copy or wording\nassertions, tests of obsolete implementations, and scaffolding or production\nhooks used only by deleted logic. Consolidate useful cases into the existing\nowner suite without weakening assertions, real-boundary coverage, or baselines.\n\nDone when every remaining test group has a named failure and each removed test\nis demonstrably covered or obsolete.\n\n## 4. Reprove the reduced change\n\nBatch the simplification edits, inspect the complete diff again, and run the\noriginal reproduction plus the focused checks for every changed contract and\naffected consumer. Use the\n[validation planner](..\u002F..\u002F..\u002Fdocs\u002FTEST_COVERAGE.md#explain-the-validation-plan)\nand [proof skill](..\u002Fopenclaw-proof-validation\u002FSKILL.md).\n\nCode changes retain the repository's required build, Shared tests, and Tray\ntests plus targeted lanes. Documentation-only skill edits use the documentation\nand skill validators. Reuse earlier evidence only when its source, inputs,\nbinary, runtime, and asserted behavior remain unchanged. Check actual execution\ncounts and selected cases, not only exit code.\n\nDone when superseded paths are unreachable, the reduced behavior has current\nproof, and the full candidate diff has an explicit keep, simplify, remove, or\nunresolved verdict. No edit is a valid outcome when the existing shape is\njustified. Prefer net-negative code, not a deletion quota.\n\nReport:\n\n- the responsibility or machinery removed;\n- the behavior and distinct failures still protected;\n- production and test deltas against the merge base;\n- a reduction against an earlier candidate revision, reported separately from\n  the whole-change delta;\n- exact validation commands, outcomes, and proof limits;\n- necessary remaining growth and unresolved repository decisions.\n\nThen use [Windows PR preparation](..\u002Fwindows-pr-prepare\u002FSKILL.md) if a local PR\nbody or readiness handoff is requested. Do not commit, push, publish, update\nGitHub metadata, or alter a shared runtime without separate explicit authority.\n\n## Source and maintenance\n\nWindows-owned adaptation of the MIT-licensed OpenClaw\n[author-side simplification workflow](https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fdcfafb5c0016e0652771c239987baff8dbd09be0\u002F.agents\u002Fskills\u002Fpr-simplify\u002FSKILL.md).\nWindows retains its architecture ledger, WinUI lifetime rules, package and\ninstaller contracts, Gateway\u002FWSL ownership, command-surface obligations,\nmulti-architecture release behavior, and mandatory local validation.\n",{"name":5,"description":7},"main","a4dd026cc5f85a444a0fcd05eef5b86282dbda8c",".agents\u002Fskills\u002Fpr-simplify",348,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node","https:\u002F\u002Fopenclaw.ai","https:\u002F\u002Fgithub.com\u002Fopenclaw","Your personal, open source AI assistant.","2026-11-14 02:54:19",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add openclaw\u002Fopenclaw-windows-node --skill pr-simplify",{"tool":55,"command":56},"bunx","bunx skills add openclaw\u002Fopenclaw-windows-node --skill pr-simplify",{"tool":58,"command":59},"pnpm","pnpm dlx skills add openclaw\u002Fopenclaw-windows-node --skill pr-simplify","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpr-simplify\u002FSKILL.md",true,[],[64,86,103,124,145,171],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":35},"01M6KZCXK5PCYWWW5FCVDYPAXK","retrigger-flaky-ci","Triage failed CI on a pull request or the active branch, decide whether the failures come from its changes, and rerun only failures that are unrelated. Use when asked to retrigger, rerun, or kick CI on a PR with failing checks.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fretrigger-flaky-ci\u002FSKILL.md",[],[71,72,73,74,75,76,77,18,78,79,80,81,82,83,21,84,85,22],"ci","retrigger flaky ci","pull","with","branch","unrelated","changes","pull request","active","request","decide","only","triage","rerun","failing",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":35},"01M698QMQN5TQES4R7ZPTYAZF5","technical-documentation","Write, review, or restructure Windows node documentation and agent instructions using current source, task-focused explanations, and explicit fact preservation.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftechnical-documentation\u002FSKILL.md",[],[93,94,95,96,33,97,98,99,100,32,101,102],"technical documentation","technical","documentation","agent instructions","task","review","instructions","write","preservation","source",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":114,"publishedAt":35},"01M698QJEA384YPM8R9CPZ1YFD","openclaw-testing","Choose proportional OpenClaw Windows node tests, builds, packaging checks, and runtime proof, then diagnose failures without weakening required gates.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fopenclaw-testing\u002FSKILL.md",[109],{"categoryNo":110,"categoryName":111,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[115,9,116,33,117,118,119,120,121,122,123,32,26],"openclaw testing","testing","diagnose","runtime","packaging","choose","tests","runtime proof","gates",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":133,"publishedAt":35},"01M698QH7JVVA09769ER9P2TKY","openclaw-proof-validation","Plan and collect OpenClaw Windows validation\u002Fproof: tests, rubber-duck review, UI evidence, MCP output, and gateway runtime proof.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fopenclaw-proof-validation\u002FSKILL.md",[130],{"categoryNo":131,"categoryName":132,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000023","Skill与智能体开发",[134,9,135,26,136,137,33,138,118,139,121,122,98,140,141,142,143,144],"openclaw proof validation","validation","MCP","gateway","evidence","collect","output","plan","ui evidence","ui","duck",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":156,"publishedAt":35},"01M698QFXW9PDK8YZ467MBW5P1","openclaw-debugging","Debug OpenClaw Windows Companion, setup, Gateway connection, node capabilities, packaged permissions, updates, installers, and system.run by selecting the failing boundary and proof path before changing code.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fopenclaw-debugging\u002FSKILL.md",[151],{"categoryNo":152,"categoryName":153,"taxonomyType":154,"taxonomyTypeDesc":155},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[157,9,158,85,159,160,161,162,163,32,164,165,137,33,166,167,168,169,26,170],"openclaw debugging","debugging","updates","code","capabilities","permissions","run","companion","path","system","debug","boundary","connection","setup",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":178,"publishedAt":35},"01M698QEPAAXVVCFQCZMEWMW6H","native-gateway-from-source","Run side-by-side named Gateway patches as the default for local and future cloud native-Gateway E2E on capable Windows clients. Build from npm latest, a published packaging release with -GatewayChannel Packaged, or explicit sources; select the patch with OPENCLAW_NATIVE_GATEWAY_DEV_PATCH and remove only owned instances.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fnative-gateway-from-source\u002FSKILL.md",[177],{"categoryNo":110,"categoryName":111,"taxonomyType":112,"taxonomyTypeDesc":113},[179,137,180,102,9,181,33,182,183,184,30,185,119,186,187,188,82,189,190,191,74],"native gateway from source","native","instances","sources","as","for","select","default","local","dev","e2e","cloud native","patch"]