How do I install the Hol Guard skill?

Run npx skillmds@latest add hashgraph-online-hol-guard-plugin/hol-guard in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Hol Guard safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Hol Guard?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Hol Guard free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Hol Guard?

hashgraph-online (@hashgraph-online-hol-guard-plugin) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Hol Guard by hashgraph-online-hol-guard-plugin

Name: Hol Guard
Rating: 4.5 (4 reviews)
Author: hashgraph-online

File contents

HOL Guard for OpenClaw

Use this skill only when the user explicitly asks to install, enable, initialize, repair, or check HOL Guard.

HOL Guard is a separate open-source local runtime package. This ClawHub skill is a discovery and setup surface. The hol-guard CLI remains the security authority and owns OpenClaw integration, policy, approvals, and evidence.

Canonical source: https://github.com/hashgraph-online/hol-guard

Check current state

Start with read-only checks:

command -v hol-guard

If Guard is installed, run:

hol-guard --version
hol-guard status

Report only what the CLI proves. Installing this skill alone does not mean runtime protection is active.

If the user asked only to check Guard, stop after hol-guard status. Do not install or initialize Guard.

Install or initialize

Continue with setup only when the user explicitly asked to install, enable, initialize, or repair Guard.

If hol-guard is missing, explain that the next command changes the user's Python/pipx environment and obtain explicit approval before running it:

pipx install hol-guard

If pipx is unavailable, stop and tell the user that the documented HOL Guard install path requires pipx. Do not silently switch package managers and do not execute a remote bootstrap script as a fallback.

After Guard is available, initialize protection interactively:

hol-guard init

Do not add unattended flags unless the user explicitly requests unattended setup. hol-guard init owns the real OpenClaw integration and avoids maintaining a second enforcement implementation in this skill.

Verify the resulting state:

hol-guard status

If protection is degraded, report the failed layer and let the Guard CLI or core documentation drive repair. Do not manually rewrite OpenClaw configuration from this skill unless the core HOL Guard documentation explicitly requires it.

Local-first boundary

Guard Cloud is optional. Do not require sign-in, credentials, or cloud connectivity for local OpenClaw protection. Offer cloud connection only if the user asks for synchronized history, shared policy, fleet visibility, or team approvals.

Safety rules

Never read .env files or unrelated credential stores.
Never bypass Guard approvals.
Never claim protection is active without hol-guard status proving it.
Do not execute code from unrelated repositories as part of setup.
Keep this package as a setup and discovery companion. Do not add a second OpenClaw enforcement implementation here.

---name: hol-guarddescription: Install, initialize, repair, or check local HOL Guard security protection for OpenClaw.---# HOL Guard for OpenClawUse this skill only when the user explicitly asks to install, enable, initialize, repair, or check HOL Guard.HOL Guard is a separate open-source local runtime package. This ClawHub skill is a discovery and setup surface. The `hol-guard` CLI remains the security authority and owns OpenClaw integration, policy, approvals, and evidence.Canonical source: https://github.com/hashgraph-online/hol-guard## Check current stateStart with read-only checks:```bashcommand -v hol-guard```If Guard is installed, run:```bashhol-guard --versionhol-guard status```Report only what the CLI proves. Installing this skill alone does not mean runtime protection is active.If the user asked only to check Guard, stop after `hol-guard status`. Do not install or initialize Guard.## Install or initializeContinue with setup only when the user explicitly asked to install, enable, initialize, or repair Guard.If `hol-guard` is missing, explain that the next command changes the user's Python/pipx environment and obtain explicit approval before running it:```bashpipx install hol-guard```If `pipx` is unavailable, stop and tell the user that the documented HOL Guard install path requires pipx. Do not silently switch package managers and do not execute a remote bootstrap script as a fallback.After Guard is available, initialize protection interactively:```bashhol-guard init```Do not add unattended flags unless the user explicitly requests unattended setup. `hol-guard init` owns the real OpenClaw integration and avoids maintaining a second enforcement implementation in this skill.Verify the resulting state:```bashhol-guard status```If protection is degraded, report the failed layer and let the Guard CLI or core documentation drive repair. Do not manually rewrite OpenClaw configuration from this skill unless the core HOL Guard documentation explicitly requires it.## Local-first boundaryGuard Cloud is optional. Do not require sign-in, credentials, or cloud connectivity for local OpenClaw protection. Offer cloud connection only if the user asks for synchronized history, shared policy, fleet visibility, or team approvals.## Safety rules- Never read `.env` files or unrelated credential stores.- Never bypass Guard approvals.- Never claim protection is active without `hol-guard status` proving it.- Do not execute code from unrelated repositories as part of setup.- Keep this package as a setup and discovery companion. Do not add a second OpenClaw enforcement implementation here.

Frequently asked questions

Hol Guard