sophhub 0.4.19 → 0.4.21

package/skills/compact-context/src/scripts/setup.sh

@@ -1,96 +1,96 @@
-#!/usr/bin/env bash
-# Set up post-compaction context refresh rules in personal ~/.agents/AGENTS.md
-# Usage: bash setup.sh
-# Safe to run multiple times.
-
-set -euo pipefail
-
-PERSONAL_AGENTS="$HOME/.agents/AGENTS.md"
-
-GREEN='\033[0;32m'
-YELLOW='\033[1;33m'
-CYAN='\033[0;36m'
-BOLD='\033[1m'
-RESET='\033[0m'
-
-echo ""
-echo -e "${BOLD}━━━ Compact Context Setup ━━━${RESET}"
-echo ""
-
-mkdir -p "$HOME/.agents"
-[ -f "$PERSONAL_AGENTS" ] || : > "$PERSONAL_AGENTS"
-
-PYTHON_OUTPUT="$(python3 - "$PERSONAL_AGENTS" <<'PY'
-import pathlib
-import re
-import sys
-
-path = pathlib.Path(sys.argv[1])
-text = path.read_text(encoding="utf-8") if path.exists() else ""
-
-startup_block = """## Session Startup
-
-Context may have been compacted. When you see `[Post-compaction context refresh]` in your context:
-1. Re-read any task files mentioned in the conversation before responding.
-2. Treat missing earlier conversation details as incomplete context, not as proof they never happened.
-3. If you need to mention compaction to the user, describe it naturally; do not force a fixed reply prefix.
-"""
-
-red_lines_block = """## Red Lines
-
-- After compaction, re-read task context files before proceeding.
-- Never assume conversation history is complete after a `[Post-compaction context refresh]`.
-- Do not force a fixed reply prefix after compaction.
-"""
-
-legacy = "（已压缩，从摘要恢复）" in text or "Start your reply with:" in text
-
-def upsert_section(source: str, title: str, block: str) -> tuple[str, bool]:
-    pattern = rf"(?ms)^## {re.escape(title)}\n.*?(?=^## |\Z)"
-    if re.search(pattern, source):
-      return re.sub(pattern, block + "\n", source), True
-    source = source.rstrip()
-    if source:
-      source += "\n\n"
-    source += block + "\n"
-    return source, False
-
-updated, startup_exists = upsert_section(text, "Session Startup", startup_block)
-updated, red_lines_exists = upsert_section(updated, "Red Lines", red_lines_block)
-updated = updated.rstrip() + "\n"
-path.write_text(updated, encoding="utf-8")
-
-print(f"startup_exists={'1' if startup_exists else '0'}")
-print(f"red_lines_exists={'1' if red_lines_exists else '0'}")
-print(f"legacy={'1' if legacy else '0'}")
-PY
-)"
-
-STARTUP_EXISTS="$(printf '%s\n' "$PYTHON_OUTPUT" | awk -F= '/^startup_exists=/{print $2}')"
-RED_LINES_EXISTS="$(printf '%s\n' "$PYTHON_OUTPUT" | awk -F= '/^red_lines_exists=/{print $2}')"
-LEGACY_FOUND="$(printf '%s\n' "$PYTHON_OUTPUT" | awk -F= '/^legacy=/{print $2}')"
-
-if [ "$STARTUP_EXISTS" = "1" ]; then
-  echo -e "${GREEN}✔ ## Session Startup updated${RESET} in $PERSONAL_AGENTS"
-else
-  echo -e "${GREEN}✔ ## Session Startup added${RESET} to $PERSONAL_AGENTS"
-fi
-
-if [ "$RED_LINES_EXISTS" = "1" ]; then
-  echo -e "${GREEN}✔ ## Red Lines updated${RESET} in $PERSONAL_AGENTS"
-else
-  echo -e "${GREEN}✔ ## Red Lines added${RESET} to $PERSONAL_AGENTS"
-fi
-
-if [ "$LEGACY_FOUND" = "1" ]; then
-  echo -e "${YELLOW}○ Legacy fixed-prefix rules were replaced with safer recovery guidance.${RESET}"
-fi
-
-echo ""
-echo -e "${BOLD}Done.${RESET} Verify with: ${CYAN}bash check.sh${RESET}"
-echo ""
-echo -e "What happens next:"
-echo -e "  • Every auto-compact can still re-inject your recovery rules"
-echo -e "  • Agent will re-read task files after a context refresh"
-echo -e "  • Replies are no longer forced to start with a fixed compaction prefix"
-echo ""
+#!/usr/bin/env bash
+# Set up post-compaction context refresh rules in personal ~/.agents/AGENTS.md
+# Usage: bash setup.sh
+# Safe to run multiple times.
+
+set -euo pipefail
+
+PERSONAL_AGENTS="$HOME/.agents/AGENTS.md"
+
+GREEN='\033[0;32m'
+YELLOW='\033[1;33m'
+CYAN='\033[0;36m'
+BOLD='\033[1m'
+RESET='\033[0m'
+
+echo ""
+echo -e "${BOLD}━━━ Compact Context Setup ━━━${RESET}"
+echo ""
+
+mkdir -p "$HOME/.agents"
+[ -f "$PERSONAL_AGENTS" ] || : > "$PERSONAL_AGENTS"
+
+PYTHON_OUTPUT="$(python3 - "$PERSONAL_AGENTS" <<'PY'
+import pathlib
+import re
+import sys
+
+path = pathlib.Path(sys.argv[1])
+text = path.read_text(encoding="utf-8") if path.exists() else ""
+
+startup_block = """## Session Startup
+
+Context may have been compacted. When you see `[Post-compaction context refresh]` in your context:
+1. Re-read any task files mentioned in the conversation before responding.
+2. Treat missing earlier conversation details as incomplete context, not as proof they never happened.
+3. If you need to mention compaction to the user, describe it naturally; do not force a fixed reply prefix.
+"""
+
+red_lines_block = """## Red Lines
+
+- After compaction, re-read task context files before proceeding.
+- Never assume conversation history is complete after a `[Post-compaction context refresh]`.
+- Do not force a fixed reply prefix after compaction.
+"""
+
+legacy = "（已压缩，从摘要恢复）" in text or "Start your reply with:" in text
+
+def upsert_section(source: str, title: str, block: str) -> tuple[str, bool]:
+    pattern = rf"(?ms)^## {re.escape(title)}\n.*?(?=^## |\Z)"
+    if re.search(pattern, source):
+      return re.sub(pattern, block + "\n", source), True
+    source = source.rstrip()
+    if source:
+      source += "\n\n"
+    source += block + "\n"
+    return source, False
+
+updated, startup_exists = upsert_section(text, "Session Startup", startup_block)
+updated, red_lines_exists = upsert_section(updated, "Red Lines", red_lines_block)
+updated = updated.rstrip() + "\n"
+path.write_text(updated, encoding="utf-8")
+
+print(f"startup_exists={'1' if startup_exists else '0'}")
+print(f"red_lines_exists={'1' if red_lines_exists else '0'}")
+print(f"legacy={'1' if legacy else '0'}")
+PY
+)"
+
+STARTUP_EXISTS="$(printf '%s\n' "$PYTHON_OUTPUT" | awk -F= '/^startup_exists=/{print $2}')"
+RED_LINES_EXISTS="$(printf '%s\n' "$PYTHON_OUTPUT" | awk -F= '/^red_lines_exists=/{print $2}')"
+LEGACY_FOUND="$(printf '%s\n' "$PYTHON_OUTPUT" | awk -F= '/^legacy=/{print $2}')"
+
+if [ "$STARTUP_EXISTS" = "1" ]; then
+  echo -e "${GREEN}✔ ## Session Startup updated${RESET} in $PERSONAL_AGENTS"
+else
+  echo -e "${GREEN}✔ ## Session Startup added${RESET} to $PERSONAL_AGENTS"
+fi
+
+if [ "$RED_LINES_EXISTS" = "1" ]; then
+  echo -e "${GREEN}✔ ## Red Lines updated${RESET} in $PERSONAL_AGENTS"
+else
+  echo -e "${GREEN}✔ ## Red Lines added${RESET} to $PERSONAL_AGENTS"
+fi
+
+if [ "$LEGACY_FOUND" = "1" ]; then
+  echo -e "${YELLOW}○ Legacy fixed-prefix rules were replaced with safer recovery guidance.${RESET}"
+fi
+
+echo ""
+echo -e "${BOLD}Done.${RESET} Verify with: ${CYAN}bash check.sh${RESET}"
+echo ""
+echo -e "What happens next:"
+echo -e "  • Every auto-compact can still re-inject your recovery rules"
+echo -e "  • Agent will re-read task files after a context refresh"
+echo -e "  • Replies are no longer forced to start with a fixed compaction prefix"
+echo ""

