Kubeshark Installer
kubeshark/kubeshark
Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.
Route routine updates of an existing local or remote OpenClaw Gateway to its installation owner, with automatic session recovery.
Install Openclaw Update
$ npx skills add openclaw/openclaw --skill openclaw-update -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openclaw/openclaw openclaw-update --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/openclaw/openclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/openclaw-update .claude/skills/openclaw-update && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "openclaw-update" agent skill from https://github.com/openclaw/openclaw/tree/main/.agents/skills/openclaw-update into .claude/skills/openclaw-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-update", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/openclaw/openclaw/tree/main/.agents/skills/openclaw-updateType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add openclaw/openclaw --skill openclaw-update -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openclaw/openclaw openclaw-update --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openclaw/openclaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/openclaw-update .agents/skills/openclaw-update && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "openclaw-update" agent skill from https://github.com/openclaw/openclaw/tree/main/.agents/skills/openclaw-update into .agents/skills/openclaw-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-update", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openclaw/openclaw --skill openclaw-update -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openclaw/openclaw openclaw-update --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openclaw/openclaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/openclaw-update .cursor/skills/openclaw-update && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "openclaw-update" agent skill from https://github.com/openclaw/openclaw/tree/main/.agents/skills/openclaw-update into .cursor/skills/openclaw-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-update", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/openclaw/openclaw.git --path .agents/skills/openclaw-update--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add openclaw/openclaw --skill openclaw-update -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openclaw/openclaw openclaw-update --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openclaw/openclaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/openclaw-update .gemini/skills/openclaw-update && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "openclaw-update" agent skill from https://github.com/openclaw/openclaw/tree/main/.agents/skills/openclaw-update into .gemini/skills/openclaw-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-update", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install openclaw/openclaw openclaw-updateInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add openclaw/openclaw --skill openclaw-update -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/openclaw/openclaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/openclaw-update .github/skills/openclaw-update && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "openclaw-update" agent skill from https://github.com/openclaw/openclaw/tree/main/.agents/skills/openclaw-update into .github/skills/openclaw-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-update", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openclaw/openclaw --skill openclaw-update -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install openclaw/openclaw openclaw-update --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openclaw/openclaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/openclaw-update .opencode/skills/openclaw-update && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "openclaw-update" agent skill from https://github.com/openclaw/openclaw/tree/main/.agents/skills/openclaw-update into .opencode/skills/openclaw-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-update", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
openclaw-update- GitHub stars
- 392k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 662 words
- Files
- 2
- Skills in repo
- 93
- Repo updated
- First seen
- Licence
- MIT
At a glance
Route routine updates of an existing local or remote OpenClaw Gateway to its installation owner, with automatic session recovery.
- Tasks that involve Deployment
- SKILL.md covers Resolve the owner, Interruption and recovery, Follow through and Verify
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Openclaw Update is an agent skill from openclaw/openclaw. 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.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in DevOps & Cloud, covering Deployment. The repository describes itself as: The AI that really does things. Any OS. Any Platform. The lobster way. 🦞. The licence is MIT.
When your agent uses it
- Tasks that involve Deployment
Example prompts
- “/openclaw-update”
What it can do on your machine
Read from SKILL.md and the folder at commit 1eb5970. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Openclaw Update loads about 1.5k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 662 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from openclaw/openclaw at commit 1eb5970, republished under its MIT licence (© openclaw). 662 words, ~1,483 tokens.
Download SKILL.mdSave it as
.claude/skills/openclaw-update/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- openclaw-update
- description
- 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.
Update OpenClaw
Use for general requests to update an existing Claw/Gateway. Select the existing update workflow; do not create another deployer or scheduler. Release validation, publication, new installations, and unrelated hosts are outside this workflow.
Resolve the owner
Identify the host, runtime user, profile/state root, service, running executable/release, 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.
Read the owner runbook and choose the matching workflow:
| Installation | Update path |
|---|---|
| Canonical live main checkout and macOS app | openclaw-live-updater. |
| Operator-configured Team server | update-team-server. |
| Other managed deployments | Deployment-specific skill/runbook and existing owner, including containers and declarative installations. |
| Standard package or single-user source | Updating and the update CLI contract, using the owning CLI on the target host/profile. |
Follow the selected workflow's commands, locks, backup/migration requirements, recovery, and cleanup. For the operator-configured Team server, only its designated Team Server · Night Watch owner executes live deployment, restart, cutover, rollback, and recovery through the canonical controller. Do not delegate those actions or designate an external executor through coordination/admission. Other workers may investigate, test, review, and land fixes, then hand results to Night Watch; an already-running external operation requires the linked Team skill's safe exact-transaction handback, never a duplicate controller or blind kill. The linked Team skill also owns notification timing and content; report non-action outcomes and blockers privately to the requesting user, not to Team. 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.
“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.
Interruption and recovery
An 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.
Task 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 owns recovery behavior and limits.
If the owner lacks controlled interruption, report or repair that gap within scope. Do not invent force flags, bypass persistence/compatibility gates, or repeat the interruption approval question.
Show full SKILL.md (252 more words)Show less
Follow through
Retain ownership of an explicit update request across busy deferral, failure, rollback, and recovery until the selected owner's full acceptance or a concrete external/access blocker requiring outside action. Respect user pauses and cancellations. Before ending with work pending, establish an active completion/observation 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.
Keep 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/pr landing. Continue through verified update acceptance after landing; persistence does not authorize bypassing locks, safeguards, or branch protection.
Verify
Use the owner's verification to prove the intended version/commit is serving, RPC/health and configured channels work, and UI/assets load through actual ingress when enabled. Inspect startup/recovery 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.
© openclaw, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/openclaw-update of openclaw/openclaw.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 1eb5970
Compare with similar skills
Openclaw Update next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Openclaw Update this skillopenclaw/openclaw | 392k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Kubeshark Installerkubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Notes | Apache-2.0 | |
| GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb | 6.7k | — | ~4k | Automated safety check: Notes | Apache-2.0 | |
| KubeSphere ServiceMesh Managerkubesphere/kubesphere | 17k | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Vercelremotion-dev/remotion | 62k | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| AWS Cdk Developmentzxkane/aws-skills | 367 | 2 repos | ~2.5k | Automated safety check: Pass | MIT |
Similar skills
GreptimeDB Dev Docker Image
GreptimeTeam/greptimedb
Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.
KubeSphere ServiceMesh Manager
kubesphere/kubesphere
Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.
- Official
Vercel
remotion-dev/remotion
Set up a Codex monitor for Vercel deployments and preview URLs.
AWS Cdk Development
zxkane/aws-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
More from openclaw/openclaw
All 93 skills in this repoOpenclaw Live Updater
openclaw/openclaw
Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.
Tmux
openclaw/openclaw
Control tmux sessions/panes for interactive CLIs: list, capture output, send keys, paste text, monitor prompts.
Feishu Doc
openclaw/openclaw
Feishu document read/write workflows. An agent skill from openclaw/openclaw.
Openclaw PR Maintainer
openclaw/openclaw
Review, triage, repair, or land OpenClaw issues and pull requests with current-source evidence and the native maintainer workflow.
Browser Automation
openclaw/openclaw
A skill your agent uses when controlling web pages with the OpenClaw browser tool, especially multi-step flows, login checks, tab management, or recovery from stale refs/timeouts.
Clawsweeper
openclaw/openclaw
A skill your agent uses for all ClawSweeper work: OpenClaw issue/PR sweep reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed…
Related
Categories
Questions about Openclaw Update
What does Openclaw Update do?
Route routine updates of an existing local or remote OpenClaw Gateway to its installation owner, with automatic session recovery. Openclaw Update is an agent skill from openclaw/openclaw. Route routine updates of an existing local or remote OpenClaw Gateway to its installation owner, with automatic session recovery.
When should I use Openclaw Update?
Openclaw Update fits situations like: tasks that involve Deployment.
How do I install Openclaw Update in Claude Code?
Run `npx skills add openclaw/openclaw --skill openclaw-update -a claude-code`. Or copy the skill folder (.agents/skills/openclaw-update in openclaw/openclaw) into .claude/skills/openclaw-update in your project. Claude Code loads it when a task matches its description.
How do I install Openclaw Update in Codex?
Run `npx skills add openclaw/openclaw --skill openclaw-update -a codex`. Or copy the skill folder (.agents/skills/openclaw-update in openclaw/openclaw) into .agents/skills/openclaw-update in your project. Codex loads it when a task matches its description.
Can I use Openclaw Update in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openclaw/openclaw --skill openclaw-update -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/openclaw-update, .gemini/skills/openclaw-update, .github/skills/openclaw-update and .opencode/skills/openclaw-update in your project.
What does Openclaw Update need to run?
SKILL.md names no scripts, command-line tools or credentials: Openclaw Update is instructions for the agent only.
Does Openclaw Update access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Openclaw Update safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Openclaw Update use?
Openclaw Update is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Openclaw Update use?
About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Openclaw Update?
Skills that share tags, products or a category with Openclaw Update: Kubeshark Installer (kubeshark/kubeshark, 12k stars), GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars), KubeSphere ServiceMesh Manager (kubesphere/kubesphere, 17k stars) and Vercel (remotion-dev/remotion, 62k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Openclaw Update?
openclaw (a GitHub organization) maintains it in openclaw/openclaw, which has 391,610 GitHub stars. The repository holds 93 skills in this directory. The repository was last updated on October 8, 2026.
Source: openclaw/openclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.