Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Security & Compliance
Self-Host
Deploy and maintain self-hosted services with security, backups, and long-term reliability.
skill openclawclawhub Free
Deploy and maintain self-hosted services with security, backups, and long-term reliability.
โฌ 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
Before Installing Anything
Backups first โ decide where data lives and how it's backed up before deploying, not after data exists Check resource requirements โ many services need more RAM than expected, OOM kills corrupt data Verify the project is actively maintained โ abandoned projects become security liabilities
Docker Fundamentals
Always use named volumes or bind mounts for persistent data โ anonymous volumes are lost on container removal Pin image versions (nginx:1.25.3 not nginx:latest) โ latest changes unexpectedly and breaks setups Set restart policy (unless-stopped or on-failure) โ containers don't auto-start after reboot by default Use docker compose down not docker compose rm โ down handles networks and volumes properly
Networking
Never expose database ports to the internet โ only the reverse proxy should be public Use a reverse proxy (Traefik, Caddy, Nginx Proxy Manager) โ handles SSL, routing, and security in one place Create Docker networks per project โ default bridge network lacks DNS resolution between containers Bind admin interfaces to localhost only (127.0.0.1:8080:8080) โ not all traffic needs to be public
SSL and Domains
Use automatic SSL with Let's Encrypt โ Caddy and Traefik do this natively For local/LAN access, use a real domain with DNS challenge โ avoids browser certificate warnings Wildcard certificates simplify multi-service setups โ one cert for *.home.example.com
Security Essentials
Change all default passwords immediately โ bots scan for default credentials within hours Enable automatic security updates for the host OS โ unpatched systems get compromised Use fail2ban or equivalent โ brute force attacks are constant Keep services behind authentication (Authelia, Authentik) โ not everything has built-in auth Disable root SSH, use key-only authentication โ password SSH is a vulnerability
Backups
Test restores, not just backups โ untested backups are wishful thinking 3-2-1 rule: 3 copies, 2 different media, 1 offsite โ local RAID is not backup Automate backup schedules โ manual backups get forgotten Back up Docker volumes, not containers โ containers are ephemeral, data is not
Monitoring
Set up uptime monitoring (Uptime Kuma is self-hostable) โ know when services die before users tell you Monitor disk space โ full disks cause silent failures and corruption Log rotation is mandatory โ Docker logs grow forever by default, fill disks Consider resource monitoring (Netdata, Prometheus) โ spot problems before they're critical
Maintenance
Schedule regular update windows โ services need updates, plan for downtime Document everything you deploy โ future you won't remember why that container exists Keep a compose file repo โ reproducibility matters when hardware fails Test updates on staging when possible โ production surprises are painful
Home Server Specifics
Dynamic DNS if ISP doesn't provide static IP โ Cloudflare, DuckDNS work well UPS protects against power loss corruption โ especially important for databases Consider power consumption โ some hardware costs more in electricity than cloud hosting Port forwarding exposes your home network โ use VPN (WireGuard, Tailscale) instead when possible
Common Mistakes
Putting everything on one machine with no redundancy โ single point of failure for all services Ignoring updates for months โ security vulnerabilities accumulate No firewall rules โ assuming "nobody knows my IP" is security Storing secrets in docker-compose.yml committed to git โ use .env files, exclude from version control Over-engineering from day one โ start simple, add complexity when needed
Category context
Identity, auth, scanning, governance, audit, and operational guardrails.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs
- SKILL.md