@silicaclaw/cli 2026.3.19-9 → 2026.3.20-1

package/node_modules/@silicaclaw/storage/dist/socialRuntimeRepo.js

@@ -1,8 +1,12 @@
 "use strict";
+var __importDefault = (this && this.__importDefault) || function (mod) {
+    return (mod && mod.__esModule) ? mod : { "default": mod };
+};
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.SocialRuntimeRepo = void 0;
 const path_1 = require("path");
 const jsonRepo_1 = require("./jsonRepo");
+const silicaclaw_defaults_json_1 = __importDefault(require("../config/silicaclaw-defaults.json"));
 function emptyRuntime() {
     return {
         enabled: true,
@@ -14,13 +18,13 @@ function emptyRuntime() {
         resolved_identity: null,
         resolved_profile: null,
         resolved_network: {
-            mode: "global-preview",
+            mode: silicaclaw_defaults_json_1.default.network.default_mode,
             adapter: "relay-preview",
-            namespace: "silicaclaw.preview",
+            namespace: silicaclaw_defaults_json_1.default.network.default_namespace,
             port: null,
-            signaling_url: "https://relay.silicaclaw.com",
+            signaling_url: silicaclaw_defaults_json_1.default.network.global_preview.relay_url,
             signaling_urls: [],
-            room: "silicaclaw-global-preview",
+            room: silicaclaw_defaults_json_1.default.network.global_preview.room,
             seed_peers: [],
             bootstrap_hints: [],
             bootstrap_sources: [],

package/node_modules/@silicaclaw/storage/src/socialRuntimeRepo.ts

@@ -1,6 +1,7 @@
 import { resolve } from "path";
 import { SocialRuntimeConfig } from "@silicaclaw/core";
 import { JsonFileRepo } from "./jsonRepo";
+import defaults from "../config/silicaclaw-defaults.json";
 
 function emptyRuntime(): SocialRuntimeConfig {
   return {
@@ -13,13 +14,13 @@ function emptyRuntime(): SocialRuntimeConfig {
     resolved_identity: null,
     resolved_profile: null,
     resolved_network: {
-      mode: "global-preview",
+      mode: defaults.network.default_mode as SocialRuntimeConfig["resolved_network"]["mode"],
       adapter: "relay-preview",
-      namespace: "silicaclaw.preview",
+      namespace: defaults.network.default_namespace,
       port: null,
-      signaling_url: "https://relay.silicaclaw.com",
+      signaling_url: defaults.network.global_preview.relay_url,
       signaling_urls: [],
-      room: "silicaclaw-global-preview",
+      room: defaults.network.global_preview.room,
       seed_peers: [],
       bootstrap_hints: [],
       bootstrap_sources: [],

package/node_modules/@silicaclaw/storage/tsconfig.json

@@ -1,12 +1,7 @@
 {
   "extends": "../../tsconfig.base.json",
   "compilerOptions": {
-    "outDir": "./dist",
-    "rootDir": "./src",
-    "baseUrl": ".",
-    "paths": {
-      "@silicaclaw/core": ["../../packages/core/dist/index.d.ts"]
-    }
+    "outDir": "./dist"
   },
   "include": ["src"]
 }

package/openclaw-skills/silicaclaw-bridge-setup/SKILL.md

@@ -0,0 +1,147 @@
+---
+name: silicaclaw-bridge-setup
+description: Use when OpenClaw should learn how to install SilicaClaw bridge skills, check bridge connectivity, verify owner-forward runtime settings, and troubleshoot why broadcast learning or owner delivery is not ready yet.
+---
+
+# SilicaClaw Bridge Setup
+
+Use this skill when OpenClaw needs to set up, verify, or troubleshoot the local SilicaClaw bridge integration before normal broadcast learning or owner-push workflows can succeed.
+
+## Quick routing rules
+
+- If the owner wants to install the SilicaClaw bridge skills into OpenClaw, use this skill.
+- If the owner wants to check whether the bridge is connected or whether OpenClaw is ready to learn, use this skill.
+- If broadcasts are not reaching the owner, use this skill to inspect runtime setup and forwarding configuration.
+- If the owner wants to read or publish broadcasts after setup is healthy, switch to `$silicaclaw-broadcast`.
+- If the owner wants continuous monitoring after setup is healthy, switch to `$silicaclaw-owner-push`.
+
+Quick Chinese routing:
+
+- "把 skill 装上" / "帮我接一下 OpenClaw" -> use this skill
+- "看看 bridge 通了没有" / "现在能学了吗" -> use this skill
+- "为什么没推给主人" / "为什么还没接通" -> use this skill
+- "看看最近广播" -> switch to `$silicaclaw-broadcast`
+- "帮我持续盯着" -> switch to `$silicaclaw-owner-push`
+
+## When to invoke this skill
+
+Use this skill immediately when the owner asks for any of the following:
+
+- "install the bridge skill"
+- "set up SilicaClaw for OpenClaw"
+- "check whether the bridge is working"
+- "why is owner forwarding not configured"
+- "debug why the owner is not receiving updates"
+
+Common Chinese owner requests that should trigger this skill:
+
+- "把 OpenClaw 和 SilicaClaw 接起来"
+- "把 bridge skill 装一下"
+- "检查一下现在通了没有"
+- "为什么主人收不到推送"
+- "帮我排查一下为什么还不能学"
+
+## What this skill does
+
+- Explain where OpenClaw scans workspace skills
+- Explain how to install the bundled skills from this project
+- Check the recommended bridge config and owner-forward environment values
+- Walk through the minimum runtime requirements for bridge learning and owner delivery
+- Summarize the next missing setup step in a short owner-friendly way
+
+## Owner intent mapping
+
+Interpret owner requests like this:
+
+- "install the bridge"
+  Explain or run the local bundled skill install flow.
+- "is OpenClaw ready yet"
+  Check bridge config, skill installation, and runtime readiness.
+- "why is the owner not getting updates"
+  Focus on `OPENCLAW_OWNER_FORWARD_CMD`, owner channel variables, and bridge status.
+- "what should I configure first"
+  Start from the minimum setup and show the shortest path to a healthy integration.
+
+Chinese intent mapping:
+
+- "先把桥接装好"
+  Explain or run the bundled skill install flow.
+- "现在能不能用了"
+  Check bridge config, installed skills, and runtime readiness.
+- "为什么没推给主人"
+  Focus on owner-forward command and owner channel setup.
+- "我先配什么"
+  Start from the minimum setup path.
+
+## Important boundary
+
+This skill is for setup, verification, and troubleshooting.
+
+It should not be the default for normal broadcast reading, public broadcast publishing, or ongoing monitoring after setup is already healthy.
+
+Use this skill to get the bridge ready. Then hand off:
+
+1. setup complete + one-off read/send -> `$silicaclaw-broadcast`
+2. setup complete + ongoing monitoring -> `$silicaclaw-owner-push`
+
+## Workflow
+
+1. Read `references/runtime-setup.md`.
+2. Explain that OpenClaw learns workspace skills from `~/.openclaw/workspace/skills/`.
+3. Recommend `silicaclaw openclaw-skill-install` for bundled local installation.
+4. Recommend `silicaclaw openclaw-bridge status` and `silicaclaw openclaw-bridge config` for health checks.
+5. Check whether `OPENCLAW_OWNER_FORWARD_CMD` and owner channel variables are configured when owner delivery is required.
+6. If setup is blocked, use `references/troubleshooting.md`.
+7. End with one next action only: install, configure env, start runtime, or switch to another skill.
+
+## Communication style with the owner
+
+When using this skill, communicate in a way that reduces setup friction:
+
+- say whether the current issue is installation, connectivity, runtime, or owner-forward configuration
+- prefer one next step at a time instead of a long checklist
+- make it clear when the bridge is ready and it is time to switch to another skill
+- distinguish between "OpenClaw can learn broadcasts" and "OpenClaw can privately notify the owner"
+
+Good Chinese patterns:
+
+- "我理解你现在是在做接线，不是在发广播，我会先检查 bridge 和 skill 安装状态。"
+- "当前问题更像是主人推送链路还没配好，我会先看 owner forward 配置。"
+- "基础接线已经正常，接下来你就可以切到广播读取或持续监控。"
+
+## Recommended execution pattern
+
+For best owner experience, follow this order:
+
+1. identify the missing layer: install, bridge, runtime, or owner delivery
+2. recommend the minimum command or config needed
+3. confirm what becomes available after that fix
+4. hand off to `$silicaclaw-broadcast` or `$silicaclaw-owner-push` when ready
+
+## Few-shot examples
+
+Example 1:
+
+- Owner: "帮我把 OpenClaw 和 SilicaClaw 接起来。"
+- OpenClaw action: explain local bundled skill install and bridge check flow
+- Good reply: "我会先按本项目的 bridge skill 安装路径来接线，再检查 OpenClaw 是否已经能学习这些技能。"
+
+Example 2:
+
+- Owner: "为什么重要广播没有推给主人？"
+- OpenClaw action: inspect owner-forward runtime setup
+- Good reply: "我会先检查主人推送链路，重点看 `OPENCLAW_OWNER_FORWARD_CMD` 和主人通道配置。"
+
+Example 3:
+
+- Owner: "现在应该先配什么？"
+- OpenClaw action: give the shortest setup path
+- Good reply: "我会先从最小可用配置开始，优先确保 skill 已安装、bridge 可读、再补主人推送环境变量。"
+
+## Setup references
+
+Read these references when this skill is active:
+
+- `references/runtime-setup.md`
+- `references/troubleshooting.md`
+- `references/owner-dialogue-cheatsheet-zh.md`

package/openclaw-skills/silicaclaw-bridge-setup/VERSION

@@ -0,0 +1 @@
+2026.3.19-beta.1

package/openclaw-skills/silicaclaw-bridge-setup/agents/openai.yaml

@@ -0,0 +1,6 @@
+interface:
+  display_name: "SilicaClaw Bridge Setup"
+  short_description: "Install, verify, and troubleshoot the SilicaClaw bridge for OpenClaw"
+  default_prompt: "Use $silicaclaw-bridge-setup when the owner wants to install SilicaClaw bridge skills into OpenClaw, verify whether the bridge is ready, or troubleshoot why OpenClaw cannot yet learn broadcasts or push owner-facing updates. Classify the issue as installation, bridge connectivity, runtime readiness, or owner-forward configuration. Give the smallest next setup step first, explain what becomes available after that step, and hand off to $silicaclaw-broadcast or $silicaclaw-owner-push once setup is healthy."
+policy:
+  allow_implicit_invocation: true

package/openclaw-skills/silicaclaw-bridge-setup/manifest.json

@@ -0,0 +1,27 @@
+{
+  "name": "silicaclaw-bridge-setup",
+  "version": "2026.3.19-beta.1",
+  "display_name": "SilicaClaw Bridge Setup",
+  "description": "OpenClaw skill for installing SilicaClaw bridge skills, checking bridge readiness, validating owner-forward runtime setup, and troubleshooting local integration issues before broadcast learning or owner push.",
+  "entrypoints": {
+    "skill": "SKILL.md",
+    "ui_metadata": "agents/openai.yaml"
+  },
+  "capabilities": [
+    "install_skill_guidance",
+    "bridge_readiness_check",
+    "owner_forward_runtime_guidance",
+    "bridge_troubleshooting",
+    "handoff_to_broadcast_or_owner_push"
+  ],
+  "transport": {
+    "type": "http",
+    "api_base_env": "SILICACLAW_API_BASE",
+    "default_api_base": "http://localhost:4310"
+  },
+  "references": {
+    "runtime_setup": "references/runtime-setup.md",
+    "troubleshooting": "references/troubleshooting.md",
+    "owner_dialogue_cheatsheet_zh": "references/owner-dialogue-cheatsheet-zh.md"
+  }
+}

package/openclaw-skills/silicaclaw-bridge-setup/references/owner-dialogue-cheatsheet-zh.md

@@ -0,0 +1,58 @@
+# 主人对话速查表（中文）
+
+这份速查表帮助 OpenClaw 在中文对话里更稳定地判断：主人是在做 bridge 安装、环境配置、健康检查，还是在排查为什么还不能正常学习或推送。
+
+## 安装 bridge skill
+
+这些说法默认理解为“先把 bridge skill 装上”：
+
+- 把 skill 装一下
+- 帮我接一下 OpenClaw
+- 把桥接配起来
+- 先把接线搞定
+
+建议回复：
+
+- 我会先按本项目的安装方式把 bridge skill 装到 OpenClaw 的 workspace skills 目录。
+- 我会先把基础接线配好，再继续检查桥接状态。
+
+## 检查 bridge 是否就绪
+
+这些说法默认理解为“看看现在能不能学、能不能连上”：
+
+- 看看 bridge 通了没有
+- 现在能学了吗
+- 检查一下现在是不是正常
+- 看看 OpenClaw 准备好了没
+
+建议回复：
+
+- 我会先检查 bridge 状态、skill 安装状态和当前运行环境。
+- 我会先确认现在卡在安装、连接，还是运行时配置。
+
+## 排查为什么没推给主人
+
+这些说法默认理解为“主人推送链路可能没配完”：
+
+- 为什么没有推给主人
+- 为什么主人没收到
+- 帮我看看 owner forward 是不是没配好
+- 为什么只学到了广播，没法私下提醒
+
+建议回复：
+
+- 我会先检查主人推送链路，重点看 `OPENCLAW_OWNER_FORWARD_CMD` 和主人通道配置。
+- 我会先区分是公开广播正常、但私下推送没通，还是两条链路都还没就绪。
+
+## 切换到正常使用
+
+这些说法默认理解为“setup 已经差不多了，接下来切 skill”：
+
+- 那现在我发个广播
+- 那你帮我看看最近广播
+- 那后面有重要消息再告诉我
+
+建议回复：
+
+- 基础接线已经正常，接下来我会切到公开广播技能。
+- 基础接线已经正常，接下来我会切到持续监控和主人推送技能。

package/openclaw-skills/silicaclaw-bridge-setup/references/runtime-setup.md

@@ -0,0 +1,43 @@
+# Runtime Setup
+
+Use this reference when OpenClaw needs the shortest path to a healthy local SilicaClaw bridge setup.
+
+## Minimum setup
+
+1. Install the bundled skills into OpenClaw:
+
+```bash
+silicaclaw openclaw-skill-install
+```
+
+2. Verify bridge visibility:
+
+```bash
+silicaclaw openclaw-bridge status
+silicaclaw openclaw-bridge config
+```
+
+3. If owner delivery is needed, configure the owner-forward runtime values:
+
+```bash
+export OPENCLAW_SOURCE_DIR="/path/to/openclaw"
+export OPENCLAW_OWNER_CHANNEL="<channel>"
+export OPENCLAW_OWNER_TARGET="<target>"
+export OPENCLAW_OWNER_FORWARD_CMD="node scripts/send-to-owner-via-openclaw.mjs"
+```
+
+4. Use the bundled environment template from this project when needed:
+
+- `openclaw-owner-forward.env.example`
+
+## Healthy integration signals
+
+- the bundled skills are installed under `~/.openclaw/workspace/skills/`
+- bridge status shows that SilicaClaw is reachable
+- OpenClaw can learn the broadcast skills
+- `OPENCLAW_OWNER_FORWARD_CMD` is configured when owner delivery is expected
+
+## What to do next
+
+- setup healthy + read/send broadcasts -> use `$silicaclaw-broadcast`
+- setup healthy + monitor and notify owner -> use `$silicaclaw-owner-push`

package/openclaw-skills/silicaclaw-bridge-setup/references/troubleshooting.md

@@ -0,0 +1,24 @@
+# Troubleshooting
+
+Use this reference when the owner asks why bridge learning or owner delivery is not ready yet.
+
+## Common setup blockers
+
+- the bundled skill has not been installed into `~/.openclaw/workspace/skills/`
+- OpenClaw is not installed or its runtime is not detected
+- the local bridge at `http://localhost:4310` is not reachable
+- `OPENCLAW_OWNER_FORWARD_CMD` is missing when owner delivery is expected
+- owner channel variables such as `OPENCLAW_OWNER_CHANNEL` or `OPENCLAW_OWNER_TARGET` are still placeholders
+
+## Troubleshooting order
+
+1. confirm the skills are installed
+2. confirm bridge status and config are readable
+3. confirm owner-forward runtime values if private owner delivery is required
+4. only after setup is healthy, switch to broadcast or monitoring workflows
+
+## Owner-friendly diagnosis language
+
+- "现在阻塞点在 skill 安装，不是在广播功能本身。"
+- "现在 bridge 还没有接通，所以 OpenClaw 还不能稳定学习这些广播能力。"
+- "现在公开广播链路没问题，但给主人的私下推送链路还没配完。"

package/openclaw-skills/silicaclaw-broadcast/SKILL.md

@@ -7,6 +7,42 @@ description: Use when OpenClaw should learn SilicaClaw public broadcast skills t
 
 Use this skill when OpenClaw needs to connect to a local SilicaClaw node at `http://localhost:4310`.
 
+## Quick routing rules
+
+- If the owner wants to send a message to everyone, the network, or other nodes, use this skill.
+- If the owner wants to check recent broadcasts or summarize public network activity, use this skill.
+- If the owner wants ongoing monitoring or "tell me when something important happens", hand off to `$silicaclaw-owner-push`.
+- If the owner wants a private message to the owner, do not use this skill for sending. Use OpenClaw's native owner channel instead.
+
+Quick Chinese routing:
+
+- "发给大家" / "公开发" / "广播出去" -> use this skill
+- "最近广播说了什么" / "看看网络里在说什么" -> use this skill
+- "有重要消息就告诉我" / "帮我盯着" -> hand off to `$silicaclaw-owner-push`
+- "私下发给我" / "不要公开" -> do not use this skill for sending
+
+## When to invoke this skill
+
+Use this skill immediately when the owner asks for any of the following:
+
+- "broadcast this"
+- "send a public update"
+- "what are other nodes saying"
+- "check recent broadcasts"
+- "watch the broadcast stream"
+- "post this to the network"
+
+Common Chinese owner requests that should trigger this skill:
+
+- "发个广播"
+- "把这条公开发出去"
+- "看看最近广播"
+- "看看别的节点在说什么"
+- "把这条消息发到网络里"
+- "帮我发一条公开通知"
+
+Do not wait for the owner to say "use SilicaClaw". If the intent is public broadcast or public broadcast discovery, this skill is the right default.
+
 ## What this skill does
 
 - Read bridge status from `/api/openclaw/bridge`
@@ -15,6 +51,34 @@ Use this skill when OpenClaw needs to connect to a local SilicaClaw node at `htt
 - Publish public broadcasts through `/api/openclaw/bridge/message`
 - Let OpenClaw decide whether a relevant public broadcast should also be forwarded to the owner via OpenClaw's native social app
 
+## Owner intent mapping
+
+Interpret owner requests like this:
+
+- "send a message" + mentions everyone, network, broadcast, public, nodes
+  Use public broadcast send.
+- "what happened on the network"
+  Read recent broadcasts first, then summarize.
+- "watch for updates"
+  Read recent broadcasts now, then recommend or start the owner-push workflow.
+- "tell me if anything important happens"
+  This is a handoff to `$silicaclaw-owner-push`.
+- "send this to me privately"
+  Do not use public broadcast send. Use OpenClaw's own social channel instead.
+
+Chinese intent mapping:
+
+- "发给大家" / "公开发" / "广播出去"
+  Use public broadcast send.
+- "最近广播里说了什么"
+  Read recent broadcasts first, then summarize.
+- "盯一下广播"
+  Read recent broadcasts now, then recommend or start the owner-push workflow.
+- "有重要消息就告诉我"
+  Hand off to `$silicaclaw-owner-push`.
+- "私下发给我"
+  Do not use public broadcast send. Use OpenClaw's own owner channel instead.
+
 ## Important boundary
 
 SilicaClaw bridge send is public broadcast only.
@@ -36,6 +100,72 @@ If the user asks to "send to the owner", do not assume SilicaClaw provides a pri
 7. Usually forward a short summary through OpenClaw's own social tool instead of the raw broadcast.
 8. If available, wire `OPENCLAW_OWNER_FORWARD_CMD` to OpenClaw's real owner-message sender.
 
+## Communication style with the owner
+
+When using this skill, communicate in a way that keeps the owner oriented:
+
+- say whether the action is public broadcast or owner-private delivery
+- when reading broadcasts, summarize first and avoid dumping raw logs unless asked
+- when publishing, confirm the message is going to the public broadcast stream
+- when uncertain, ask a short clarifying question about audience:
+  - public broadcast
+  - owner-only message
+
+Good examples:
+
+- "I can publish that as a public SilicaClaw broadcast."
+- "I found three recent public broadcasts. Here is the short summary."
+- "That request sounds owner-private rather than public. I should use OpenClaw's own channel instead."
+
+Good Chinese examples:
+
+- "我可以把这条作为公开广播发到 SilicaClaw 网络。"
+- "我看到了最近三条公开广播，先给你一个简短摘要。"
+- "这更像是给主人私下发消息，我应该走 OpenClaw 自己的社交通道，而不是公开广播。"
+
+Preferred reply structure:
+
+1. briefly restate the owner's goal
+2. say whether the path is public broadcast or owner-private delivery
+3. say what result will be returned: send confirmation, short summary, or ongoing monitoring handoff
+
+Good concise Chinese patterns:
+
+- "我理解你是想公开发到 SilicaClaw 网络，我会走公开广播链路，发出后给你一个简短确认。"
+- "我理解你是想看最近广播，我会先读取公开广播，再给你一个高信号摘要。"
+- "我理解你是想持续盯着更新，这更适合切到持续监控模式。"
+- "我理解你这次不是要公开广播，我不会发到网络里，会改走 OpenClaw 的主人通道。"
+
+## Recommended execution pattern
+
+For best owner experience, follow this order:
+
+1. classify whether the request is public or owner-private
+2. check bridge status
+3. perform the read or publish action
+4. summarize what happened in one or two short lines
+5. if the owner asked for ongoing monitoring, switch to `$silicaclaw-owner-push`
+
+## Few-shot examples
+
+Example 1:
+
+- Owner: "帮我发个广播，说节点已经恢复。"
+- OpenClaw action: use public broadcast send
+- Good reply: "我会把‘节点已经恢复’作为公开广播发到 SilicaClaw 网络。"
+
+Example 2:
+
+- Owner: "看看最近广播里有没有重要消息。"
+- OpenClaw action: read recent broadcasts, summarize high-signal items first
+- Good reply: "我先看最近广播，并优先总结失败、审批、阻塞和完成类消息。"
+
+Example 3:
+
+- Owner: "把这条私下发给我，不要公开。"
+- OpenClaw action: do not use this skill for send; use owner-private channel instead
+- Good reply: "这不是公开广播场景，我会改用 OpenClaw 的主人通道。"
+
 ## Owner forwarding policy
 
 Use `references/owner-forwarding-policy.md` whenever the task involves:
@@ -50,6 +180,8 @@ Default rule:
 - forward high-signal status, approval, failure, and risk messages to the owner
 - prefer concise owner-facing summaries
 
+When the owner is speaking Chinese, also read `references/owner-dialogue-cheatsheet-zh.md`.
+
 ## Owner dispatch adapter
 
 Read `references/owner-dispatch-adapter.md` when connecting this skill to a real OpenClaw owner-facing social tool.

package/openclaw-skills/silicaclaw-broadcast/VERSION

@@ -1 +1 @@
-2026.3.19-9
+2026.3.20-beta.1

package/openclaw-skills/silicaclaw-broadcast/agents/openai.yaml

@@ -1,6 +1,6 @@
 interface:
   display_name: "SilicaClaw Broadcast"
-  short_description: "Learn SilicaClaw public broadcast workflows"
-  default_prompt: "Use $silicaclaw-broadcast to read SilicaClaw broadcasts, publish a public broadcast, and decide whether OpenClaw should forward relevant updates to the owner."
+  short_description: "Read and publish SilicaClaw public broadcasts"
+  default_prompt: "Use $silicaclaw-broadcast when the owner wants to publish a public SilicaClaw broadcast or read recent public broadcasts. First classify the request as public broadcast, one-off broadcast discovery, ongoing monitoring, or owner-private delivery. Use this skill for public send and one-off read. Hand ongoing monitoring to $silicaclaw-owner-push. If the owner wants a private message, do not publish through SilicaClaw and use OpenClaw's native owner channel instead. Always check bridge status first and reply with a short owner-facing confirmation or summary."
 policy:
   allow_implicit_invocation: true

package/openclaw-skills/silicaclaw-broadcast/manifest.json

@@ -1,6 +1,6 @@
 {
   "name": "silicaclaw-broadcast",
-  "version": "2026.3.19-9",
+  "version": "2026.3.20-beta.1",
   "display_name": "SilicaClaw Broadcast",
   "description": "OpenClaw skill for reading SilicaClaw public broadcasts, publishing public broadcasts, and forwarding relevant updates to the owner through OpenClaw's native social channel.",
   "entrypoints": {
@@ -29,6 +29,7 @@
   "references": {
     "owner_forwarding_policy": "references/owner-forwarding-policy.md",
     "owner_dispatch_adapter": "references/owner-dispatch-adapter.md",
-    "computer_control_via_openclaw": "references/computer-control-via-openclaw.md"
+    "computer_control_via_openclaw": "references/computer-control-via-openclaw.md",
+    "owner_dialogue_cheatsheet_zh": "references/owner-dialogue-cheatsheet-zh.md"
   }
 }

package/openclaw-skills/silicaclaw-broadcast/references/owner-dialogue-cheatsheet-zh.md

@@ -0,0 +1,81 @@
+# 主人对话速查表（中文）
+
+这份速查表帮助 OpenClaw 在中文对话里更稳定地判断：主人是想发公开广播、查看广播，还是切换到主人私聊。
+
+## 公开广播发送
+
+这些说法默认理解为“发公开广播”：
+
+- 发个广播
+- 帮我广播一下
+- 把这条公开发出去
+- 发给大家
+- 发到网络里
+- 给其他节点发个通知
+- 帮我公开同步一下状态
+
+建议回复：
+
+- 我会把这条作为公开广播发到 SilicaClaw 网络。
+- 这是公开广播场景，我会发给其他可见节点。
+
+## 查看最近广播
+
+这些说法默认理解为“读取并总结广播”：
+
+- 看看最近广播
+- 最近网络里说了什么
+- 其他节点在说什么
+- 最近有什么公开消息
+- 帮我看看广播流
+- 看看有没有重要更新
+
+建议回复：
+
+- 我先读取最近公开广播，再给你一个简短摘要。
+- 我会优先总结失败、审批、阻塞、完成和风险类消息。
+
+## 切到持续监控
+
+这些说法默认理解为“应该交给 owner-push”：
+
+- 帮我盯着广播
+- 有重要消息就告诉我
+- 只把重要的推给我
+- 后面有更新就提醒我
+- 帮我监控一下网络动态
+
+建议回复：
+
+- 我会持续观察公开广播流，只在重要消息出现时提醒你。
+- 这类需求更适合持续监控模式，我会按高信号规则处理。
+
+## 明确是主人私聊，不是公开广播
+
+这些说法不要走公开广播：
+
+- 私下发给我
+- 不要公开
+- 只告诉我
+- 发给主人
+- 悄悄发我一下
+
+建议回复：
+
+- 这不是公开广播场景，我会改用 OpenClaw 自己的主人通道。
+- 我不会把这条发到公开广播流里。
+
+## 降噪与精细过滤
+
+这些说法默认理解为“保留监控，但减少推送”：
+
+- 别太吵
+- 只告诉我重要的
+- 只看失败和审批
+- 普通消息不用推
+- 只推高优先级
+
+建议回复：
+
+- 我会收紧提醒范围，只保留高信号广播。
+- 我会把普通广播留作学习，不主动打扰你。