Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Standardized skill install workflow using short aliases (chis/chisf) with force + force-install + workspace-aware lookup.
Standardized skill install workflow using short aliases (chis/chisf) with force + force-install + workspace-aware lookup.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
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.
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.
A lightweight skill to standardize how we install/manage OpenClaw skills.
chis <slug> [workdir] [version] = install a skill from ClawHub. chisf <slug> [workdir] [version] = force-install when the package is flagged/requires overwrite. clawhub inspect <slug> = inspect before install (recommended for validation). Always run installs with explicit workdir and skills dir to avoid path confusion. Default workdir in examples: /Users/zququ/.openclaw/workspace.
clawhub install <slug> --workdir /Users/zququ/.openclaw/workspace --dir skills --version <version> Omit --version for latest. If no version argument, installs latest available.
clawhub install <slug> --force --workdir /Users/zququ/.openclaw/workspace --dir skills --version <version> Use this when: package is flagged as suspicious overwrite behavior is required
clawhub inspect <slug>
clawhub list --workdir /Users/zququ/.openclaw/workspace --dir skills
Use these shortcuts in practice: chis <slug> โ same as standard install in default workspace. chisf <slug> โ same as force install in default workspace. If needed, set your session path context and explicitly pass an alternate path: chis --workdir /alt/path <slug> chisf --workdir /alt/path <slug>
If Rate limit exceeded: retry after a few minutes. If command fails due to path mismatch: ensure you are checking with same --workdir and --dir skills used during install. If package not found: confirm correct slug via clawhub search <keyword>.
Use: --workdir /Users/zququ/.openclaw/workspace --dir skills Already-known working example: clawhub install proactive-agent --force --workdir /Users/zququ/.openclaw/workspace --dir skills
CHISF is a human-facing label I use for force-install style operations. Keep all install actions explicit and repeatable; never rely on default working dir. Failure handling If install fails, run clawhub inspect <slug> --workdir /Users/zququ/.openclaw/workspace --dir skills for a quick pre-check. If it still fails due to environment mismatch, re-run with explicit --workdir /Users/zququ/.openclaw/workspace and --dir skills (never rely on implicit defaults). For suspected API/service issues (e.g., rate limit exceeded), prefer 10โ20 minute pause and retry. If rate limit persists, use the local fallback installer: /Users/zququ/.local/bin/clawhub-install-safe --force <slug> <workdir> (or without --force when not needed) before switching to another approach. Keep the same --workdir and --dir skills/registry context when re-running.
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.