Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
Deploy
Ship applications reliably with CI/CD, rollback strategies, and zero-downtime deployment patterns.
skill openclawclawhub Free
Ship applications reliably with CI/CD, rollback strategies, and zero-downtime deployment patterns.
โฌ 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
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
Pre-Deploy Checklist
Tests passing in CI โ never deploy with failing tests Environment variables set in target โ missing secrets cause silent failures Database migrations run before code deploy โ new code expecting new schema fails Rollback plan ready โ know exactly how to revert before you need to
Deployment Strategies
Rolling: update instances one by one โ safe, slower, no extra resources Blue-green: full parallel environment, instant switch โ fast rollback, 2x resources Canary: route percentage to new version โ catch issues early, complex routing Choose based on risk tolerance and resources โ no universal best
Zero-Downtime Deploys
Health checks must pass before traffic routes โ unhealthy instances stay out Graceful shutdown: finish in-flight requests before terminating Database changes must be backwards compatible โ old code still running during deploy Session handling: sticky sessions or external session store โ don't lose user state
CI/CD Pipeline
Build once, deploy everywhere โ same artifact to staging and prod Cache dependencies between builds โ save minutes per deploy Parallel steps where possible โ tests, linting, security scans Fail fast: quick checks first โ don't wait for slow tests to catch typos Pin action versions with SHA โ tags can change unexpectedly
Environment Management
Staging mirrors prod โ different configs cause "works in staging" bugs Secrets in secret manager, not environment files โ rotation without redeploy Feature flags decouple deploy from release โ ship dark, enable later Config as code in version control โ except secrets
Database Migrations
Migrations must be backwards compatible during deploy window Add columns nullable first, then backfill, then add constraint Never rename columns in one step โ add new, migrate data, remove old Test migrations on prod-size data โ 10 rows is fast, 10 million isn't Rollback script for every migration
Rollback
Automated rollback on health check failure Keep previous version artifacts available โ can't rollback what you deleted Database rollbacks are hard โ design migrations to not need them Feature flags for instant rollback of functionality without deploy Document rollback procedure โ panic time is not learning time
Monitoring Post-Deploy
Watch error rates for 15 minutes after deploy โ most issues surface quickly Compare key metrics to pre-deploy baseline Alerting on anomalies: latency spike, error rate increase Log correlation: trace requests through systems User-facing smoke tests after deploy
Containers
Image tagged with git SHA โ know exactly what's running Health check endpoint that verifies dependencies Resource limits set โ prevent runaway containers
Serverless
Cold start optimization โ keep bundles small Provisioned concurrency for latency-sensitive paths Timeout set appropriately โ default is often too short
Static Sites
CDN cache invalidation after deploy Immutable assets with content hashes โ cache forever Preview deploys for PRs
Common Mistakes
Deploying Friday afternoon โ issues surface when nobody's watching No rollback plan โ hoping nothing goes wrong isn't a strategy Mixing code and migration deploys โ one thing at a time Manual deploy steps โ if it's not automated, it's wrong sometimes Deploying without monitoring โ you won't know it's broken until users complain
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
1 Docs
- SKILL.md