Merge branch 'main' into commands-list-clean

docs/tools/clawdhub.md

@@ -50,7 +50,8 @@ bun add -g clawdhub
 
 By default, the CLI installs skills into `./skills` under your current working directory. Clawdbot loads workspace skills from `<workspace>/skills` and will pick them up in the **next** session. If you already use `~/.clawdbot/skills` or bundled skills, workspace skills take precedence.
 
-For more detail on how skills are loaded and gated, see `docs/skills.md`.
+For more detail on how skills are loaded, shared, and gated, see
+[Skills](/tools/skills).
 
 ## What the service provides (features)
 

docs/tools/elevated.md

@@ -15,7 +15,7 @@ read_when:
 - **Global availability gate**: `agent.elevated` is global (not per-agent). If disabled or sender not allowlisted, elevated is unavailable everywhere.
 - **Per-session state**: `/elevated on|off` sets the elevated level for the current session key.
 - **Inline directive**: `/elevated on` inside a message applies to that message only.
-- **Groups**: In group chats, elevated directives are only honored when the agent is mentioned.
+- **Groups**: In group chats, elevated directives are only honored when the agent is mentioned. Command-only messages that bypass mention requirements are treated as mentioned.
 - **Host execution**: elevated runs `bash` on the host (bypasses sandbox).
 - **Unsandboxed agents**: when there is no sandbox to bypass, elevated does not change where `bash` runs.
 - **Tool policy still applies**: if `bash` is denied by tool policy, elevated cannot be used.

docs/tools/skills.md

@@ -23,6 +23,36 @@ If a skill name conflicts, precedence is:
 Additionally, you can configure extra skill folders (lowest precedence) via
 `skills.load.extraDirs` in `~/.clawdbot/clawdbot.json`.
 
+## Per-agent vs shared skills
+
+In **multi-agent** setups, each agent has its own workspace. That means:
+
+- **Per-agent skills** live in `<workspace>/skills` for that agent only.
+- **Shared skills** live in `~/.clawdbot/skills` (managed/local) and are visible
+  to **all agents** on the same machine.
+- **Shared folders** can also be added via `skills.load.extraDirs` (lowest
+  precedence) if you want a common skills pack used by multiple agents.
+
+If the same skill name exists in more than one place, the usual precedence
+applies: workspace wins, then managed/local, then bundled.
+
+## ClawdHub (install + sync)
+
+ClawdHub is the public skills registry for Clawdbot. Use it to discover,
+install, update, and back up skills. Full guide: [ClawdHub](/tools/clawdhub).
+
+Common flows:
+
+- Install a skill into your workspace:
+  - `clawdhub install <skill-slug>`
+- Update all installed skills:
+  - `clawdhub update --all`
+- Sync (scan + publish updates):
+  - `clawdhub sync --all`
+
+By default, `clawdhub` installs into `./skills` under your current working
+directory; Clawdbot picks that up as `<workspace>/skills` on the next session.
+
 ## Format (AgentSkills + Pi-compatible)
 
 `SKILL.md` must include at least:

docs/tools/slash-commands.md

@@ -53,6 +53,8 @@ Text-only:
 
 Notes:
 - Commands accept an optional `:` between the command and args (e.g. `/think: high`, `/send: on`, `/help:`).
+- `/verbose` is meant for debugging and extra visibility; keep it **off** in normal use.
+- `/reasoning` (and `/verbose`) are risky in group settings: they may reveal internal reasoning or tool output you did not intend to expose. Prefer leaving them off, especially in group chats.
 
 ## Surface notes