[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M698RNDJ70XSP96KTVGDJM97":3,"skill-same:01M698RNDJ70XSP96KTVGDJM97":69},{"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},"01M698RNDJ70XSP96KTVGDJM97","openclaw-update",null,"Route routine updates of an existing local or remote OpenClaw Gateway to its installation owner, with automatic session recovery. Defer to deployment-specific skills when available.","openclaw\u002Fopenclaw","openclaw","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F252820863?v=4","01M698P3FSAZ6B4R928ZF19KPT","01M698PDMDRVH56MV30D253NFP",394352,"MIT","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fopenclaw-update\u002FSKILL.md",[],[18,9,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"openclaw update","update","when","routine","automatic","Existing","updates","with","remote","local","installation","route","session","recovery","gateway","deployment","session recovery","2026-11-10 10:12:30",false,"---\nname: openclaw-update\ndescription: \"Route routine updates of an existing local or remote OpenClaw Gateway to its installation owner, with automatic session recovery. Defer to deployment-specific skills when available.\"\n---\n\n# Update OpenClaw\n\nUse for general requests to update an existing Claw\u002FGateway. Select the existing update workflow; do not create another deployer or scheduler. Release validation, publication, new installations, and unrelated hosts are outside this workflow.\n\n## Resolve the owner\n\nIdentify the host, runtime user, profile\u002Fstate root, service, running executable\u002Frelease, and update owner from operator configuration and live inspection. The current repository or shell CLI may belong to another install. Keep private access details and state out of public artifacts.\n\nRead the owner runbook and choose the matching workflow:\n\n| Installation                               | Update path                                                                                                                                                |\n| ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| Canonical live main checkout and macOS app | [openclaw-live-updater](..\u002Fopenclaw-live-updater\u002FSKILL.md).                                                                                                |\n| Operator-configured Team server            | [update-team-server](..\u002Fupdate-team-server\u002FSKILL.md).                                                                                                      |\n| Other managed deployments                  | Deployment-specific skill\u002Frunbook and existing owner, including containers and declarative installations.                                                  |\n| Standard package or single-user source     | [Updating](..\u002F..\u002F..\u002Fdocs\u002Finstall\u002Fupdating.md) and the [update CLI contract](..\u002F..\u002F..\u002Fdocs\u002Fcli\u002Fupdate.md), using the owning CLI on the target host\u002Fprofile. |\n\nFollow the selected workflow's commands, locks, backup\u002Fmigration requirements, recovery, notification policy, and cleanup. Do not apply standard CLI updates inside a separately managed release or running container, mutate files used by a live Gateway, or overwrite dirty checkouts.\n\n“Latest” preserves the configured channel; explicitly requested “latest main” selects the development source flow (`--channel dev` for the standard CLI). Preview the target and report the actual serving SHA: development preflight can select an older buildable commit. Do not auto-accept unapproved downgrades or plugin capability changes.\n\n## Interruption and recovery\n\nAn update request includes routine restart and bounded interruption, subject to deployment policy. **Eligible sessions resume automatically. Do not ask again solely because agents, replies, or tasks are active.** Use the owner's graceful drain and recovery-preserving interruption.\n\nTask cancellation, session aborts, and queue clearing can discard work; do not use them to manufacture idleness or manually replay recovered turns. PTYs do not survive. [Restart recovery](..\u002F..\u002F..\u002Fdocs\u002Fgateway\u002Frestart-recovery.md) owns recovery behavior and limits.\n\nIf the owner lacks controlled interruption, report or repair that gap within scope. Do not invent force flags, bypass persistence\u002Fcompatibility gates, or repeat the interruption approval question.\n\n## Follow through\n\nRetain ownership of an explicit update request across busy deferral, failure, rollback, and recovery until the selected owner's full acceptance or a concrete external\u002Faccess blocker requiring outside action. Respect user pauses and cancellations. Before ending with work pending, establish an active completion\u002Fobservation path or supported continuation through that owner; return without waiting for another prompt. If no continuation path exists, state that blocker instead of promising one. An existing cadence or restored old process alone does not complete the request.\n\nKeep deployment-specific recovery and target selection with the linked owner. Qualify suspected issues at the actual failing path, improve updater guidance for confirmed durable gaps, and repair confirmed defects within the authorized scope. Use isolated worktrees and subagents where useful; test and review repairs, then land them through normal PR review, CI, and `scripts\u002Fpr` landing. Continue through verified update acceptance after landing; persistence does not authorize bypassing locks, safeguards, or branch protection.\n\n## Verify\n\nUse the owner's verification to prove the intended version\u002Fcommit is serving, RPC\u002Fhealth and configured channels work, and UI\u002Fassets load through actual ingress when enabled. Inspect startup\u002Frecovery errors without exposing secrets. Read the native deployment result separately from an observer or wrapper exit status: a successful observer can report a deferred or failed update. A build, handoff acknowledgement, or healthy old process is not completion. Keep detailed receipts private; report the result, next action or exact blocker in one to three short, friendly lines, with a short SHA only when useful and no repeated logs or full hashes.\n","# Update OpenClaw\n\nUse for general requests to update an existing Claw\u002FGateway. Select the existing update workflow; do not create another deployer or scheduler. Release validation, publication, new installations, and unrelated hosts are outside this workflow.\n\n## Resolve the owner\n\nIdentify the host, runtime user, profile\u002Fstate root, service, running executable\u002Frelease, and update owner from operator configuration and live inspection. The current repository or shell CLI may belong to another install. Keep private access details and state out of public artifacts.\n\nRead the owner runbook and choose the matching workflow:\n\n| Installation                               | Update path                                                                                                                                                |\n| ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| Canonical live main checkout and macOS app | [openclaw-live-updater](..\u002Fopenclaw-live-updater\u002FSKILL.md).                                                                                                |\n| Operator-configured Team server            | [update-team-server](..\u002Fupdate-team-server\u002FSKILL.md).                                                                                                      |\n| Other managed deployments                  | Deployment-specific skill\u002Frunbook and existing owner, including containers and declarative installations.                                                  |\n| Standard package or single-user source     | [Updating](..\u002F..\u002F..\u002Fdocs\u002Finstall\u002Fupdating.md) and the [update CLI contract](..\u002F..\u002F..\u002Fdocs\u002Fcli\u002Fupdate.md), using the owning CLI on the target host\u002Fprofile. |\n\nFollow the selected workflow's commands, locks, backup\u002Fmigration requirements, recovery, notification policy, and cleanup. Do not apply standard CLI updates inside a separately managed release or running container, mutate files used by a live Gateway, or overwrite dirty checkouts.\n\n“Latest” preserves the configured channel; explicitly requested “latest main” selects the development source flow (`--channel dev` for the standard CLI). Preview the target and report the actual serving SHA: development preflight can select an older buildable commit. Do not auto-accept unapproved downgrades or plugin capability changes.\n\n## Interruption and recovery\n\nAn update request includes routine restart and bounded interruption, subject to deployment policy. **Eligible sessions resume automatically. Do not ask again solely because agents, replies, or tasks are active.** Use the owner's graceful drain and recovery-preserving interruption.\n\nTask cancellation, session aborts, and queue clearing can discard work; do not use them to manufacture idleness or manually replay recovered turns. PTYs do not survive. [Restart recovery](..\u002F..\u002F..\u002Fdocs\u002Fgateway\u002Frestart-recovery.md) owns recovery behavior and limits.\n\nIf the owner lacks controlled interruption, report or repair that gap within scope. Do not invent force flags, bypass persistence\u002Fcompatibility gates, or repeat the interruption approval question.\n\n## Follow through\n\nRetain ownership of an explicit update request across busy deferral, failure, rollback, and recovery until the selected owner's full acceptance or a concrete external\u002Faccess blocker requiring outside action. Respect user pauses and cancellations. Before ending with work pending, establish an active completion\u002Fobservation path or supported continuation through that owner; return without waiting for another prompt. If no continuation path exists, state that blocker instead of promising one. An existing cadence or restored old process alone does not complete the request.\n\nKeep deployment-specific recovery and target selection with the linked owner. Qualify suspected issues at the actual failing path, improve updater guidance for confirmed durable gaps, and repair confirmed defects within the authorized scope. Use isolated worktrees and subagents where useful; test and review repairs, then land them through normal PR review, CI, and `scripts\u002Fpr` landing. Continue through verified update acceptance after landing; persistence does not authorize bypassing locks, safeguards, or branch protection.\n\n## Verify\n\nUse the owner's verification to prove the intended version\u002Fcommit is serving, RPC\u002Fhealth and configured channels work, and UI\u002Fassets load through actual ingress when enabled. Inspect startup\u002Frecovery errors without exposing secrets. Read the native deployment result separately from an observer or wrapper exit status: a successful observer can report a deferred or failed update. A build, handoff acknowledgement, or healthy old process is not completion. Keep detailed receipts private; report the result, next action or exact blocker in one to three short, friendly lines, with a short SHA only when useful and no repeated logs or full hashes.\n",{"name":5,"description":7},"main","df9d3240e52a533ea176e98cf047ed6b40cf37d6",".agents\u002Fskills\u002Fopenclaw-update",82861,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw","https:\u002F\u002Fopenclaw.ai","https:\u002F\u002Fgithub.com\u002Fopenclaw","Your personal, open source AI assistant.","2026-11-12 03:01:25",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add openclaw\u002Fopenclaw --skill openclaw-update",{"tool":55,"command":56},"bunx","bunx skills add openclaw\u002Fopenclaw --skill openclaw-update",{"tool":58,"command":59},"pnpm","pnpm dlx skills add openclaw\u002Fopenclaw --skill openclaw-update","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fopenclaw-update\u002FSKILL.md",true,[63],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"agents\u002Fopenai.yaml","REFERENCE","参考文档",116,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fopenclaw-update\u002Fagents\u002Fopenai.yaml",[70,76,99,116,138,162],{"skillNo":71,"name":72,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":35},"01M698VP84FNM6G9MR1HPX7MF7","lobster","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fextensions\u002Flobster\u002FSKILL.md",[],[72],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":35},"01M698YY8QGQ7S8TJNKJG6VTPH","xurl","xurl CLI for authenticated X posts, replies, reads\u002Fsearch, DMs, media upload, followers, auth status, or raw v2 API calls.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Fxurl\u002FSKILL.md",[],[78,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98],"for","api","calls","replies","posts","upload","tap","install","brew","node","Media","search","npm","status","auth","cli",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":35},"01M698YWT1CJ0WK88WB909R9RT","weather","Current weather and forecasts with web_fetch, falling back to wttr.in curl for locations, rain, temperature, travel planning.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Fweather\u002FSKILL.md",[],[101,106,107,90,108,91,109,110,111,112,113,114,83,115,25],"travel planning","travel","fetch","curl","https","help","planning","web","back","temperature",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":127,"publishedAt":35},"01M698YV2Q0R0JJKAWGFS21K0N","visualize","Create inline visuals for code and explanations, or author persistent OpenClaw dashboard widgets with show_widget.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Fvisualize\u002FSKILL.md",[122],{"categoryNo":123,"categoryName":124,"taxonomyType":125,"taxonomyTypeDesc":126},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[118,128,129,130,131,83,25,132,133,134,135,136,9,137],"widgets","openclaw dashboard","author","inline","show","code","create","visuals","dashboard","widget",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":152,"publishedAt":35},"01M698YS2TRJH9ENG28HD9CD87","trello","Manage Trello boards, lists, and cards via the Trello REST API.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Ftrello\u002FSKILL.md",[144,149],{"categoryNo":145,"categoryName":146,"taxonomyType":147,"taxonomyTypeDesc":148},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":150,"categoryName":151,"taxonomyType":125,"taxonomyTypeDesc":126},"01JBSEEDCAT000000000000030","开发工程师",[140,110,153,154,155,156,157,158,90,91,159,109,84,160,161],"cloud","manage","via","rest api","token","atlassian","jq","REST","developer",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":35},"01M698YQ9Q3M4W78EWV2KSCSVW","tmux","Control tmux sessions\u002Fpanes for interactive CLIs: list, capture output, send keys, paste text, monitor prompts.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Ftmux\u002FSKILL.md",[],[164,90,169,170,83,171,172,173,174,175,176,177,91,178,179,180,181,182,183],"send","darwin","keys","paste","output","control","prompts","interactive","list","capture","panes","text","monitor","sessions","linux"]