Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
Openclaw Manager
Deploy, harden, and operate OpenClaw across local and hosted environments (Fly.io, Render, Railway, Hetzner, GCP) with secure defaults, channel setup guidanc...
skill openclawclawhub Free
Deploy, harden, and operate OpenClaw across local and hosted environments (Fly.io, Render, Railway, Hetzner, GCP) with secure defaults, channel setup guidanc...
โฌ 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, agents/openai.yaml, references/openclaw-doc-map.md, references/openclaw-integrations-playbook.md, references/openclaw-mode-matrix.md, references/openclaw-ops-ledger-schema.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
- 0.1.1
Provenance
- Publisher
- hollaugo
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Overview
Build and operate OpenClaw with production-safe defaults across both local and hosted environments. This skill is optimized for operators with limited platform expertise and enforces hard security gates before rollout completion. Primary references: Docs map: references/openclaw-doc-map.md Security gates checklist: references/openclaw-security-checklist.md Mode matrix: references/openclaw-mode-matrix.md OS matrix: references/openclaw-os-matrix.md Integrations playbook: references/openclaw-integrations-playbook.md Ops ledger schema: references/openclaw-ops-ledger-schema.md Automation helpers: scripts/plan_openclaw_rollout.py scripts/validate_openclaw_env.py scripts/update_openclaw_ops_ledger.py Default ops ledger path: ./openclaw-manager-operations-ledger.md (or operator specified)
Hard-Stop Rules (Never Bypass)
Stop and block deployment/install progression if any condition is true: Required secrets profile fails validation. Security checklist mandatory gates are not all passing. Rollback path is not documented and owned. Ops ledger was not updated for the current phase. Public exposure requested without auth boundary and token controls.
1) Intake and Scope Lock
Collect and confirm: mode: local or hosted provider: local, fly, render, railway, hetzner, gcp os: macos, linux, windows-wsl2 channels: subset of telegram, discord, slack integrations: subset of email, calendar environment: dev, staging, prod exposure: private or public Before proceeding, write a scope_lock ledger entry: python3 scripts/update_openclaw_ops_ledger.py \ --ledger-file ./openclaw-manager-operations-ledger.md \ --event scope_lock \ --operator codex \ --mode hosted \ --provider fly \ --os linux \ --environment prod \ --secrets-profile hosted-fly \ --channels telegram,slack \ --integrations email,calendar \ --security-status pending \ --rollback-tested no \ --blocking-issues "none" \ --next-owner operator \ --next-action-date 2026-02-20
2) Generate a Decision-Complete Plan
Always generate a plan first: python3 scripts/plan_openclaw_rollout.py \ --mode hosted \ --provider fly \ --os linux \ --channels telegram,slack \ --integrations email,calendar \ --environment prod \ --exposure public \ --ledger-file ./openclaw-manager-operations-ledger.md \ --output /tmp/openclaw-rollout.md The plan output is the execution contract. Do not skip sections.
3) Validate Secrets and Config Profile Before Any Infra Change
Validate environment using profile-aware gates: python3 scripts/validate_openclaw_env.py \ --env-file .env \ --profile hosted-fly \ --json Validation enforces: required keys by profile required provider/model alternatives malformed and duplicate env keys placeholder values weak gateway/setup tokens legacy alias warnings Write a predeploy_validation ledger entry immediately after validation.
4) Execute Mode Branch
Branch A: Local install (mode=local) Use official install/onboarding docs for local setup. Apply OS-specific commands from references/openclaw-os-matrix.md. Validate startup, persistence path, and local auth boundaries. If local public exposure is requested, apply gateway hardening gates from security checklist first. Branch B: Hosted clone + deploy (mode=hosted) Clone the selected OpenClaw source repo. Follow provider playbook from references/openclaw-doc-map.md. Configure persistent storage before production traffic. Configure ingress/auth, secrets, and health checks. Verify runtime logs for startup/auth errors and secret leakage. Write a deploy_complete ledger entry once deployment/install is complete.
5) Configure Channels and Integrations Safely
For each selected channel/integration: inject credentials via secret manager/env only run a minimal smoke test verify auth boundaries and error logging safety Track each item as: configured pending_credentials blocked Use references/openclaw-integrations-playbook.md for email/calendar specifics.
6) Agent + Memory Baseline
Document and validate: memory persistence strategy retention expectations restart and recovery behavior agent behavior boundaries Update ledger with operational baseline decisions.
7) Mandatory Security Gate
Run references/openclaw-security-checklist.md and produce pass/fail per gate. No go-live if any mandatory gate fails. Write a security_gate ledger entry with explicit blockers (if any).
8) Handover and Incident Readiness
Produce: provider status summary channel + integration matrix security gate table rollback and escalation ownership follow-up actions by risk order Write handover ledger entry. For incidents/troubleshooting, append incident entries as events happen.
Output Contract
Always return: Mode/provider/OS/environment status summary Security gate results (hard pass/fail) Channel + integration matrix Agent + memory configuration summary Ops ledger update confirmation (event names written) Follow-up actions ordered by risk
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
5 Docs1 Config
- SKILL.md
- references/openclaw-doc-map.md
- references/openclaw-integrations-playbook.md
- references/openclaw-mode-matrix.md
- references/openclaw-ops-ledger-schema.md
- agents/openai.yaml