[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79JYRTRK3DB17F7FFNDACQY":3,"skill-same:01M79JYRTRK3DB17F7FFNDACQY":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":42},"01M79JYRTRK3DB17F7FFNDACQY","control-ui",null,"Operate and troubleshoot the OpenClaw Control UI: navigate connected clients, organize sessions, build session dashboards, and handle direct or Tailscale-hosted Gateways.","leon36000\u002FOPSYS-AI","leon36000","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F216249790?v=4","01M79JWJK00J10J79XZA3G4KH0","01M79JWJKTT8J3C7PZ0TX7X4PQ",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fleon36000\u002FOPSYS-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fcontrol-ui\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: control-ui\ndescription: \"Operate and troubleshoot the OpenClaw Control UI: navigate connected clients, organize sessions, build session dashboards, and handle direct or Tailscale-hosted Gateways.\"\nuser-invocable: true\n---\n\n# Control UI\n\nUse OpenClaw's typed UI tools for state and layout. Use browser automation only\nto inspect or interact with rendered pixels.\n\n## Mental model\n\n- A sidebar item is a **session**, not a dashboard page.\n- Each session owns one board. The board contains tabs and widgets.\n- Pinning a session keeps it in the sidebar. Sessions with a stored board appear\n  in the `\u002Fdashboards` gallery.\n- `screen` changes connected Control UI layout and navigation. It does not read\n  the page or take screenshots.\n- `sessions_list` finds sessions. `sessions` renames, groups, pins, or archives\n  them. It does not edit board content.\n- `dashboard` reads and arranges the current session's board and registered\n  plugin widgets. `show_widget` authors or updates custom HTML\u002FSVG widgets.\n\nDo not replace these operations with shell calls or raw Gateway RPC when the\ntyped tool exists.\n\n## Start safely\n\n1. Identify the target session and whether the Control UI is local\u002Fdirect or\n   published through Tailscale or another HTTPS proxy.\n   - If the user wants a dedicated sidebar dashboard, choose or create its\n     visible session before authoring any widget. A tab is only a partition\n     inside one session's board; it never creates a sidebar row.\n   - If the current turn is running in a temporary or parent session, hand the\n     dashboard task to the intended visible session first. Board widgets are\n     keyed by session and cannot be moved to another session afterward.\n2. Read current state before changing it:\n   - use `sessions_list` to resolve the session;\n   - use `dashboard` with `action: \"read\"` for the current session;\n   - inspect existing tabs, stable widget names, owners, sizes, and panel layout.\n3. If the task targets another session's board, move the work into that session.\n   Dashboard tools intentionally operate on the current session.\n\nRead [hosting.md](references\u002Fhosting.md) before opening or repairing a remote\nControl UI. Read [dashboards.md](references\u002Fdashboards.md) before creating or\nrestructuring a board.\nUse the `visualize` skill for widget composition, libraries, interactive code\nexplanations, and dashboard content. Keep session and board organization here.\n\n## Navigate and arrange the UI\n\nUse `screen` for deterministic client commands:\n\n- `navigate` to open a session by `sessionKey`;\n- `sidebar_show` \u002F `sidebar_hide` for the session sidebar;\n- `split_right` \u002F `split_down`, `focus`, and `close_pane` for panes;\n- `terminal_show` \u002F `terminal_hide` and `browser_show` \u002F `browser_hide` for\n  docked panels.\n\n`screen` broadcasts to every connected Control UI that advertises UI commands;\nit cannot select one browser tab. Confirm the blast radius when several clients\nmay be open. If it reports no capable client, ask the user to open the Control\nUI and retry.\n\nUse the in-app browser or an available browser-control tool when the task needs\nDOM inspection, clicking, typing, or screenshots. Reuse the existing signed-in\nControl UI tab when possible.\n\n## Build a session dashboard\n\n1. Call `dashboard read`. Reuse suitable tabs and widget names.\n2. Create or rename tabs with `tab_create` \u002F `tab_update`; use short lowercase\n   slug IDs.\n3. Add content with the correct owner:\n   - native text, metrics, tables, charts, and links: `show_widget` with\n     `pin: true` and `report`;\n   - self-contained custom HTML\u002FSVG or registered-source content:\n     `show_widget` with `pin: true`;\n   - trusted plugin widgets: `dashboard widget_put` with an advertised\n     `pluginKind`.\n     Do not embed Grafana or another external application in an `\u003Ciframe>` inside\n     `show_widget`; widget sandboxes reject child-frame URLs and navigation. Use\n     an ordinary user-clicked link to open the application, fetch an exact HTTPS\n     API through declared `capabilities.netOrigins`, use a Gateway data binding,\n     or install\u002Fuse a trusted plugin widget instead.\n4. Use a stable `name` when calling `show_widget`. Reusing the same name with\n   new `widget_code` updates the widget in place.\n5. Arrange with `widget_move`, `widget_resize`, and tab reordering. Prefer size\n   presets and board order over pixel placement.\n6. Pin the current session with `sessions patch` when it should stay prominent.\n7. Call `dashboard focus_tab` to show the intended tab in the dashboard side\n   panel. If no Control UI is connected, the command returns unavailable; have\n   the user open the session and retry.\n8. Choose the presentation after focusing the tab. `set_presentation` with\n   `presentation: \"expanded\"` expands the dashboard; `\"split\"` shows it beside\n   chat in the current panel layout. The human can use\n   **Expand side panel** for a full-width dashboard, **Collapse** to bring chat\n   back, or close the panel for chat alone.\n\nNever create a fake top-level page for a dashboard. For a dedicated dashboard,\nuse a dedicated session, pin that session, and build its board from inside it.\n\n## Update without breaking the board\n\n- Read first and mutate the smallest unit.\n- Keep stable tab IDs and widget names unless replacement is intentional.\n- Do not change a widget's content owner in place. Remove it, then recreate it\n  with the new owner or registered kind.\n- Capability grants are bound to exact widget bytes and revision. Changed\n  content may require approval again.\n- Resetting a conversation preserves its board. Deleting the session deletes\n  the board.\n\n## Verify the result\n\nUse two layers of proof:\n\n1. **State:** `dashboard read` shows the expected tabs, widgets, names, owners,\n   order, and sizes; `sessions_list` shows the expected session\n   metadata.\n2. **Rendered UI:** open the actual Control UI, confirm the correct session and\n   dashboard panel, then inspect or screenshot the widget frame. Exercise any\n   important controls.\n\nAn HTTP 200 for the shell or widget route is transport proof, not visual proof.\nDo not claim the dashboard works until the sandboxed frame renders.\nFor widgets that fetch live data, exercise that fetch from the rendered frame.\nA host-side `curl` does not prove the browser received the required capability\ngrant or accepted the endpoint's CORS and mixed-content policy.\nIf no browser-control or connected-client inspection is available, report the\ndashboard as published but visually unverified instead of claiming success.\n\n## Recovery order\n\nWhen a widget is blank or stale:\n\n1. confirm the expected session, tab, widget name, and revision with\n   `dashboard read`;\n2. classify the hosting path using [hosting.md](references\u002Fhosting.md);\n3. verify the Control UI origin, the separate widget sandbox origin, and the\n   protocol used on every reverse-proxy hop;\n4. if widget JavaScript reports `Failed to fetch`, verify its exact HTTPS origin\n   is declared and granted in `capabilities.netOrigins`, then check browser CORS\n   and mixed-content errors;\n5. after a Gateway restart or routing change, republish\u002Fupdate the widget so the\n   browser receives a fresh ticketed frame URL;\n6. reload the Control UI and verify the rendered frame, not only route status.\n","# Control UI\n\nUse OpenClaw's typed UI tools for state and layout. Use browser automation only\nto inspect or interact with rendered pixels.\n\n## Mental model\n\n- A sidebar item is a **session**, not a dashboard page.\n- Each session owns one board. The board contains tabs and widgets.\n- Pinning a session keeps it in the sidebar. Sessions with a stored board appear\n  in the `\u002Fdashboards` gallery.\n- `screen` changes connected Control UI layout and navigation. It does not read\n  the page or take screenshots.\n- `sessions_list` finds sessions. `sessions` renames, groups, pins, or archives\n  them. It does not edit board content.\n- `dashboard` reads and arranges the current session's board and registered\n  plugin widgets. `show_widget` authors or updates custom HTML\u002FSVG widgets.\n\nDo not replace these operations with shell calls or raw Gateway RPC when the\ntyped tool exists.\n\n## Start safely\n\n1. Identify the target session and whether the Control UI is local\u002Fdirect or\n   published through Tailscale or another HTTPS proxy.\n   - If the user wants a dedicated sidebar dashboard, choose or create its\n     visible session before authoring any widget. A tab is only a partition\n     inside one session's board; it never creates a sidebar row.\n   - If the current turn is running in a temporary or parent session, hand the\n     dashboard task to the intended visible session first. Board widgets are\n     keyed by session and cannot be moved to another session afterward.\n2. Read current state before changing it:\n   - use `sessions_list` to resolve the session;\n   - use `dashboard` with `action: \"read\"` for the current session;\n   - inspect existing tabs, stable widget names, owners, sizes, and panel layout.\n3. If the task targets another session's board, move the work into that session.\n   Dashboard tools intentionally operate on the current session.\n\nRead [hosting.md](references\u002Fhosting.md) before opening or repairing a remote\nControl UI. Read [dashboards.md](references\u002Fdashboards.md) before creating or\nrestructuring a board.\nUse the `visualize` skill for widget composition, libraries, interactive code\nexplanations, and dashboard content. Keep session and board organization here.\n\n## Navigate and arrange the UI\n\nUse `screen` for deterministic client commands:\n\n- `navigate` to open a session by `sessionKey`;\n- `sidebar_show` \u002F `sidebar_hide` for the session sidebar;\n- `split_right` \u002F `split_down`, `focus`, and `close_pane` for panes;\n- `terminal_show` \u002F `terminal_hide` and `browser_show` \u002F `browser_hide` for\n  docked panels.\n\n`screen` broadcasts to every connected Control UI that advertises UI commands;\nit cannot select one browser tab. Confirm the blast radius when several clients\nmay be open. If it reports no capable client, ask the user to open the Control\nUI and retry.\n\nUse the in-app browser or an available browser-control tool when the task needs\nDOM inspection, clicking, typing, or screenshots. Reuse the existing signed-in\nControl UI tab when possible.\n\n## Build a session dashboard\n\n1. Call `dashboard read`. Reuse suitable tabs and widget names.\n2. Create or rename tabs with `tab_create` \u002F `tab_update`; use short lowercase\n   slug IDs.\n3. Add content with the correct owner:\n   - native text, metrics, tables, charts, and links: `show_widget` with\n     `pin: true` and `report`;\n   - self-contained custom HTML\u002FSVG or registered-source content:\n     `show_widget` with `pin: true`;\n   - trusted plugin widgets: `dashboard widget_put` with an advertised\n     `pluginKind`.\n     Do not embed Grafana or another external application in an `\u003Ciframe>` inside\n     `show_widget`; widget sandboxes reject child-frame URLs and navigation. Use\n     an ordinary user-clicked link to open the application, fetch an exact HTTPS\n     API through declared `capabilities.netOrigins`, use a Gateway data binding,\n     or install\u002Fuse a trusted plugin widget instead.\n4. Use a stable `name` when calling `show_widget`. Reusing the same name with\n   new `widget_code` updates the widget in place.\n5. Arrange with `widget_move`, `widget_resize`, and tab reordering. Prefer size\n   presets and board order over pixel placement.\n6. Pin the current session with `sessions patch` when it should stay prominent.\n7. Call `dashboard focus_tab` to show the intended tab in the dashboard side\n   panel. If no Control UI is connected, the command returns unavailable; have\n   the user open the session and retry.\n8. Choose the presentation after focusing the tab. `set_presentation` with\n   `presentation: \"expanded\"` expands the dashboard; `\"split\"` shows it beside\n   chat in the current panel layout. The human can use\n   **Expand side panel** for a full-width dashboard, **Collapse** to bring chat\n   back, or close the panel for chat alone.\n\nNever create a fake top-level page for a dashboard. For a dedicated dashboard,\nuse a dedicated session, pin that session, and build its board from inside it.\n\n## Update without breaking the board\n\n- Read first and mutate the smallest unit.\n- Keep stable tab IDs and widget names unless replacement is intentional.\n- Do not change a widget's content owner in place. Remove it, then recreate it\n  with the new owner or registered kind.\n- Capability grants are bound to exact widget bytes and revision. Changed\n  content may require approval again.\n- Resetting a conversation preserves its board. Deleting the session deletes\n  the board.\n\n## Verify the result\n\nUse two layers of proof:\n\n1. **State:** `dashboard read` shows the expected tabs, widgets, names, owners,\n   order, and sizes; `sessions_list` shows the expected session\n   metadata.\n2. **Rendered UI:** open the actual Control UI, confirm the correct session and\n   dashboard panel, then inspect or screenshot the widget frame. Exercise any\n   important controls.\n\nAn HTTP 200 for the shell or widget route is transport proof, not visual proof.\nDo not claim the dashboard works until the sandboxed frame renders.\nFor widgets that fetch live data, exercise that fetch from the rendered frame.\nA host-side `curl` does not prove the browser received the required capability\ngrant or accepted the endpoint's CORS and mixed-content policy.\nIf no browser-control or connected-client inspection is available, report the\ndashboard as published but visually unverified instead of claiming success.\n\n## Recovery order\n\nWhen a widget is blank or stale:\n\n1. confirm the expected session, tab, widget name, and revision with\n   `dashboard read`;\n2. classify the hosting path using [hosting.md](references\u002Fhosting.md);\n3. verify the Control UI origin, the separate widget sandbox origin, and the\n   protocol used on every reverse-proxy hop;\n4. if widget JavaScript reports `Failed to fetch`, verify its exact HTTPS origin\n   is declared and granted in `capabilities.netOrigins`, then check browser CORS\n   and mixed-content errors;\n5. after a Gateway restart or routing change, republish\u002Fupdate the widget so the\n   browser receives a fresh ticketed frame URL;\n6. reload the Control UI and verify the rendered frame, not only route status.\n",{"name":5,"description":7,"user-invocable":23},true,"main","54d89d355555ba29c51a05828bb2ee9b8abbfc1d","core\u002Fskills\u002Fcontrol-ui","https:\u002F\u002Fgithub.com\u002Fleon36000\u002FOPSYS-AI","https:\u002F\u002Fgithub.com\u002Fleon36000","2026-11-08 05:46:02",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":23},[32,35,38],{"tool":33,"command":34},"npx","npx skills add leon36000\u002FOPSYS-AI --skill control-ui",{"tool":36,"command":37},"bunx","bunx skills add leon36000\u002FOPSYS-AI --skill control-ui",{"tool":39,"command":40},"pnpm","pnpm dlx skills add leon36000\u002FOPSYS-AI --skill control-ui","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fleon36000\u002FOPSYS-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fcontrol-ui\u002FSKILL.md",[43,49],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"references\u002Fdashboards.md","REFERENCE","参考文档",4921,"https:\u002F\u002Fgithub.com\u002Fleon36000\u002FOPSYS-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fcontrol-ui\u002Freferences\u002Fdashboards.md",{"path":50,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fhosting.md",4843,"https:\u002F\u002Fgithub.com\u002Fleon36000\u002FOPSYS-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fcontrol-ui\u002Freferences\u002Fhosting.md",[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M79K66JYY28KMDVMJ4M1RBT7","procedure-demo","Procédure de test.","https:\u002F\u002Fgithub.com\u002Fleon36000\u002FOPSYS-AI\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fdepartements\u002Fm09-demo\u002Fskills\u002Fprocedure-demo\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M79K62M77K68EJYYT1HGZZYR","traiter-un-signal-critique","Procédure pour lister les signaux critiques d'une affaire et proposer leur prise en compte ou leur clôture, qui restent des décisions humaines, et pour proposer de lier une session à une affaire.","https:\u002F\u002Fgithub.com\u002Fleon36000\u002FOPSYS-AI\u002Fblob\u002Fmain\u002Fdepartments\u002Fm10-memoire\u002Fskills\u002Ftraiter-un-signal-critique\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M79K5XV1PC7Q699VC05WPVEX","preflight-contexte-suffisant","Procédure PREFLIGHT pour vérifier qu'un dossier de contexte (événement, résumé, preuves, impact, prochaine action, références de décisions) est suffisant avant une action importante, et pour consommer un Work Completion Trigger de M4.","https:\u002F\u002Fgithub.com\u002Fleon36000\u002FOPSYS-AI\u002Fblob\u002Fmain\u002Fdepartments\u002Fm10-memoire\u002Fskills\u002Fpreflight-contexte-suffisant\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M79K5TB07Q63XCV00FSX4AR0","journaliser-une-decision","Procédure pour journaliser une décision motivée au registre Affaires et obtenir sa référence vérifiable, ou pour signaler puis arbitrer une révision entre deux souvenirs, sans jamais fusionner ni muter un maillon existant.","https:\u002F\u002Fgithub.com\u002Fleon36000\u002FOPSYS-AI\u002Fblob\u002Fmain\u002Fdepartments\u002Fm10-memoire\u002Fskills\u002Fjournaliser-une-decision\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M79K5PB7JFBETB3A08ACKXXS","etat-consolide-et-contradictions","Procédure pour ingérer un snapshot d'un module, reconstruire l'état consolidé de l'entreprise et présenter ses contradictions internes sans jamais les résoudre ni en inventer la cause.","https:\u002F\u002Fgithub.com\u002Fleon36000\u002FOPSYS-AI\u002Fblob\u002Fmain\u002Fdepartments\u002Fm09-strategic-intelligence\u002Fskills\u002Fetat-consolide-et-contradictions\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M79K5K368MQEQA5TZ2FRQGMD","briefing-du-matin","Procédure pour produire le briefing du matin (décisions en attente, alertes M8, faits de la veille, manques) pour une date de référence donnée, lire ce qu'il n'a pas pu afficher, et lire les alertes de mesure de M8 avec leurs preuves, sans jamais rien y inventer, y décider ni y ajouter de diagnostic.","https:\u002F\u002Fgithub.com\u002Fleon36000\u002FOPSYS-AI\u002Fblob\u002Fmain\u002Fdepartments\u002Fm09-strategic-intelligence\u002Fskills\u002Fbriefing-du-matin\u002FSKILL.md",[],[]]