Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
DevOps
Automate deployments, manage infrastructure, and build reliable CI/CD pipelines.
skill openclawclawhub Free
Automate deployments, manage infrastructure, and build reliable CI/CD pipelines.
โฌ 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
CI/CD Pipelines
Fail fast: run linting and unit tests before expensive integration tests โ saves time and compute Cache dependencies between runs โ npm install on every build wastes minutes Pin action versions with SHA, not tags โ actions/checkout@v3 can change, SHA is immutable Secrets in environment variables, never in code or logs โ mask them in CI output Parallel jobs for independent steps โ test, lint, and build can run simultaneously
Deployment Strategies
Blue-green: run new version alongside old, switch traffic atomically โ instant rollback by switching back Canary: route percentage of traffic to new version โ catch issues before full rollout Rolling: update instances incrementally โ balance between speed and risk Always have rollback plan before deploying โ know exactly how to revert Deploy the same artifact to all environments โ build once, promote through stages
Infrastructure as Code
Version control all infrastructure โ terraform, ansible, cloudformation in git Never apply changes without plan/diff review โ terraform plan before apply State files contain secrets โ store remotely with encryption, never in git Modules for reusable components โ don't copy-paste infrastructure definitions Separate environments with workspaces or directories โ dev changes shouldn't affect prod
Containers
One process per container โ containers are not VMs Health checks are mandatory โ orchestrators need them for routing and restarts Don't run as root โ use non-root USER in Dockerfile Immutable images: config via environment, not baked in โ same image in all environments Tag images with git SHA, not just latest โ know exactly what's deployed
Secrets Management
Never store secrets in environment files committed to git โ use vault, sealed secrets, or CI secret storage Rotate secrets regularly โ automation makes rotation painless Different secrets per environment โ dev leak shouldn't compromise prod Audit secret access โ know who accessed what and when Secrets in memory, not disk when possible โ temp files persist longer than expected
Monitoring & Alerting
Four golden signals: latency, traffic, errors, saturation โ start here Alert on symptoms, not causes โ "users seeing errors" not "CPU high" Every alert must be actionable โ if you can't do anything, it's noise Dashboard per service with key metrics โ one glance shows health Structured logs (JSON) for machine parsing โ grep works, but queries are better
Reliability
Define SLOs before building alerting โ what does "healthy" mean for this service? Error budgets: some failures are acceptable โ 99.9% means 8 hours downtime/year is OK Chaos engineering in staging โ break things intentionally before prod breaks accidentally Runbooks for common incidents โ 3am is not the time to figure out recovery steps Post-mortems without blame โ focus on systems, not people
Common Mistakes
SSH into prod to fix things โ all changes through automation, or you'll forget what you did No staging environment โ "works on my machine" doesn't mean works in prod Ignoring flaky tests โ they erode trust in CI, either fix or delete Manual steps in deployment โ if it's not automated, it'll be done wrong eventually Monitoring only happy paths โ check error rates and edge cases too
Networking
Internal services don't need public IPs โ use private subnets, expose only load balancers TLS everywhere, including internal traffic โ zero trust, even behind firewall DNS for service discovery โ hardcoded IPs break when things move Load balancer health checks separate from app health โ LB needs fast response, app health can be thorough Firewall default deny โ explicitly allow what's needed, block everything else
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