From b08220718a2ea2d770f2d3a3137a3d725ab352a2 Mon Sep 17 00:00:00 2001 From: Vincent Koc Date: Fri, 27 Feb 2026 13:47:05 -0800 Subject: [PATCH] Docs: stage ClawHub capability enforcement wording --- docs/tools/clawhub.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/tools/clawhub.md b/docs/tools/clawhub.md index 63ec84b32c2..9005eaaa3b2 100644 --- a/docs/tools/clawhub.md +++ b/docs/tools/clawhub.md @@ -113,9 +113,9 @@ legitimate contributors. Skills declare `capabilities` in their SKILL.md frontmatter to describe what system access they need. ClawHub displays these to users before install. -OpenClaw enforces them at runtime — community skills that attempt to use tools -without the matching declared capability are blocked. Skills with no capabilities -are treated as read-only (model-only instructions, no tool access). +OpenClaw uses these declarations for visibility and policy checks as capability +enforcement rolls out in stages. Skills with no capabilities are treated as +read-only metadata declarations. Available capabilities: `shell`, `filesystem`, `network`, `browser`, `sessions`, `messaging`, `scheduling`.