[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M780AMARFY03BTMCT0JZHDBK":3,"skill-same:01M780AMARFY03BTMCT0JZHDBK":90},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M780AMARFY03BTMCT0JZHDBK","openclaw-control-ui-e2e",null,"Use when changing or proving OpenClaw Control UI behavior with deterministic Gateway fixtures, browser flows, rendered evidence or interaction profiling.","TheAngryPit\u002FTheAngrySkills","TheAngryPit","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7040636?v=4","01M7803EENA9ATXJ46S9268QJX","Vitor Cepeda Lopes","01M7803EF9FMF4G4420XE4DV7Y",0,"MIT","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fopenclaw-core\u002Fopenclaw-control-ui-e2e\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fopenclaw-core\u002Fopenclaw-control-ui-e2e\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: openclaw-control-ui-e2e\ndescription: \"Use when changing or proving OpenClaw Control UI behavior with deterministic Gateway fixtures, browser flows, rendered evidence or interaction profiling.\"\n---\n\n# Control Ui E2E\n\nCodex adaptation of the pinned OpenClaw source. Repository-specific commands apply only to a verified OpenClaw checkout; portable debugger commands apply to their selected process.\n\n## Repository and UI boundary\nUse only in the selected OpenClaw checkout. Read root and scoped UI instructions, inspect current package scripts and the relevant UI owners before choosing commands. Use the packaged upstream workflow for test shape and mock patterns. Follow [visual proof](references\u002Fupstream\u002Freferences\u002Fvisual-proof.md), [interaction profiling](references\u002Fupstream\u002Freferences\u002Finteraction-performance.md) and [Run Inspector evidence](references\u002Fupstream\u002Freferences\u002Frun-inspector.md) for those branches. Resolve repository-owned imports in that checkout.\n\nFor substantial UI changes, follow the upstream visual-proof guidance and prepare a fixture-driven state gallery covering relevant normal, empty, loading, error, permission, long-content and expanded\u002Fselected states. Label proposed\u002Fstatic states, preserve a baseline for comparisons, and give each example a stable feedback identifier. Keep gallery\u002Frecording output task-local unless explicitly selected for commit.\n\nUse native Codex file\u002Fpanel\u002Fbrowser tools for presentation and inspection; OpenClaw tools named in upstream material do not become Codex capabilities. Follow applicable effective-html\u002FImpeccable guidance. Never replace required real interaction with a screenshot of a mock.\n\nRun focused Vitest\u002FPlaywright proof through existing repository commands. Separate mocked-Gateway boundary evidence from real Gateway\u002Fproduct evidence and rendered-client evidence. Creating an isolated test state is different from touching the operator's live Gateway, account or data; preserve the applicable authorization.\n\nInspect the actual requested output and relevant wide\u002Fnarrow states through an authorized surface, fix concrete defects and inspect again. If native rendering access is denied, preserve that refusal and report visual proof pending. Do not upload recordings without scoped publication authority and disclosure review.\n\n## Visual evidence and recordings\n\nPair before\u002Fafter captures with deterministic behavior assertions for appearance changes. Keep final captures separate from the evolving gallery and inspect the actual screenshots and finalized video before reporting them. If a recorder fails or shows unexpected behavior, stop, fix the behavior, add or update a regression test, then record again. Keep generated media task-local and do not upload it without scoped publication authority.\n\n## Interaction profiling\n\nFor responsiveness work, define named actions, visible-result assertions and expected Gateway requests across the relevant desktop\u002Fmobile, keyboard, loading\u002Ferror, permission and large-data states. Use the production UI build with matching `serverBuildId` and `serverVersion`; measure each action from before interaction through its asserted visible outcome and requests, separately from navigation and deferred background work. Begin report-only. One successful sample proves collection and behavior, not stable latency; do not treat route visits or test-file counts as interaction coverage or report automation-to-assertion wall time as INP. See the packaged [interaction profiling procedure](references\u002Fupstream\u002Freferences\u002Finteraction-performance.md) for capture and artifact requirements.\n\n## Run Inspector evidence\n\nCount evidence only when the rendered panel has an unambiguous matching run and execution identity and the selected receipt is present. The requested URL alone is not proof. Preserve the caller's Chat page and unsent draft, and never manufacture a terminal transcript key from a DOM selector or history row. Use the packaged [Run Inspector capture details](references\u002Fupstream\u002Freferences\u002Frun-inspector.md) for selectors and lifecycle.\n\n## Selective installation\n\nNo mandatory installed companion from this pack is required. Checkout\u002Fruntime prerequisites and the conditional source references still apply.\n\n## Source procedures and boundary\n\nRead [the packaged upstream entrypoint](references\u002Fupstream\u002FSKILL.source.md) when using this workflow; its supporting files remain beside it. This root owns Codex invocation, target resolution and authorization. Upstream examples are reference procedures, not grants of access, installation, deployment, publication or another model\u002Fprovider. Use native Codex tools where capable and preserve an actual refusal. The operator's chosen model, project instructions and source-trust policy remain authoritative.\n\nFor repository-owned dependencies and original relative links, use [the source link map](references\u002Fupstream-link-map.json) against the verified checkout or its pinned GitHub reference. The pack does not claim that a linked release\u002Fchannel skill or runtime is installed. Inspect the current owning source before executing a version-sensitive example.\n\n[Provenance and adaptation record](PROVENANCE.md) identifies the source commit, retained resources and changes.\n","# Control Ui E2E\n\nCodex adaptation of the pinned OpenClaw source. Repository-specific commands apply only to a verified OpenClaw checkout; portable debugger commands apply to their selected process.\n\n## Repository and UI boundary\nUse only in the selected OpenClaw checkout. Read root and scoped UI instructions, inspect current package scripts and the relevant UI owners before choosing commands. Use the packaged upstream workflow for test shape and mock patterns. Follow [visual proof](references\u002Fupstream\u002Freferences\u002Fvisual-proof.md), [interaction profiling](references\u002Fupstream\u002Freferences\u002Finteraction-performance.md) and [Run Inspector evidence](references\u002Fupstream\u002Freferences\u002Frun-inspector.md) for those branches. Resolve repository-owned imports in that checkout.\n\nFor substantial UI changes, follow the upstream visual-proof guidance and prepare a fixture-driven state gallery covering relevant normal, empty, loading, error, permission, long-content and expanded\u002Fselected states. Label proposed\u002Fstatic states, preserve a baseline for comparisons, and give each example a stable feedback identifier. Keep gallery\u002Frecording output task-local unless explicitly selected for commit.\n\nUse native Codex file\u002Fpanel\u002Fbrowser tools for presentation and inspection; OpenClaw tools named in upstream material do not become Codex capabilities. Follow applicable effective-html\u002FImpeccable guidance. Never replace required real interaction with a screenshot of a mock.\n\nRun focused Vitest\u002FPlaywright proof through existing repository commands. Separate mocked-Gateway boundary evidence from real Gateway\u002Fproduct evidence and rendered-client evidence. Creating an isolated test state is different from touching the operator's live Gateway, account or data; preserve the applicable authorization.\n\nInspect the actual requested output and relevant wide\u002Fnarrow states through an authorized surface, fix concrete defects and inspect again. If native rendering access is denied, preserve that refusal and report visual proof pending. Do not upload recordings without scoped publication authority and disclosure review.\n\n## Visual evidence and recordings\n\nPair before\u002Fafter captures with deterministic behavior assertions for appearance changes. Keep final captures separate from the evolving gallery and inspect the actual screenshots and finalized video before reporting them. If a recorder fails or shows unexpected behavior, stop, fix the behavior, add or update a regression test, then record again. Keep generated media task-local and do not upload it without scoped publication authority.\n\n## Interaction profiling\n\nFor responsiveness work, define named actions, visible-result assertions and expected Gateway requests across the relevant desktop\u002Fmobile, keyboard, loading\u002Ferror, permission and large-data states. Use the production UI build with matching `serverBuildId` and `serverVersion`; measure each action from before interaction through its asserted visible outcome and requests, separately from navigation and deferred background work. Begin report-only. One successful sample proves collection and behavior, not stable latency; do not treat route visits or test-file counts as interaction coverage or report automation-to-assertion wall time as INP. See the packaged [interaction profiling procedure](references\u002Fupstream\u002Freferences\u002Finteraction-performance.md) for capture and artifact requirements.\n\n## Run Inspector evidence\n\nCount evidence only when the rendered panel has an unambiguous matching run and execution identity and the selected receipt is present. The requested URL alone is not proof. Preserve the caller's Chat page and unsent draft, and never manufacture a terminal transcript key from a DOM selector or history row. Use the packaged [Run Inspector capture details](references\u002Fupstream\u002Freferences\u002Frun-inspector.md) for selectors and lifecycle.\n\n## Selective installation\n\nNo mandatory installed companion from this pack is required. Checkout\u002Fruntime prerequisites and the conditional source references still apply.\n\n## Source procedures and boundary\n\nRead [the packaged upstream entrypoint](references\u002Fupstream\u002FSKILL.source.md) when using this workflow; its supporting files remain beside it. This root owns Codex invocation, target resolution and authorization. Upstream examples are reference procedures, not grants of access, installation, deployment, publication or another model\u002Fprovider. Use native Codex tools where capable and preserve an actual refusal. The operator's chosen model, project instructions and source-trust policy remain authoritative.\n\nFor repository-owned dependencies and original relative links, use [the source link map](references\u002Fupstream-link-map.json) against the verified checkout or its pinned GitHub reference. The pack does not claim that a linked release\u002Fchannel skill or runtime is installed. Inspect the current owning source before executing a version-sensitive example.\n\n[Provenance and adaptation record](PROVENANCE.md) identifies the source commit, retained resources and changes.\n",{"name":5,"description":7},"main","f31e1d2df163b90a48e30d0a3df67285f6641418","skills\u002Fengineering\u002Fopenclaw-core\u002Fopenclaw-control-ui-e2e",1,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills","https:\u002F\u002Fgithub.com\u002FTheAngryPit","www.vitorcepedalopes.com","Creative Director | Executive Producer | Storyteller | Narrative Worlds & Creative Production Systems\r\nFounder @TheHive-Mind ","2026-11-14 21:48:38",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add TheAngryPit\u002FTheAngrySkills --skill openclaw-control-ui-e2e",{"tool":40,"command":41},"bunx","bunx skills add TheAngryPit\u002FTheAngrySkills --skill openclaw-control-ui-e2e",{"tool":43,"command":44},"pnpm","pnpm dlx skills add TheAngryPit\u002FTheAngrySkills --skill openclaw-control-ui-e2e","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fopenclaw-core\u002Fopenclaw-control-ui-e2e\u002FSKILL.md",true,[48,54,58,62,66,70,74,78,82,86],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"agents\u002Fopenai.yaml","REFERENCE","参考文档",295,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fopenclaw-core\u002Fopenclaw-control-ui-e2e\u002Fagents\u002Fopenai.yaml",{"path":55,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":16},"LICENSE","许可证",1076,{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"PROVENANCE.md",2785,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fopenclaw-core\u002Fopenclaw-control-ui-e2e\u002FPROVENANCE.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fupstream-link-map.json",4100,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fopenclaw-core\u002Fopenclaw-control-ui-e2e\u002Freferences\u002Fupstream-link-map.json",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fupstream\u002Fagents\u002Fopenai.yaml",264,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fopenclaw-core\u002Fopenclaw-control-ui-e2e\u002Freferences\u002Fupstream\u002Fagents\u002Fopenai.yaml",{"path":71,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fupstream\u002Freferences\u002Finteraction-performance.md",4688,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fopenclaw-core\u002Fopenclaw-control-ui-e2e\u002Freferences\u002Fupstream\u002Freferences\u002Finteraction-performance.md",{"path":75,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fupstream\u002Freferences\u002Frun-inspector.md",1331,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fopenclaw-core\u002Fopenclaw-control-ui-e2e\u002Freferences\u002Fupstream\u002Freferences\u002Frun-inspector.md",{"path":79,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fupstream\u002Freferences\u002Fvisual-proof.md",5404,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fopenclaw-core\u002Fopenclaw-control-ui-e2e\u002Freferences\u002Fupstream\u002Freferences\u002Fvisual-proof.md",{"path":83,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fupstream\u002FSKILL.source.md",3911,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fopenclaw-core\u002Fopenclaw-control-ui-e2e\u002Freferences\u002Fupstream\u002FSKILL.source.md",{"path":87,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":88,"sourceHtmlUrl":89},"UPSTREAM.json",1771,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fopenclaw-core\u002Fopenclaw-control-ui-e2e\u002FUPSTREAM.json",[91,98,105,112,119,126],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":20},"01M782GJ4CTPNKZN0WXTASXXZ4","X MCP guide","ALWAYS read this before using any X tool (the X plugin, any X MCP, or Grok Bot's built-in public X reads) and again on any X error. X tools are included in Grok Bot at no cost: never estimate costs, check credits, or tell the user to buy credits. tools=0 \u002F user-X-* not found is a setup failure, not a paywall. Covers Spaces, communities, and Lists (reads and list writes), X Chat (XChat, inbox, DMs, unread, message requests, Chat PIN, juicebox, xchat_lite: clone xchat-grokbot-helper yourself and decrypt locally), scheduled X calls (schedule_call, list_scheduled_calls and the other call tools), and livestreams (stream sources, broadcasts, scheduled broadcasts, broadcast chat, moderators, mutes). Chat, call, livestream, Spaces, or Lists tools missing while other X tools work: reconnect the X plugin.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fx\u002Fskills\u002Fx-api-mcp-guide\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":20},"01M782GBW77901ESC9PD3XAM6V","X Money guide","Read this before the first X Money action in a session and again on any X Money error, refusal, or missing capability. Covers the approval rule for every action that moves money (always ask, every time, no exceptions), how the connection works (connection code plus passkey in the X app), how to guide the user through connect, reconnect, and revoke at x.com\u002Fi\u002Fmoney\u002Fsettings\u002Fconnections, and what each failure message means.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fx-money\u002Fskills\u002Fx-money-guide\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":20},"01M782G7CMYD2JSVT3RX81QRB8","google-slides","Build and edit Google Slides through the google-slides MCP tools - slides, grids of cards and columns, text boxes, shapes, images, tables, styling, layout inspection, and per-slide PNG rendering. Use when creating a deck, laying out slide elements, matching a template, or verifying how a slide looks.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fgoogle-slides\u002Fskills\u002Fgoogle-slides\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":20},"01M782G4DDAJ4SMGJEF13HTX69","google-sheets","Build and edit Google Sheets with the google-sheets tools - values, formatting, charts, conditional formatting, structure, validation, named and protected ranges. Use when creating a spreadsheet or dashboard, formatting cells, adding or fixing charts, or reorganizing tabs and rows.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fgoogle-sheets\u002Fskills\u002Fgoogle-sheets\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":20},"01M782G1F8QNMNKRSY6M3Y0QG6","google-drive","Work with Google Drive through its MCP tools - search, read, create, organize, share, comment, and export files. Use when creating files in specific folders, moving or renaming, converting Markdown\u002FCSV into Docs\u002FSheets, managing comments, or exporting a rendered PDF.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fgoogle-drive\u002Fskills\u002Fgoogle-drive\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":20},"01M782FYVJ5XTP2R0B446RRYTX","google-docs","Author and edit Google Docs with the google-docs tools - structured writing, character and paragraph styling, lists, tables, images, headers\u002Ffooters. Use when creating a formatted document, editing document content, or applying styles.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fgoogle-docs\u002Fskills\u002Fgoogle-docs\u002FSKILL.md",[],[]]