package/skills/consensus/skill.json

@@ -1,20 +1,20 @@
-{
-  "name": "consensus",
-  "version": "1.0.0",
-  "types": [
-    "store"
-  ],
-  "displayName": "商务沟通skill",
-  "description": "将零散想法、产品介绍或方案说明，重构成更专业、更清晰、更有对象感的表达",
-  "changelog": [
-    {
-      "version": "1.0.0",
-      "date": "2026-04-14",
-      "changes": [
-        "初次提交"
-      ]
-    }
-  ],
-  "createdAt": "2026-04-14",
-  "updatedAt": "2026-04-14"
-}
+{
+  "name": "consensus",
+  "version": "1.0.0",
+  "types": [
+    "store"
+  ],
+  "displayName": "商务沟通skill",
+  "description": "将零散想法、产品介绍或方案说明，重构成更专业、更清晰、更有对象感的表达",
+  "changelog": [
+    {
+      "version": "1.0.0",
+      "date": "2026-04-14",
+      "changes": [
+        "初次提交"
+      ]
+    }
+  ],
+  "createdAt": "2026-04-14",
+  "updatedAt": "2026-04-14"
+}

package/skills/consensus/src/SKILL.md

@@ -1,93 +1,93 @@
----
-name: consensus
-description: |
-  将零散想法、内部表述、产品介绍或方案说明，重构成更专业、更清晰、更有对象感的表达。
-  适用于润色表达、专业化改写、名词定义、场景化解释、客户话术、伙伴话术、行业化表达与共识对齐。
-commands:
-  - /consensus rewrite - 将原始表述改写成更专业清晰的版本
-  - /consensus align - 面向客户、伙伴或内部协作做共识对齐
-  - /consensus define - 定义关键名词并澄清概念边界
-metadata:
-  openclaw:
-    emoji: "🤝"
-    requires:
-      bins: []
-      env: []
----
-
-# Consensus
-
-把用户“已经想明白但还没讲明白”的内容，整理成更专业、更清晰、可复用、面向对象的表达，可直接用于客户沟通、伙伴沟通或内部协作。
-
-## 适用场景
-
-当出现以下需求时，使用这个 skill：
-
-- 用户想把原始表达说得更专业
-- 用户想把内部语言改成客户能听懂的话
-- 用户想定义关键名词或澄清概念边界
-- 用户想把能力翻译成场景、问题和价值
-- 用户想分别产出客户版、伙伴版或内部协作版表达
-
-以下情况不要使用：
-
-- 需要真实行业数据，但上下文没有提供
-- 法律、财务、合规类正式意见
-- 只做轻量语法修正，不涉及结构重写
-
-## 默认工作流
-
-1. 先判断用户真正想表达的核心意图，不要只改字句。
-2. 找出关键名词、黑话和技术词，先定义，再展开。
-3. 把表达从“我们想说什么”改成“对方需要听懂什么”。
-4. 把功能翻译成场景、问题、价值和落地方式。
-5. 根据对象和使用场景，产出可直接复用的话术版本。
-
-优先使用下面这条翻译链路：
-
-`能力或做法 -> 解决的问题 -> 适用场景 -> 业务价值 -> 协作或落地方式`
-
-## 输入处理
-
-输入可以很粗糙，例如一句话、几条关键词、一段内部表述，或一段混乱说明。
-
-默认识别这四件事：
-
-- 核心意图
-- 目标对象
-- 行业或场景
-- 输出用途
-
-如果信息不完整：
-
-- 能安全推断就直接推断，并明确写出假设
-- 不能安全推断时，只追问最关键的一个缺口
-
-## 输出结构
-
-除非用户明确要求极短输出，否则默认按下面顺序组织：
-
-1. 核心表达
-2. 关键名词定义
-3. 场景化解释
-4. 面向对象的话术
-5. 待确认项
-
-## 写作规则
-
-- 先定义，后展开
-- 先场景，后功能
-- 先价值，后细节
-- 少黑话，少空话
-- 不编事实
-- 不把推测写成事实
-- 尽量让结果可以直接发给客户或伙伴
-
-## 最终检查
-
-输出前检查：
-
-- 陌生读者能否快速听懂
-- 关键名词是否已定义
-- 是否完成对象视角和场景视角转换
-- 是否保留了假设和边界
+---
+name: consensus
+description: |
+  将零散想法、内部表述、产品介绍或方案说明，重构成更专业、更清晰、更有对象感的表达。
+  适用于润色表达、专业化改写、名词定义、场景化解释、客户话术、伙伴话术、行业化表达与共识对齐。
+commands:
+  - /consensus rewrite - 将原始表述改写成更专业清晰的版本
+  - /consensus align - 面向客户、伙伴或内部协作做共识对齐
+  - /consensus define - 定义关键名词并澄清概念边界
+metadata:
+  openclaw:
+    emoji: "🤝"
+    requires:
+      bins: []
+      env: []
+---
+
+# Consensus
+
+把用户“已经想明白但还没讲明白”的内容，整理成更专业、更清晰、可复用、面向对象的表达，可直接用于客户沟通、伙伴沟通或内部协作。
+
+## 适用场景
+
+当出现以下需求时，使用这个 skill：
+
+- 用户想把原始表达说得更专业
+- 用户想把内部语言改成客户能听懂的话
+- 用户想定义关键名词或澄清概念边界
+- 用户想把能力翻译成场景、问题和价值
+- 用户想分别产出客户版、伙伴版或内部协作版表达
+
+以下情况不要使用：
+
+- 需要真实行业数据，但上下文没有提供
+- 法律、财务、合规类正式意见
+- 只做轻量语法修正，不涉及结构重写
+
+## 默认工作流
+
+1. 先判断用户真正想表达的核心意图，不要只改字句。
+2. 找出关键名词、黑话和技术词，先定义，再展开。
+3. 把表达从“我们想说什么”改成“对方需要听懂什么”。
+4. 把功能翻译成场景、问题、价值和落地方式。
+5. 根据对象和使用场景，产出可直接复用的话术版本。
+
+优先使用下面这条翻译链路：
+
+`能力或做法 -> 解决的问题 -> 适用场景 -> 业务价值 -> 协作或落地方式`
+
+## 输入处理
+
+输入可以很粗糙，例如一句话、几条关键词、一段内部表述，或一段混乱说明。
+
+默认识别这四件事：
+
+- 核心意图
+- 目标对象
+- 行业或场景
+- 输出用途
+
+如果信息不完整：
+
+- 能安全推断就直接推断，并明确写出假设
+- 不能安全推断时，只追问最关键的一个缺口
+
+## 输出结构
+
+除非用户明确要求极短输出，否则默认按下面顺序组织：
+
+1. 核心表达
+2. 关键名词定义
+3. 场景化解释
+4. 面向对象的话术
+5. 待确认项
+
+## 写作规则
+
+- 先定义，后展开
+- 先场景，后功能
+- 先价值，后细节
+- 少黑话，少空话
+- 不编事实
+- 不把推测写成事实
+- 尽量让结果可以直接发给客户或伙伴
+
+## 最终检查
+
+输出前检查：
+
+- 陌生读者能否快速听懂
+- 关键名词是否已定义
+- 是否完成对象视角和场景视角转换
+- 是否保留了假设和边界

