Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
Skill Update
Safely update skills with preview, migration support, and user validation. Never lose data or break workflows.
skill openclawclawhub Free
Safely update skills with preview, migration support, and user validation. Never lose data or break workflows.
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, migrate.md, preview.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.0
Provenance
- Publisher
- ivangdavila
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Safe Skill Updates
Core principle: Never update without user understanding and approval. Updates can break things: Changed file locations โ data loss Removed features โ broken workflows New requirements โ unexpected behavior Changed data formats โ incompatible state References: Read preview.md โ Diff and impact analysis Read migrate.md โ Data migration strategies
Update Flow
Check โ Are updates available? Preview โ What changes? How does it affect user? Explain โ Present changes step-by-step Confirm โ User explicitly approves Backup โ Save current state Update โ Apply new version Verify โ Confirm everything works
Checking for Updates
npx clawhub outdated # List skills with updates npx clawhub info <slug> # Show available versions Proactive notification: When user mentions a skill, check if update exists. Mention it once, don't nag.
Preview Before Update
โ ๏ธ Never update without showing impact first. For each changed file: Show what's different (added/removed/modified) Explain how it affects user's workflow Flag breaking changes prominently Breaking change indicators: File/folder structure changes Removed instructions or features New required setup steps Changed data format expectations
User Validation
Present changes in digestible format: "Skill X has v2.0.0 available. Changes: โ ๏ธ Breaking: Config now in config.md (was in SKILL.md) Added: New templates/ folder with examples Removed: Old legacy.md no longer needed Migration needed: Your saved preferences need to move. I can help migrate. Proceed?" Only update after explicit "yes".
Backup Strategy
Before ANY update: Copy current skill folder to ~/.clawhub/backups/<slug>-<version>-<timestamp>/ Note the backup location in response If update fails โ offer restore
Handling Migrations
When data format changes: Detect user's current data (preferences, saved state) Explain what needs to migrate Propose migration steps Execute only with approval Verify migrated data works See migrate.md for patterns.
Rollback
If update causes problems: "Something's not working? I have a backup from before the update. Want me to restore skill X to v1.2.3?" Keep backups for at least 7 days or until user confirms new version works. Updates should feel safe, not scary. User stays in control.
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
3 Docs
- SKILL.md
- migrate.md
- preview.md