@silicaclaw/cli 2026.3.19-2 → 2026.3.19-21

package/node_modules/vary/README.md

@@ -0,0 +1,101 @@
+# vary
+
+[![NPM Version][npm-image]][npm-url]
+[![NPM Downloads][downloads-image]][downloads-url]
+[![Node.js Version][node-version-image]][node-version-url]
+[![Build Status][travis-image]][travis-url]
+[![Test Coverage][coveralls-image]][coveralls-url]
+
+Manipulate the HTTP Vary header
+
+## Installation
+
+This is a [Node.js](https://nodejs.org/en/) module available through the
+[npm registry](https://www.npmjs.com/). Installation is done using the
+[`npm install` command](https://docs.npmjs.com/getting-started/installing-npm-packages-locally): 
+
+```sh
+$ npm install vary
+```
+
+## API
+
+<!-- eslint-disable no-unused-vars -->
+
+```js
+var vary = require('vary')
+```
+
+### vary(res, field)
+
+Adds the given header `field` to the `Vary` response header of `res`.
+This can be a string of a single field, a string of a valid `Vary`
+header, or an array of multiple fields.
+
+This will append the header if not already listed, otherwise leaves
+it listed in the current location.
+
+<!-- eslint-disable no-undef -->
+
+```js
+// Append "Origin" to the Vary header of the response
+vary(res, 'Origin')
+```
+
+### vary.append(header, field)
+
+Adds the given header `field` to the `Vary` response header string `header`.
+This can be a string of a single field, a string of a valid `Vary` header,
+or an array of multiple fields.
+
+This will append the header if not already listed, otherwise leaves
+it listed in the current location. The new header string is returned.
+
+<!-- eslint-disable no-undef -->
+
+```js
+// Get header string appending "Origin" to "Accept, User-Agent"
+vary.append('Accept, User-Agent', 'Origin')
+```
+
+## Examples
+
+### Updating the Vary header when content is based on it
+
+```js
+var http = require('http')
+var vary = require('vary')
+
+http.createServer(function onRequest (req, res) {
+  // about to user-agent sniff
+  vary(res, 'User-Agent')
+
+  var ua = req.headers['user-agent'] || ''
+  var isMobile = /mobi|android|touch|mini/i.test(ua)
+
+  // serve site, depending on isMobile
+  res.setHeader('Content-Type', 'text/html')
+  res.end('You are (probably) ' + (isMobile ? '' : 'not ') + 'a mobile user')
+})
+```
+
+## Testing
+
+```sh
+$ npm test
+```
+
+## License
+
+[MIT](LICENSE)
+
+[npm-image]: https://img.shields.io/npm/v/vary.svg
+[npm-url]: https://npmjs.org/package/vary
+[node-version-image]: https://img.shields.io/node/v/vary.svg
+[node-version-url]: https://nodejs.org/en/download
+[travis-image]: https://img.shields.io/travis/jshttp/vary/master.svg
+[travis-url]: https://travis-ci.org/jshttp/vary
+[coveralls-image]: https://img.shields.io/coveralls/jshttp/vary/master.svg
+[coveralls-url]: https://coveralls.io/r/jshttp/vary
+[downloads-image]: https://img.shields.io/npm/dm/vary.svg
+[downloads-url]: https://npmjs.org/package/vary

package/node_modules/vary/index.js

@@ -0,0 +1,149 @@
+/*!
+ * vary
+ * Copyright(c) 2014-2017 Douglas Christopher Wilson
+ * MIT Licensed
+ */
+
+'use strict'
+
+/**
+ * Module exports.
+ */
+
+module.exports = vary
+module.exports.append = append
+
+/**
+ * RegExp to match field-name in RFC 7230 sec 3.2
+ *
+ * field-name    = token
+ * token         = 1*tchar
+ * tchar         = "!" / "#" / "$" / "%" / "&" / "'" / "*"
+ *               / "+" / "-" / "." / "^" / "_" / "`" / "|" / "~"
+ *               / DIGIT / ALPHA
+ *               ; any VCHAR, except delimiters
+ */
+
+var FIELD_NAME_REGEXP = /^[!#$%&'*+\-.^_`|~0-9A-Za-z]+$/
+
+/**
+ * Append a field to a vary header.
+ *
+ * @param {String} header
+ * @param {String|Array} field
+ * @return {String}
+ * @public
+ */
+
+function append (header, field) {
+  if (typeof header !== 'string') {
+    throw new TypeError('header argument is required')
+  }
+
+  if (!field) {
+    throw new TypeError('field argument is required')
+  }
+
+  // get fields array
+  var fields = !Array.isArray(field)
+    ? parse(String(field))
+    : field
+
+  // assert on invalid field names
+  for (var j = 0; j < fields.length; j++) {
+    if (!FIELD_NAME_REGEXP.test(fields[j])) {
+      throw new TypeError('field argument contains an invalid header name')
+    }
+  }
+
+  // existing, unspecified vary
+  if (header === '*') {
+    return header
+  }
+
+  // enumerate current values
+  var val = header
+  var vals = parse(header.toLowerCase())
+
+  // unspecified vary
+  if (fields.indexOf('*') !== -1 || vals.indexOf('*') !== -1) {
+    return '*'
+  }
+
+  for (var i = 0; i < fields.length; i++) {
+    var fld = fields[i].toLowerCase()
+
+    // append value (case-preserving)
+    if (vals.indexOf(fld) === -1) {
+      vals.push(fld)
+      val = val
+        ? val + ', ' + fields[i]
+        : fields[i]
+    }
+  }
+
+  return val
+}
+
+/**
+ * Parse a vary header into an array.
+ *
+ * @param {String} header
+ * @return {Array}
+ * @private
+ */
+
+function parse (header) {
+  var end = 0
+  var list = []
+  var start = 0
+
+  // gather tokens
+  for (var i = 0, len = header.length; i < len; i++) {
+    switch (header.charCodeAt(i)) {
+      case 0x20: /*   */
+        if (start === end) {
+          start = end = i + 1
+        }
+        break
+      case 0x2c: /* , */
+        list.push(header.substring(start, end))
+        start = end = i + 1
+        break
+      default:
+        end = i + 1
+        break
+    }
+  }
+
+  // final token
+  list.push(header.substring(start, end))
+
+  return list
+}
+
+/**
+ * Mark that a request is varied on a header field.
+ *
+ * @param {Object} res
+ * @param {String|Array} field
+ * @public
+ */
+
+function vary (res, field) {
+  if (!res || !res.getHeader || !res.setHeader) {
+    // quack quack
+    throw new TypeError('res argument is required')
+  }
+
+  // get existing header
+  var val = res.getHeader('Vary') || ''
+  var header = Array.isArray(val)
+    ? val.join(', ')
+    : String(val)
+
+  // set new header
+  if ((val = append(header, field))) {
+    res.setHeader('Vary', val)
+  }
+}

package/node_modules/vary/package.json

@@ -0,0 +1,43 @@
+{
+  "name": "vary",
+  "description": "Manipulate the HTTP Vary header",
+  "version": "1.1.2",
+  "author": "Douglas Christopher Wilson <doug@somethingdoug.com>",
+  "license": "MIT",
+  "keywords": [
+    "http",
+    "res",
+    "vary"
+  ],
+  "repository": "jshttp/vary",
+  "devDependencies": {
+    "beautify-benchmark": "0.2.4",
+    "benchmark": "2.1.4",
+    "eslint": "3.19.0",
+    "eslint-config-standard": "10.2.1",
+    "eslint-plugin-import": "2.7.0",
+    "eslint-plugin-markdown": "1.0.0-beta.6",
+    "eslint-plugin-node": "5.1.1",
+    "eslint-plugin-promise": "3.5.0",
+    "eslint-plugin-standard": "3.0.1",
+    "istanbul": "0.4.5",
+    "mocha": "2.5.3",
+    "supertest": "1.1.0"
+  },
+  "files": [
+    "HISTORY.md",
+    "LICENSE",
+    "README.md",
+    "index.js"
+  ],
+  "engines": {
+    "node": ">= 0.8"
+  },
+  "scripts": {
+    "bench": "node benchmark/index.js",
+    "lint": "eslint --plugin markdown --ext js,md .",
+    "test": "mocha --reporter spec --bail --check-leaks test/",
+    "test-cov": "istanbul cover node_modules/mocha/bin/_mocha -- --reporter dot --check-leaks test/",
+    "test-travis": "istanbul cover node_modules/mocha/bin/_mocha --report lcovonly -- --reporter spec --check-leaks test/"
+  }
+}

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 还不能稳定学习这些广播能力。"
+- "现在公开广播链路没问题，但给主人的私下推送链路还没配完。"