package/skills/deepwiki/skill.json

@@ -1,20 +1,20 @@
-{
-  "name": "deepwiki",
-  "version": "1.0.0",
-  "types": [
-    "store"
-  ],
-  "displayName": "DeepWiki文档助手",
-  "description": "通过 DeepWiki MCP 服务器查询 GitHub 仓库文档和维基，支持搜索仓库维基、获取文档结构以及基于 AI 的仓库相关问题解答",
-  "changelog": [
-    {
-      "version": "1.0.0",
-      "date": "2026-04-14",
-      "changes": [
-        "初次提交"
-      ]
-    }
-  ],
-  "createdAt": "2026-04-14",
-  "updatedAt": "2026-04-14"
-}
+{
+  "name": "deepwiki",
+  "version": "1.0.0",
+  "types": [
+    "store"
+  ],
+  "displayName": "DeepWiki文档助手",
+  "description": "通过 DeepWiki MCP 服务器查询 GitHub 仓库文档和维基，支持搜索仓库维基、获取文档结构以及基于 AI 的仓库相关问题解答",
+  "changelog": [
+    {
+      "version": "1.0.0",
+      "date": "2026-04-14",
+      "changes": [
+        "初次提交"
+      ]
+    }
+  ],
+  "createdAt": "2026-04-14",
+  "updatedAt": "2026-04-14"
+}

