[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M698QMQN5TQES4R7ZPTYAZF5":3,"skill-same:01M698QMQN5TQES4R7ZPTYAZF5":64},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":40,"ownerHtmlUrl":41,"ownerBlogUrl":40,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M698QMQN5TQES4R7ZPTYAZF5","technical-documentation",null,"Write, review, or restructure Windows node documentation and agent instructions using current source, task-focused explanations, and explicit fact preservation.","openclaw\u002Fopenclaw-windows-node","openclaw","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F252820863?v=4","01M698P3FSAZ6B4R928ZF19KPT","01M698Q6SND6RHZDPP8ZM0NSP7",2198,"MIT","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftechnical-documentation\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29],"technical documentation","documentation","technical","review","windows","node","write","instructions","task","preservation","source","agent instructions","2026-11-10 10:12:30",false,"---\nname: technical-documentation\ndescription: Write, review, or restructure Windows node documentation and agent instructions using current source, task-focused explanations, and explicit fact preservation.\n---\n\n# Windows technical documentation\n\nUse for repository documentation, contributor guidance, and agent instruction\nfiles in the OpenClaw Windows node repository. This is a brownfield workflow:\npreserve current ownership, terminology, and validation rather than importing a\ngeneric documentation system. A request to audit or plan remains read-only;\nrewriting requires authorization.\n\nDo not turn a scoped documentation task into a repository-wide audit, code\ncleanup, UI-copy rewrite, or release operation.\n\n## Define the reader and outcome\n\nClassify the work as build, review, or refactor. Name the primary reader and the\nobservable result they need before choosing the page type.\n\n| Page | First useful result |\n|---|---|\n| Overview | The reader chooses the appropriate Windows surface or guide |\n| Guide | One recommended workflow reaches an observable outcome |\n| Reference | A precise contract answers a specific lookup |\n| Troubleshooting | A symptom leads to a safe check, interpretation, and next action |\n| Architecture | A contributor finds the authoritative owner and preserved invariant |\n| Agent instruction | A task routes to its owner, constraints, and required evidence |\n\nState what the page covers and what it does not. Explain the normal path before\nalternatives. Put prerequisites, consent, and safety boundaries before the\naffected command. Move rare cases and exhaustive contracts to named references\nwithout removing facts that still matter.\n\n## Load only the owning context\n\nRead [documentation ownership](..\u002F..\u002F..\u002Fdocs\u002FAGENTS.md), then the target page and\nthe source that owns its claims. Use this map to select context rather than\npreloading the documentation collection.\n\n| Surface | Read first | Verify against |\n|---|---|---|\n| Product overview, install, update, uninstall | [README](..\u002F..\u002F..\u002FREADME.md), [setup](..\u002F..\u002F..\u002Fdocs\u002FSETUP.md) | `installer.iss`, updater code, uninstall scripts, current release assets |\n| WinUI Settings, Workspace, Command Center, or tray UX | [WinUI ownership](..\u002F..\u002F..\u002Fsrc\u002FOpenClaw.Tray.WinUI\u002FAGENTS.md), [design system](..\u002F..\u002F..\u002FDESIGN.md) | XAML\u002FC#, localized `.resw` resources, accessibility guidance |\n| Gateway, pairing, operator, node, or credentials | [operator and node concepts](..\u002F..\u002F..\u002Fdocs\u002FOPERATOR_NODE_CONCEPTS.md), [connection architecture](..\u002F..\u002F..\u002Fdocs\u002FCONNECTION_ARCHITECTURE.md) | connection owners, protocol contracts, focused tests |\n| Node mode, permissions, sandbox, MCP, or `winnode` | [Windows node testing](..\u002F..\u002F..\u002Fdocs\u002FWINDOWS_NODE_TESTING.md), [MCP mode](..\u002F..\u002F..\u002Fdocs\u002FMCP_MODE.md) | capability registration, `McpToolBridge`, command tests |\n| Local WSL Gateway setup or administration | [onboarding](..\u002F..\u002F..\u002Fdocs\u002FONBOARDING_WIZARD.md), [WSL Gateway admin](..\u002F..\u002F..\u002Fdocs\u002FWSL_GATEWAY_ADMIN.md) | setup engine, setup UI, installed Gateway contract |\n| Installer, MSIX, Store, version, or release flow | [releasing](..\u002F..\u002F..\u002Fdocs\u002FRELEASING.md), [versioning](..\u002F..\u002F..\u002Fdocs\u002FVERSIONING.md), [Store submission](..\u002F..\u002F..\u002Fdocs\u002FMICROSOFT_STORE.md) | build scripts, workflows, manifests, packaging-repository ownership |\n| Logs, support context, or connection diagnostics | [setup troubleshooting](..\u002F..\u002F..\u002Fdocs\u002FSETUP.md#troubleshooting), [MCP connection diagnostics](..\u002F..\u002F..\u002Fdocs\u002FMCP_MODE.md#current-command-surface) | activation routes and diagnostics services that produce the data |\n| Architecture ownership or a moved responsibility | [architecture ledger](..\u002F..\u002F..\u002Fdocs\u002FARCHITECTURE.md) | named production owner, callers, tests, closed ledger rows |\n\nFollow linked architecture context only when the documented contract crosses\nthat boundary.\n\n## Use Windows terminology precisely\n\n- **OpenClaw Windows Hub** names this repository and Windows product area.\n  **OpenClaw Companion** names the installed desktop app.\n- **Gateway**, **local WSL gateway**, **operator**, **node**, **pairing**,\n  **reapproval**, and **Node Mode** have distinct meanings. Use\n  [operator and node concepts](..\u002F..\u002F..\u002Fdocs\u002FOPERATOR_NODE_CONCEPTS.md) rather\n  than collapsing them into \"the app is connected.\"\n- Local MCP is a loopback transport and may work without Gateway pairing. Never\n  use local MCP success as proof of operator or node connectivity.\n- Use the current native surface names. Copy visible labels and capitalization\n  from localized resources rather than normalizing an old screenshot, plan, or\n  prose name.\n- Write architecture display names as **x64** and **ARM64**. Use runtime\n  identifiers such as `win-x64` and `win-arm64` exactly. Claim both\n  architectures only for a build, installer, portable, MSIX, Store, or proof\n  surface whose current owner actually supports both.\n\n## Respect authored and generated boundaries\n\n- Repository Markdown, `AGENTS.md`, and `.agents\u002Fskills` are authored guidance.\n  Native UI copy remains owned by `.resw` resources and their callers; a docs\n  edit must not create a competing UI string source.\n- Edit a generator, manifest, workflow, or authoritative source instead of\n  generated in-repository output such as build artifacts, copied skills, or\n  derived catalogs. Preserve documented release-owner edits to generated\n  GitHub release bodies, including the classification marker in\n  [RELEASING.md](..\u002F..\u002F..\u002Fdocs\u002FRELEASING.md), and require separate publication\n  authority.\n- Setup injects a managed Windows-node section into a Gateway workspace\n  `AGENTS.md`. Document that contract in this repository; do not hand-edit a\n  user's generated managed block as the repository fix.\n- Preserve the full [`winnode` command reference](..\u002Fwinnode\u002FSKILL.md). It ships\n  beside the CLI as `skill.md` and is drift-checked against capability\n  registration. Splitting or shortening it is a packaging and command-contract\n  change, not an editorial shortcut.\n- Keep [ARCHITECTURE.md](..\u002F..\u002F..\u002Fdocs\u002FARCHITECTURE.md) as the single ownership\n  ledger. A scoped guide links to it instead of creating another ledger.\n- Keep editable Excalidraw sources and rendered SVGs paired. Do not introduce\n  Mermaid or a separate diagram publication path.\n\n## Verify every behavior-sensitive claim\n\n- Check commands, flags, defaults, settings locations, architecture support,\n  owners, errors, and recovery behavior against current source and tests.\n- Separate current behavior, released behavior, historical measurements,\n  proposals, and required proof. Include a date and source revision for\n  historical evidence when known.\n- Do not infer GitHub release publication, Microsoft Store availability,\n  signing, rollout, Gateway compatibility, or x64\u002FARM64 parity from a successful\n  build or workflow definition.\n- Distinguish the app-owned locked-down WSL Gateway from an existing local,\n  remote, or native Gateway. Commands run in Windows PowerShell and commands run\n  as the WSL `openclaw` or `root` user are not interchangeable.\n- A fixture, source assertion, local MCP result, or unit test proves only its\n  named boundary. It does not establish real Gateway pairing, signed installer\n  behavior, Store rollout, WinUI rendering, or native sandbox containment.\n- For diagnostics, start from the visible symptom. Prefer redacted support\n  context, bounded log excerpts, and credential-free status commands. Never\n  paste tokens, full private configuration, unrelated logs, or machine-specific\n  private state.\n- Run repository scripts and contributor commands from the repository root.\n  User-facing commands must not assume a checkout. Use bounded placeholders and\n  an expected result, and mark shell transitions explicitly when a workflow\n  enters WSL.\n\nFor a rewrite or split, use the\n[fact-preservation procedure](references\u002Frefactoring.md).\n\n## Validate and hand off\n\nRun the repository documentation checks from the repository root:\n\n```powershell\n.\\scripts\\validate-docs.ps1\n.\\scripts\\validate-agent-skills.ps1\n.\\scripts\\test-agent-skills-validator.ps1\ngit diff --check\n```\n\nUse [formal test selection](..\u002F..\u002F..\u002Fdocs\u002FTEST_COVERAGE.md#formal-validation-paths)\nfor executable changes, UI copy, generators, packaging, or shipped command\nreferences. Ordinary prose does not require a full app build or native runtime\nproof. Do not claim a command, installer, Gateway path, or UI flow was exercised\nwhen only its source or documentation was checked.\n\nReport the page purpose, audience and outcome, corrected claims, destinations of\nmoved facts, source owners checked, authored\u002Fgenerated boundary decisions,\nvalidation results, and unresolved ownership questions. Publication needs\nseparate authority.\n\n## Source and maintenance\n\nWindows-owned guidance, adapted from the MIT-licensed OpenClaw\n[technical-documentation skill](https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fa1fb89994ae04c434def18e8d45d81abdf672364\u002F.agents\u002Fskills\u002Ftechnical-documentation\u002FSKILL.md),\n[documentation overlay](https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fa1fb89994ae04c434def18e8d45d81abdf672364\u002F.agents\u002Fskills\u002Ftechnical-documentation\u002Freferences\u002Fopenclaw.md),\nand [refactoring workflow](https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fa1fb89994ae04c434def18e8d45d81abdf672364\u002F.agents\u002Fskills\u002Fopenclaw-refactor-docs\u002FSKILL.md).\nThis is not a synchronized copy. Windows owns its terminology, commands, proof\nrequirements, GitHub Markdown conventions, release surfaces, and paired\nExcalidraw\u002FSVG diagrams.\n","# Windows technical documentation\n\nUse for repository documentation, contributor guidance, and agent instruction\nfiles in the OpenClaw Windows node repository. This is a brownfield workflow:\npreserve current ownership, terminology, and validation rather than importing a\ngeneric documentation system. A request to audit or plan remains read-only;\nrewriting requires authorization.\n\nDo not turn a scoped documentation task into a repository-wide audit, code\ncleanup, UI-copy rewrite, or release operation.\n\n## Define the reader and outcome\n\nClassify the work as build, review, or refactor. Name the primary reader and the\nobservable result they need before choosing the page type.\n\n| Page | First useful result |\n|---|---|\n| Overview | The reader chooses the appropriate Windows surface or guide |\n| Guide | One recommended workflow reaches an observable outcome |\n| Reference | A precise contract answers a specific lookup |\n| Troubleshooting | A symptom leads to a safe check, interpretation, and next action |\n| Architecture | A contributor finds the authoritative owner and preserved invariant |\n| Agent instruction | A task routes to its owner, constraints, and required evidence |\n\nState what the page covers and what it does not. Explain the normal path before\nalternatives. Put prerequisites, consent, and safety boundaries before the\naffected command. Move rare cases and exhaustive contracts to named references\nwithout removing facts that still matter.\n\n## Load only the owning context\n\nRead [documentation ownership](..\u002F..\u002F..\u002Fdocs\u002FAGENTS.md), then the target page and\nthe source that owns its claims. Use this map to select context rather than\npreloading the documentation collection.\n\n| Surface | Read first | Verify against |\n|---|---|---|\n| Product overview, install, update, uninstall | [README](..\u002F..\u002F..\u002FREADME.md), [setup](..\u002F..\u002F..\u002Fdocs\u002FSETUP.md) | `installer.iss`, updater code, uninstall scripts, current release assets |\n| WinUI Settings, Workspace, Command Center, or tray UX | [WinUI ownership](..\u002F..\u002F..\u002Fsrc\u002FOpenClaw.Tray.WinUI\u002FAGENTS.md), [design system](..\u002F..\u002F..\u002FDESIGN.md) | XAML\u002FC#, localized `.resw` resources, accessibility guidance |\n| Gateway, pairing, operator, node, or credentials | [operator and node concepts](..\u002F..\u002F..\u002Fdocs\u002FOPERATOR_NODE_CONCEPTS.md), [connection architecture](..\u002F..\u002F..\u002Fdocs\u002FCONNECTION_ARCHITECTURE.md) | connection owners, protocol contracts, focused tests |\n| Node mode, permissions, sandbox, MCP, or `winnode` | [Windows node testing](..\u002F..\u002F..\u002Fdocs\u002FWINDOWS_NODE_TESTING.md), [MCP mode](..\u002F..\u002F..\u002Fdocs\u002FMCP_MODE.md) | capability registration, `McpToolBridge`, command tests |\n| Local WSL Gateway setup or administration | [onboarding](..\u002F..\u002F..\u002Fdocs\u002FONBOARDING_WIZARD.md), [WSL Gateway admin](..\u002F..\u002F..\u002Fdocs\u002FWSL_GATEWAY_ADMIN.md) | setup engine, setup UI, installed Gateway contract |\n| Installer, MSIX, Store, version, or release flow | [releasing](..\u002F..\u002F..\u002Fdocs\u002FRELEASING.md), [versioning](..\u002F..\u002F..\u002Fdocs\u002FVERSIONING.md), [Store submission](..\u002F..\u002F..\u002Fdocs\u002FMICROSOFT_STORE.md) | build scripts, workflows, manifests, packaging-repository ownership |\n| Logs, support context, or connection diagnostics | [setup troubleshooting](..\u002F..\u002F..\u002Fdocs\u002FSETUP.md#troubleshooting), [MCP connection diagnostics](..\u002F..\u002F..\u002Fdocs\u002FMCP_MODE.md#current-command-surface) | activation routes and diagnostics services that produce the data |\n| Architecture ownership or a moved responsibility | [architecture ledger](..\u002F..\u002F..\u002Fdocs\u002FARCHITECTURE.md) | named production owner, callers, tests, closed ledger rows |\n\nFollow linked architecture context only when the documented contract crosses\nthat boundary.\n\n## Use Windows terminology precisely\n\n- **OpenClaw Windows Hub** names this repository and Windows product area.\n  **OpenClaw Companion** names the installed desktop app.\n- **Gateway**, **local WSL gateway**, **operator**, **node**, **pairing**,\n  **reapproval**, and **Node Mode** have distinct meanings. Use\n  [operator and node concepts](..\u002F..\u002F..\u002Fdocs\u002FOPERATOR_NODE_CONCEPTS.md) rather\n  than collapsing them into \"the app is connected.\"\n- Local MCP is a loopback transport and may work without Gateway pairing. Never\n  use local MCP success as proof of operator or node connectivity.\n- Use the current native surface names. Copy visible labels and capitalization\n  from localized resources rather than normalizing an old screenshot, plan, or\n  prose name.\n- Write architecture display names as **x64** and **ARM64**. Use runtime\n  identifiers such as `win-x64` and `win-arm64` exactly. Claim both\n  architectures only for a build, installer, portable, MSIX, Store, or proof\n  surface whose current owner actually supports both.\n\n## Respect authored and generated boundaries\n\n- Repository Markdown, `AGENTS.md`, and `.agents\u002Fskills` are authored guidance.\n  Native UI copy remains owned by `.resw` resources and their callers; a docs\n  edit must not create a competing UI string source.\n- Edit a generator, manifest, workflow, or authoritative source instead of\n  generated in-repository output such as build artifacts, copied skills, or\n  derived catalogs. Preserve documented release-owner edits to generated\n  GitHub release bodies, including the classification marker in\n  [RELEASING.md](..\u002F..\u002F..\u002Fdocs\u002FRELEASING.md), and require separate publication\n  authority.\n- Setup injects a managed Windows-node section into a Gateway workspace\n  `AGENTS.md`. Document that contract in this repository; do not hand-edit a\n  user's generated managed block as the repository fix.\n- Preserve the full [`winnode` command reference](..\u002Fwinnode\u002FSKILL.md). It ships\n  beside the CLI as `skill.md` and is drift-checked against capability\n  registration. Splitting or shortening it is a packaging and command-contract\n  change, not an editorial shortcut.\n- Keep [ARCHITECTURE.md](..\u002F..\u002F..\u002Fdocs\u002FARCHITECTURE.md) as the single ownership\n  ledger. A scoped guide links to it instead of creating another ledger.\n- Keep editable Excalidraw sources and rendered SVGs paired. Do not introduce\n  Mermaid or a separate diagram publication path.\n\n## Verify every behavior-sensitive claim\n\n- Check commands, flags, defaults, settings locations, architecture support,\n  owners, errors, and recovery behavior against current source and tests.\n- Separate current behavior, released behavior, historical measurements,\n  proposals, and required proof. Include a date and source revision for\n  historical evidence when known.\n- Do not infer GitHub release publication, Microsoft Store availability,\n  signing, rollout, Gateway compatibility, or x64\u002FARM64 parity from a successful\n  build or workflow definition.\n- Distinguish the app-owned locked-down WSL Gateway from an existing local,\n  remote, or native Gateway. Commands run in Windows PowerShell and commands run\n  as the WSL `openclaw` or `root` user are not interchangeable.\n- A fixture, source assertion, local MCP result, or unit test proves only its\n  named boundary. It does not establish real Gateway pairing, signed installer\n  behavior, Store rollout, WinUI rendering, or native sandbox containment.\n- For diagnostics, start from the visible symptom. Prefer redacted support\n  context, bounded log excerpts, and credential-free status commands. Never\n  paste tokens, full private configuration, unrelated logs, or machine-specific\n  private state.\n- Run repository scripts and contributor commands from the repository root.\n  User-facing commands must not assume a checkout. Use bounded placeholders and\n  an expected result, and mark shell transitions explicitly when a workflow\n  enters WSL.\n\nFor a rewrite or split, use the\n[fact-preservation procedure](references\u002Frefactoring.md).\n\n## Validate and hand off\n\nRun the repository documentation checks from the repository root:\n\n```powershell\n.\\scripts\\validate-docs.ps1\n.\\scripts\\validate-agent-skills.ps1\n.\\scripts\\test-agent-skills-validator.ps1\ngit diff --check\n```\n\nUse [formal test selection](..\u002F..\u002F..\u002Fdocs\u002FTEST_COVERAGE.md#formal-validation-paths)\nfor executable changes, UI copy, generators, packaging, or shipped command\nreferences. Ordinary prose does not require a full app build or native runtime\nproof. Do not claim a command, installer, Gateway path, or UI flow was exercised\nwhen only its source or documentation was checked.\n\nReport the page purpose, audience and outcome, corrected claims, destinations of\nmoved facts, source owners checked, authored\u002Fgenerated boundary decisions,\nvalidation results, and unresolved ownership questions. Publication needs\nseparate authority.\n\n## Source and maintenance\n\nWindows-owned guidance, adapted from the MIT-licensed OpenClaw\n[technical-documentation skill](https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fa1fb89994ae04c434def18e8d45d81abdf672364\u002F.agents\u002Fskills\u002Ftechnical-documentation\u002FSKILL.md),\n[documentation overlay](https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fa1fb89994ae04c434def18e8d45d81abdf672364\u002F.agents\u002Fskills\u002Ftechnical-documentation\u002Freferences\u002Fopenclaw.md),\nand [refactoring workflow](https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fa1fb89994ae04c434def18e8d45d81abdf672364\u002F.agents\u002Fskills\u002Fopenclaw-refactor-docs\u002FSKILL.md).\nThis is not a synchronized copy. Windows owns its terminology, commands, proof\nrequirements, GitHub Markdown conventions, release surfaces, and paired\nExcalidraw\u002FSVG diagrams.\n",{"name":5,"description":7},"main","a4dd026cc5f85a444a0fcd05eef5b86282dbda8c",".agents\u002Fskills\u002Ftechnical-documentation",346,"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-13 02:36:55",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add openclaw\u002Fopenclaw-windows-node --skill technical-documentation",{"tool":50,"command":51},"bunx","bunx skills add openclaw\u002Fopenclaw-windows-node --skill technical-documentation",{"tool":53,"command":54},"pnpm","pnpm dlx skills add openclaw\u002Fopenclaw-windows-node --skill technical-documentation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftechnical-documentation\u002FSKILL.md",true,[58],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Frefactoring.md","REFERENCE","参考文档",2988,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftechnical-documentation\u002Freferences\u002Frefactoring.md",[65,90,109,130,151,177],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":30},"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",[],[72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89],"ci","retrigger flaky ci","pull","with","branch","unrelated","changes","pr","pull request","active","request","decide","only","triage","use","rerun","failing","when",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":30},"01M698QKPXJ8ZG34MYHPPCAT4T","pr-simplify","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.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpr-simplify\u002FSKILL.md",[],[97,79,98,22,99,100,101,102,103,86,89,104,23,105,106,107,108],"pr simplify","simplify","platform","slop","remove","complete","fix","change","preparation","implementation","proof","contracts",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":120,"publishedAt":30},"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",[115],{"categoryNo":116,"categoryName":117,"taxonomyType":118,"taxonomyTypeDesc":119},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[121,9,122,22,123,124,125,126,127,128,129,23,107],"openclaw testing","testing","diagnose","runtime","packaging","choose","tests","runtime proof","gates",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":139,"publishedAt":30},"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",[136],{"categoryNo":137,"categoryName":138,"taxonomyType":118,"taxonomyTypeDesc":119},"01JBSEEDCAT000000000000023","Skill与智能体开发",[140,9,141,107,142,143,22,144,124,145,127,128,21,146,147,148,149,150],"openclaw proof validation","validation","MCP","gateway","evidence","collect","output","plan","ui evidence","ui","duck",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":162,"publishedAt":30},"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",[157],{"categoryNo":158,"categoryName":159,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[163,9,164,88,165,166,167,168,169,23,170,171,143,22,172,173,174,175,107,176],"openclaw debugging","debugging","updates","code","capabilities","permissions","run","companion","path","system","debug","boundary","connection","setup",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":184,"publishedAt":30},"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",[183],{"categoryNo":116,"categoryName":117,"taxonomyType":118,"taxonomyTypeDesc":119},[185,143,186,28,9,187,22,188,189,190,101,191,125,192,193,194,84,195,196,197,75],"native gateway from source","native","instances","sources","as","for","select","default","local","dev","e2e","cloud native","patch"]