package/skills/deepwiki/src/SKILL.md

@@ -1,45 +1,45 @@
----
-name: deepwiki
-description: Query GitHub repository documentation and wikis using DeepWiki MCP server. Use when the user needs to search repository wikis, get documentation structure, or ask AI-powered questions about GitHub repositories.
----
-
-# DeepWiki
-
-Use this skill to access documentation for public GitHub repositories via the DeepWiki MCP server. You can search repository wikis, get structure, and ask complex questions grounded in the repository's documentation.
-
-## Commands
-
-### Ask Question
-Ask any question about a GitHub repository and get an AI-powered, context-grounded response.
-```bash
-node ./scripts/deepwiki.js ask <owner/repo> "your question"
-```
-
-### Read Wiki Structure
-Get a list of documentation topics for a GitHub repository.
-```bash
-node ./scripts/deepwiki.js structure <owner/repo>
-```
-
-### Read Wiki Contents
-View documentation about a specific path in a GitHub repository's wiki.
-```bash
-node ./scripts/deepwiki.js contents <owner/repo> <path>
-```
-
-## Examples
-
-**Ask about Devin's MCP usage:**
-```bash
-node ./scripts/deepwiki.js ask cognitionlabs/devin "How do I use MCP?"
-```
-
-**Get the structure for the React docs:**
-```bash
-node ./scripts/deepwiki.js structure facebook/react
-```
-
-## Notes
-- Base Server: `https://mcp.deepwiki.com/mcp`
-- Works for public repositories only.
-- No authentication required.
+---
+name: deepwiki
+description: Query GitHub repository documentation and wikis using DeepWiki MCP server. Use when the user needs to search repository wikis, get documentation structure, or ask AI-powered questions about GitHub repositories.
+---
+
+# DeepWiki
+
+Use this skill to access documentation for public GitHub repositories via the DeepWiki MCP server. You can search repository wikis, get structure, and ask complex questions grounded in the repository's documentation.
+
+## Commands
+
+### Ask Question
+Ask any question about a GitHub repository and get an AI-powered, context-grounded response.
+```bash
+node ./scripts/deepwiki.js ask <owner/repo> "your question"
+```
+
+### Read Wiki Structure
+Get a list of documentation topics for a GitHub repository.
+```bash
+node ./scripts/deepwiki.js structure <owner/repo>
+```
+
+### Read Wiki Contents
+View documentation about a specific path in a GitHub repository's wiki.
+```bash
+node ./scripts/deepwiki.js contents <owner/repo> <path>
+```
+
+## Examples
+
+**Ask about Devin's MCP usage:**
+```bash
+node ./scripts/deepwiki.js ask cognitionlabs/devin "How do I use MCP?"
+```
+
+**Get the structure for the React docs:**
+```bash
+node ./scripts/deepwiki.js structure facebook/react
+```
+
+## Notes
+- Base Server: `https://mcp.deepwiki.com/mcp`
+- Works for public repositories only.
+- No authentication required.

package/skills/deepwiki/src/_meta.json

@@ -1,6 +1,6 @@
-{
-  "ownerId": "kn7azq5e6sw0fbwwzdpcwvvjzd7z0x4z",
-  "slug": "deepwiki",
-  "version": "1.0.0",
-  "publishedAt": 1768156757977
+{
+  "ownerId": "kn7azq5e6sw0fbwwzdpcwvvjzd7z0x4z",
+  "slug": "deepwiki",
+  "version": "1.0.0",
+  "publishedAt": 1768156757977
 }