Update nexus: fix conflicts and sync local changes
This commit is contained in:
Shen Wei
@@ -1,282 +1,282 @@
|
||||
---
|
||||
title: AgentMail 技能使用文档
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
---
|
||||
|
||||
# AgentMail 技能使用文档
|
||||
|
||||
> 基于实际案例整理：2026-04-04 处理 billyshen@163.com 发来的房屋合同图片
|
||||
|
||||
---
|
||||
|
||||
## 📬 AgentMail 是什么？
|
||||
|
||||
AgentMail 是一个 API-first 的邮件平台，专为 AI Agent 设计。它不是传统的 Gmail/Outlook，而是一个可以通过 API 创建邮箱、收发邮件、处理附件的平台。
|
||||
|
||||
**核心特点：**
|
||||
- 无 rate limit，适合 Agent 高频使用
|
||||
- 支持 Webhook 实时处理邮件
|
||||
- API 驱动，可编程控制
|
||||
|
||||
---
|
||||
|
||||
## 📋 环境配置
|
||||
|
||||
### 1. 安装 Python SDK
|
||||
|
||||
```bash
|
||||
pip3 install --break-system-packages agentmail python-dotenv
|
||||
```
|
||||
|
||||
### 2. 配置环境变量
|
||||
|
||||
在 `~/.openclaw/.env` 中添加：
|
||||
|
||||
```bash
|
||||
AGENTMAIL_API_KEY=your_api_key_here
|
||||
AGENTMAIL_EMAIL=star-agent@agentmail.to # 收件邮箱（可选）
|
||||
```
|
||||
|
||||
### 3. API Key 获取
|
||||
|
||||
登录 [console.agentmail.to](https://console.agentmail.to) → Dashboard → 生成 API Key
|
||||
|
||||
---
|
||||
|
||||
## 🔄 核心工作流程
|
||||
|
||||
### 步骤 1：读取邮件
|
||||
|
||||
```python
|
||||
import os
|
||||
from agentmail import AgentMail
|
||||
|
||||
client = AgentMail(api_key=os.getenv('AGENTMAIL_API_KEY'))
|
||||
|
||||
# 查看所有收件箱
|
||||
inboxes = client.inboxes.list(limit=10)
|
||||
for inbox in inboxes.inboxes:
|
||||
print(f"Inbox: {inbox.inbox_id}")
|
||||
print(f"Display name: {inbox.display_name}")
|
||||
|
||||
# 列出邮件
|
||||
messages = client.inboxes.messages.list(
|
||||
inbox_id='star-agent@agentmail.to',
|
||||
limit=10
|
||||
)
|
||||
for msg in messages.messages:
|
||||
print(f"From: {msg.from_}")
|
||||
print(f"Subject: {msg.subject}")
|
||||
print(f"Time: {msg.timestamp}")
|
||||
print(f"Attachments: {len(msg.attachments) if msg.attachments else 0}")
|
||||
```
|
||||
|
||||
### 步骤 2：获取邮件详情
|
||||
|
||||
```python
|
||||
# 获取单封邮件详情
|
||||
msg = client.inboxes.messages.get(
|
||||
inbox_id='star-agent@agentmail.to',
|
||||
message_id='<4c3b2d60.4e8d.19d56c37eb3.Coremail.billyshen@163.com>'
|
||||
)
|
||||
|
||||
print(f"Subject: {msg.subject}")
|
||||
print(f"Text: {msg.text}")
|
||||
print(f"Attachments count: {len(msg.attachments)}")
|
||||
|
||||
# 遍历附件
|
||||
for att in msg.attachments:
|
||||
print(f" - {att.filename} ({att.size} bytes)")
|
||||
print(f" Content type: {att.content_type}")
|
||||
print(f" Attachment ID: {att.attachment_id}")
|
||||
```
|
||||
|
||||
### 步骤 3：下载附件
|
||||
|
||||
AgentMail 的附件需要通过两步获取：
|
||||
1. 获取附件的下载 URL
|
||||
2. 用下载 URL 获取文件内容
|
||||
|
||||
```python
|
||||
import httpx
|
||||
import urllib.parse
|
||||
|
||||
api_key = os.getenv('AGENTMAIL_API_KEY')
|
||||
msg_id = urllib.parse.quote('<4c3b2d60.4e8d.19d56c37eb3.Coremail.billyshen@163.com>')
|
||||
|
||||
# 遍历所有附件并下载
|
||||
for att in msg.attachments:
|
||||
att_id = att.attachment_id
|
||||
filename = att.filename
|
||||
|
||||
# 获取下载链接
|
||||
resp = httpx.get(
|
||||
f"https://api.agentmail.to/v0/inboxes/star-agent@agentmail.to/messages/{msg_id}/attachments/{att_id}",
|
||||
headers={"Authorization": f"Bearer {api_key}"},
|
||||
timeout=30.0
|
||||
)
|
||||
download_url = resp.json()['download_url']
|
||||
|
||||
# 下载文件
|
||||
img_resp = httpx.get(download_url, timeout=60.0)
|
||||
local_path = f'/tmp/{filename}'
|
||||
with open(local_path, 'wb') as f:
|
||||
f.write(img_resp.content)
|
||||
print(f"Downloaded: {local_path}")
|
||||
```
|
||||
|
||||
### 步骤 4：发送邮件
|
||||
|
||||
```python
|
||||
client.inboxes.messages.send(
|
||||
inbox_id='star-agent@agentmail.to',
|
||||
to='recipient@example.com',
|
||||
subject='主题',
|
||||
text='正文内容',
|
||||
attachments=[{
|
||||
'filename': 'report.pdf',
|
||||
'content': base64.b64encode(file_data).decode()
|
||||
}]
|
||||
)
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## ⚠️ 注意事项
|
||||
|
||||
### 1. 代理问题
|
||||
|
||||
如果系统配置了 SOCKS5 代理，需要在调用前取消代理设置：
|
||||
|
||||
```python
|
||||
import os
|
||||
os.environ.pop('HTTP_PROXY', None)
|
||||
os.environ.pop('HTTPS_PROXY', None)
|
||||
os.environ.pop('http_proxy', None)
|
||||
os.environ.pop('https_proxy', None)
|
||||
```
|
||||
|
||||
或者在执行命令时 unset：
|
||||
|
||||
```bash
|
||||
unset HTTP_PROXY && unset HTTPS_PROXY && unset http_proxy && unset https_proxy
|
||||
python3 script.py
|
||||
```
|
||||
|
||||
### 2. 附件 API 路径
|
||||
|
||||
附件信息在邮件列表中不包含 `content` 字段，需要单独调用 `/attachments/{attachment_id}` 端点获取 `download_url`。
|
||||
|
||||
### 3. httpx 的 SOCKS 支持
|
||||
|
||||
如果遇到 `ImportError: Using SOCKS proxy, but the 'socksio' package is not installed`：
|
||||
|
||||
```bash
|
||||
pip3 install --break-system-packages socksio httpx
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 📝 实际案例：处理邮件中的图片附件
|
||||
|
||||
### 场景
|
||||
用户通过 163 邮箱发送了 6 张图片到 `star-agent@agentmail.to`，要求识别图片文字并生成 Word 文档。
|
||||
|
||||
### 执行过程
|
||||
|
||||
```python
|
||||
import os
|
||||
import httpx
|
||||
from agentmail import AgentMail
|
||||
|
||||
client = AgentMail(api_key=os.getenv('AGENTMAIL_API_KEY'))
|
||||
|
||||
# 1. 获取邮件
|
||||
msg = client.inboxes.messages.get(
|
||||
inbox_id='star-agent@agentmail.to',
|
||||
message_id='<4c3b2d60.4e8d.19d56c37eb3.Coremail.billyshen@163.com>'
|
||||
)
|
||||
|
||||
print(f"Subject: {msg.subject}")
|
||||
print(f"Attachments: {len(msg.attachments)}")
|
||||
|
||||
# 2. 下载所有图片
|
||||
os.makedirs('/tmp/ocr_images', exist_ok=True)
|
||||
|
||||
for i, att in enumerate(msg.attachments):
|
||||
att_id = att.attachment_id
|
||||
filename = att.filename
|
||||
|
||||
resp = httpx.get(
|
||||
f"https://api.agentmail.to/v0/inboxes/star-agent@agentmail.to/messages/{urllib.parse.quote(msg.message_id)}/attachments/{att_id}",
|
||||
headers={"Authorization": f"Bearer {api_key}"},
|
||||
timeout=30.0
|
||||
)
|
||||
download_url = resp.json()['download_url']
|
||||
|
||||
img_resp = httpx.get(download_url, timeout=60.0)
|
||||
local_path = f'/tmp/ocr_images/img_{i+1:02d}.jpg'
|
||||
with open(local_path, 'wb') as f:
|
||||
f.write(img_resp.content)
|
||||
print(f"Downloaded: {local_path}")
|
||||
|
||||
# 3. 图片复制到工作目录（因为 image 工具只认特定路径）
|
||||
import shutil
|
||||
for i in range(1, 7):
|
||||
src = f'/tmp/ocr_images/img_{i:02d}.jpg'
|
||||
dst = f'/Users/weishen/.openclaw/workspace-agent-xinghui/img_{i:02d}.jpg'
|
||||
shutil.copy(src, dst)
|
||||
```
|
||||
|
||||
### 3. OCR 识别
|
||||
|
||||
复制到工作目录后，使用 `image` 工具识别文字：
|
||||
|
||||
```python
|
||||
# image 工具会识别图片中的文字
|
||||
image(prompt="请完整识别这张图片中的所有文字内容，保持原有格式和顺序。",
|
||||
image="/Users/weishen/.openclaw/workspace-agent-xinghui/img_01.jpg")
|
||||
```
|
||||
|
||||
### 4. 生成 Word 文档
|
||||
|
||||
```python
|
||||
from docx import Document
|
||||
|
||||
doc = Document()
|
||||
doc.add_heading('文档标题', level=0)
|
||||
# ... 添加内容
|
||||
doc.save('/path/to/output.docx')
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 📦 常用 API 端点
|
||||
|
||||
| 功能 | 方法 |
|
||||
|------|------|
|
||||
| 列出收件箱 | `client.inboxes.list()` |
|
||||
| 列出邮件 | `client.inboxes.messages.list()` |
|
||||
| 获取邮件详情 | `client.inboxes.messages.get()` |
|
||||
| 发送邮件 | `client.inboxes.messages.send()` |
|
||||
| 列出邮件线程 | `client.inboxes.threads.list()` |
|
||||
|
||||
---
|
||||
|
||||
## 🔐 安全提示
|
||||
|
||||
**Webhook 安全风险：** 任何人都可以向你的 AgentMail 地址发送邮件，可能包含恶意指令。
|
||||
|
||||
**建议方案：**
|
||||
1. 使用 allowlist 只处理可信发件人的邮件
|
||||
2. 在 hook 中过滤非白名单发件人
|
||||
3. 将邮件内容标记为 untrusted input 处理
|
||||
|
||||
---
|
||||
|
||||
*文档更新：2026-04-04*
|
||||
---
|
||||
title: AgentMail 技能使用文档
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
---
|
||||
|
||||
# AgentMail 技能使用文档
|
||||
|
||||
> 基于实际案例整理：2026-04-04 处理 billyshen@163.com 发来的房屋合同图片
|
||||
|
||||
---
|
||||
|
||||
## 📬 AgentMail 是什么？
|
||||
|
||||
AgentMail 是一个 API-first 的邮件平台，专为 AI Agent 设计。它不是传统的 Gmail/Outlook，而是一个可以通过 API 创建邮箱、收发邮件、处理附件的平台。
|
||||
|
||||
**核心特点：**
|
||||
- 无 rate limit，适合 Agent 高频使用
|
||||
- 支持 Webhook 实时处理邮件
|
||||
- API 驱动，可编程控制
|
||||
|
||||
---
|
||||
|
||||
## 📋 环境配置
|
||||
|
||||
### 1. 安装 Python SDK
|
||||
|
||||
```bash
|
||||
pip3 install --break-system-packages agentmail python-dotenv
|
||||
```
|
||||
|
||||
### 2. 配置环境变量
|
||||
|
||||
在 `~/.openclaw/.env` 中添加：
|
||||
|
||||
```bash
|
||||
AGENTMAIL_API_KEY=your_api_key_here
|
||||
AGENTMAIL_EMAIL=star-agent@agentmail.to # 收件邮箱（可选）
|
||||
```
|
||||
|
||||
### 3. API Key 获取
|
||||
|
||||
登录 [console.agentmail.to](https://console.agentmail.to) → Dashboard → 生成 API Key
|
||||
|
||||
---
|
||||
|
||||
## 🔄 核心工作流程
|
||||
|
||||
### 步骤 1：读取邮件
|
||||
|
||||
```python
|
||||
import os
|
||||
from agentmail import AgentMail
|
||||
|
||||
client = AgentMail(api_key=os.getenv('AGENTMAIL_API_KEY'))
|
||||
|
||||
# 查看所有收件箱
|
||||
inboxes = client.inboxes.list(limit=10)
|
||||
for inbox in inboxes.inboxes:
|
||||
print(f"Inbox: {inbox.inbox_id}")
|
||||
print(f"Display name: {inbox.display_name}")
|
||||
|
||||
# 列出邮件
|
||||
messages = client.inboxes.messages.list(
|
||||
inbox_id='star-agent@agentmail.to',
|
||||
limit=10
|
||||
)
|
||||
for msg in messages.messages:
|
||||
print(f"From: {msg.from_}")
|
||||
print(f"Subject: {msg.subject}")
|
||||
print(f"Time: {msg.timestamp}")
|
||||
print(f"Attachments: {len(msg.attachments) if msg.attachments else 0}")
|
||||
```
|
||||
|
||||
### 步骤 2：获取邮件详情
|
||||
|
||||
```python
|
||||
# 获取单封邮件详情
|
||||
msg = client.inboxes.messages.get(
|
||||
inbox_id='star-agent@agentmail.to',
|
||||
message_id='<4c3b2d60.4e8d.19d56c37eb3.Coremail.billyshen@163.com>'
|
||||
)
|
||||
|
||||
print(f"Subject: {msg.subject}")
|
||||
print(f"Text: {msg.text}")
|
||||
print(f"Attachments count: {len(msg.attachments)}")
|
||||
|
||||
# 遍历附件
|
||||
for att in msg.attachments:
|
||||
print(f" - {att.filename} ({att.size} bytes)")
|
||||
print(f" Content type: {att.content_type}")
|
||||
print(f" Attachment ID: {att.attachment_id}")
|
||||
```
|
||||
|
||||
### 步骤 3：下载附件
|
||||
|
||||
AgentMail 的附件需要通过两步获取：
|
||||
1. 获取附件的下载 URL
|
||||
2. 用下载 URL 获取文件内容
|
||||
|
||||
```python
|
||||
import httpx
|
||||
import urllib.parse
|
||||
|
||||
api_key = os.getenv('AGENTMAIL_API_KEY')
|
||||
msg_id = urllib.parse.quote('<4c3b2d60.4e8d.19d56c37eb3.Coremail.billyshen@163.com>')
|
||||
|
||||
# 遍历所有附件并下载
|
||||
for att in msg.attachments:
|
||||
att_id = att.attachment_id
|
||||
filename = att.filename
|
||||
|
||||
# 获取下载链接
|
||||
resp = httpx.get(
|
||||
f"https://api.agentmail.to/v0/inboxes/star-agent@agentmail.to/messages/{msg_id}/attachments/{att_id}",
|
||||
headers={"Authorization": f"Bearer {api_key}"},
|
||||
timeout=30.0
|
||||
)
|
||||
download_url = resp.json()['download_url']
|
||||
|
||||
# 下载文件
|
||||
img_resp = httpx.get(download_url, timeout=60.0)
|
||||
local_path = f'/tmp/{filename}'
|
||||
with open(local_path, 'wb') as f:
|
||||
f.write(img_resp.content)
|
||||
print(f"Downloaded: {local_path}")
|
||||
```
|
||||
|
||||
### 步骤 4：发送邮件
|
||||
|
||||
```python
|
||||
client.inboxes.messages.send(
|
||||
inbox_id='star-agent@agentmail.to',
|
||||
to='recipient@example.com',
|
||||
subject='主题',
|
||||
text='正文内容',
|
||||
attachments=[{
|
||||
'filename': 'report.pdf',
|
||||
'content': base64.b64encode(file_data).decode()
|
||||
}]
|
||||
)
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## ⚠️ 注意事项
|
||||
|
||||
### 1. 代理问题
|
||||
|
||||
如果系统配置了 SOCKS5 代理，需要在调用前取消代理设置：
|
||||
|
||||
```python
|
||||
import os
|
||||
os.environ.pop('HTTP_PROXY', None)
|
||||
os.environ.pop('HTTPS_PROXY', None)
|
||||
os.environ.pop('http_proxy', None)
|
||||
os.environ.pop('https_proxy', None)
|
||||
```
|
||||
|
||||
或者在执行命令时 unset：
|
||||
|
||||
```bash
|
||||
unset HTTP_PROXY && unset HTTPS_PROXY && unset http_proxy && unset https_proxy
|
||||
python3 script.py
|
||||
```
|
||||
|
||||
### 2. 附件 API 路径
|
||||
|
||||
附件信息在邮件列表中不包含 `content` 字段，需要单独调用 `/attachments/{attachment_id}` 端点获取 `download_url`。
|
||||
|
||||
### 3. httpx 的 SOCKS 支持
|
||||
|
||||
如果遇到 `ImportError: Using SOCKS proxy, but the 'socksio' package is not installed`：
|
||||
|
||||
```bash
|
||||
pip3 install --break-system-packages socksio httpx
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 📝 实际案例：处理邮件中的图片附件
|
||||
|
||||
### 场景
|
||||
用户通过 163 邮箱发送了 6 张图片到 `star-agent@agentmail.to`，要求识别图片文字并生成 Word 文档。
|
||||
|
||||
### 执行过程
|
||||
|
||||
```python
|
||||
import os
|
||||
import httpx
|
||||
from agentmail import AgentMail
|
||||
|
||||
client = AgentMail(api_key=os.getenv('AGENTMAIL_API_KEY'))
|
||||
|
||||
# 1. 获取邮件
|
||||
msg = client.inboxes.messages.get(
|
||||
inbox_id='star-agent@agentmail.to',
|
||||
message_id='<4c3b2d60.4e8d.19d56c37eb3.Coremail.billyshen@163.com>'
|
||||
)
|
||||
|
||||
print(f"Subject: {msg.subject}")
|
||||
print(f"Attachments: {len(msg.attachments)}")
|
||||
|
||||
# 2. 下载所有图片
|
||||
os.makedirs('/tmp/ocr_images', exist_ok=True)
|
||||
|
||||
for i, att in enumerate(msg.attachments):
|
||||
att_id = att.attachment_id
|
||||
filename = att.filename
|
||||
|
||||
resp = httpx.get(
|
||||
f"https://api.agentmail.to/v0/inboxes/star-agent@agentmail.to/messages/{urllib.parse.quote(msg.message_id)}/attachments/{att_id}",
|
||||
headers={"Authorization": f"Bearer {api_key}"},
|
||||
timeout=30.0
|
||||
)
|
||||
download_url = resp.json()['download_url']
|
||||
|
||||
img_resp = httpx.get(download_url, timeout=60.0)
|
||||
local_path = f'/tmp/ocr_images/img_{i+1:02d}.jpg'
|
||||
with open(local_path, 'wb') as f:
|
||||
f.write(img_resp.content)
|
||||
print(f"Downloaded: {local_path}")
|
||||
|
||||
# 3. 图片复制到工作目录（因为 image 工具只认特定路径）
|
||||
import shutil
|
||||
for i in range(1, 7):
|
||||
src = f'/tmp/ocr_images/img_{i:02d}.jpg'
|
||||
dst = f'/Users/weishen/.openclaw/workspace-agent-xinghui/img_{i:02d}.jpg'
|
||||
shutil.copy(src, dst)
|
||||
```
|
||||
|
||||
### 3. OCR 识别
|
||||
|
||||
复制到工作目录后，使用 `image` 工具识别文字：
|
||||
|
||||
```python
|
||||
# image 工具会识别图片中的文字
|
||||
image(prompt="请完整识别这张图片中的所有文字内容，保持原有格式和顺序。",
|
||||
image="/Users/weishen/.openclaw/workspace-agent-xinghui/img_01.jpg")
|
||||
```
|
||||
|
||||
### 4. 生成 Word 文档
|
||||
|
||||
```python
|
||||
from docx import Document
|
||||
|
||||
doc = Document()
|
||||
doc.add_heading('文档标题', level=0)
|
||||
# ... 添加内容
|
||||
doc.save('/path/to/output.docx')
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 📦 常用 API 端点
|
||||
|
||||
| 功能 | 方法 |
|
||||
|------|------|
|
||||
| 列出收件箱 | `client.inboxes.list()` |
|
||||
| 列出邮件 | `client.inboxes.messages.list()` |
|
||||
| 获取邮件详情 | `client.inboxes.messages.get()` |
|
||||
| 发送邮件 | `client.inboxes.messages.send()` |
|
||||
| 列出邮件线程 | `client.inboxes.threads.list()` |
|
||||
|
||||
---
|
||||
|
||||
## 🔐 安全提示
|
||||
|
||||
**Webhook 安全风险：** 任何人都可以向你的 AgentMail 地址发送邮件，可能包含恶意指令。
|
||||
|
||||
**建议方案：**
|
||||
1. 使用 allowlist 只处理可信发件人的邮件
|
||||
2. 在 hook 中过滤非白名单发件人
|
||||
3. 将邮件内容标记为 untrusted input 处理
|
||||
|
||||
---
|
||||
|
||||
*文档更新：2026-04-04*
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@@ -127,7 +127,7 @@ cat ~/.ssh/id_ed25519.pub
|
||||
## 正确命令
|
||||
|
||||
```bash
|
||||
ssh -T git@192.168.3.189 -p 2222
|
||||
ssh -T git@192.168.3.17 -p 2222
|
||||
```
|
||||
|
||||
```
|
||||
@@ -220,7 +220,7 @@ http://192.168.3.189:3000/admin/nexus.git ❌
|
||||
## 2. 修改为 SSH
|
||||
|
||||
```bash
|
||||
git remote set-url origin ssh://git@192.168.3.189:2222/admin/nexus.git
|
||||
git remote set-url origin ssh://git@192.168.3.17:2222/ishenwei/nexus.git
|
||||
```
|
||||
## 3. 验证
|
||||
|
||||
|
||||
@@ -1,327 +1,327 @@
|
||||
---
|
||||
title: 如何让创造力「爆表」到感觉像在犯罪？7天重启大脑的终极指南
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
---
|
||||
|
||||
# 如何让创造力「爆表」到感觉像在犯罪？7天重启大脑的终极指南
|
||||
|
||||
你是否感觉大脑像被榨干了一样？创意枯竭，灵感消失？这可能是认知过载而非情绪疲劳。本文揭示创造力枯竭的三大元凶，并提供一套7天重启大脑的实用方法，让你找回那个充满灵感的自己。
|
||||
|
||||
# 如何让创造力「爆表」到感觉像在犯罪？7天重启大脑的终极指南
|
||||
|
||||
**作者：** DAN KOE（编译整理）
|
||||
**阅读时间：** 8分钟
|
||||
|
||||
---
|
||||
|
||||
## 一、那个大脑被「榨干」的时刻
|
||||
|
||||
最近几周，我感觉自己的大脑完全被榨干了。
|
||||
|
||||
你知道那种感觉——既在思考一切，又什么都没在想。当你试图思考、头脑风暴或想出一个好主意时，无论怎么努力，脑子里就是一片空白。
|
||||
|
||||
这更像是认知过载，而非情绪疲劳。我可以继续工作，但感觉自己不像个完整的人。
|
||||
|
||||
可能是压力太大。
|
||||
|
||||
可能是AI用太多了（最近我沉迷于各种AI工具）。
|
||||
|
||||
可能是写作习惯被打乱了（因为注意力转移到公司其他问题上，导致更多压力）。
|
||||
|
||||
就在上个月，好点子和写作对我来说还是轻而易举的事。我可以坐下来尽情写作，感觉质量不错，接近原创思考。
|
||||
|
||||
但这种情况持续越久，那种感觉就越强烈。
|
||||
|
||||
为什么我写不出来？我的所有想法都去哪儿了？
|
||||
|
||||
我该如何找回状态？
|
||||
|
||||
这就是我写这篇文章的首要目标——为你和我提供一个指南，帮助我们回到最具创造力的状态。
|
||||
|
||||
我的次要目标是向你展示，即使你不认为自己是个「有创造力的人」，也可以进入一种极其愉悦的意识状态。类似于心流状态，但可能更强大。
|
||||
|
||||
我的第三个目标是给你一个7天方案。如果你严格执行，你会从大脑被榨干的感觉中复活，变得充满活力。
|
||||
|
||||
因为在当今世界，你的创造力是最稀缺的资源。
|
||||
|
||||
任何人都可以建造任何东西，思考任何东西，写任何东西。在商业、写作、艺术和一般生活质量方面，能够选择最具创造性的道路的人将会获胜——那条别人从未考虑过的道路。
|
||||
|
||||
## 二、你没有想法的三大原因
|
||||
|
||||
### 1. 条件反射：好奇心的天敌
|
||||
|
||||
当你想到创造力时，你会想到孩子。
|
||||
|
||||
他们用如此新鲜的眼光看世界。如果一个孩子让ChatGPT建造一个传送装置，以便带朋友去另一个星系，没人会眨眼睛。但如果你这样做，人们会认为你是个不懂「世界如何运作」的白痴。
|
||||
|
||||
孩子们还没有从父母、老师和同龄人那里收到复合的负面反馈。他们还没有内化自己必须以某种方式行事，以适应这个破碎而无聊的社会。
|
||||
|
||||
你必须上学。
|
||||
|
||||
你必须尽力找一份高薪工作。
|
||||
|
||||
你必须赞美这个神，如果你不服从，你就会下地狱。
|
||||
|
||||
到大多数人20岁时，他们和其他人一样——相同的想法、行动和信仰类型。他们正在走分配给他们的生活道路，而不是他们选择创造的道路。
|
||||
|
||||
创造力需要宽松地持有信念，并在不立即拒绝或妖魔化的情况下考虑一个想法。
|
||||
|
||||
### 2. 生产力优先：必输的游戏
|
||||
|
||||
当朝九晚五的工作在工业化时期成为常态时，生产力成为最高价值。每个人都成为只学会放置一块拼图的专家，因为如果他们知道如何解决整个问题，他们就会是企业家而不是员工。
|
||||
|
||||
今天，每个人都觉得自己落后了（说实话，在一个你没有创造的游戏中，你永远也追不上。创造力是唯一的出路）。
|
||||
|
||||
你有一个永远迫在眉睫的最后期限。
|
||||
|
||||
一个紧张的大脑只担心生存，当你的神经系统被截止日期统治时，你看不到新的联系。
|
||||
|
||||
如果你的生活不是围绕优化和效率构建的（换句话说，如果你不是机器人），每个人都认为你毫无用处。但这正是创造力所需要的——无用的漫游。真正的无聊。为正确的想法创造空间，这将带你走得更远，比那些陷入与其他人相同竞赛的「生产力兄弟」更远。
|
||||
|
||||
### 3. 无限输入，零处理时间
|
||||
|
||||
你的新陈代谢只能这么快。
|
||||
|
||||
很明显，如果你吃太多食物，你会开始感觉迟钝，看起来也迟钝。是的，你会变胖。
|
||||
|
||||
但大多数人没有意识到这也适用于思维。
|
||||
|
||||
他们觉得如果一周不听10个播客，就无法「跟上」，尽管事实恰恰相反。他们的思维新陈代谢没有时间消化信息。
|
||||
|
||||
有一个时间用于精心策划的信息，帮助激发更多想法，但如果不严格控制，很快就会变得危险。
|
||||
|
||||
创造力很少是输入问题，但同样，你只能用冰箱里的东西做饭。问题是大多数人的冰箱里装满了冰淇淋和苏打水。
|
||||
|
||||
## 三、你不是无聊，你是过度刺激
|
||||
|
||||
"丹，我一直很无聊，我没有创造力。"
|
||||
|
||||
长期过度刺激和过度咖啡因摄入不是无聊。你被炸得如此彻底，以至于走到了另一端，并将其与无聊联系起来，因为你已经习惯了欣快感，以至于它变得无聊。你简直不能再往前走了，你必须往回走。
|
||||
|
||||
真正的无聊（在你的戒断期之后）会做几件事：
|
||||
|
||||
### 1. 无聊提供了通往新奇的大门
|
||||
|
||||
卡尔·荣格，OG心理学家，强调阴影工作的重要性——面对我们通常避免的不舒服的方面。
|
||||
|
||||
与无聊共处正是这样做的。
|
||||
|
||||
当理性思维停止试图解决一切时，它会激活突破性的见解。
|
||||
|
||||
它揭示了外部条件反射下我们真实的欲望。
|
||||
|
||||
它为3个心流触发器设置了场景，使你更有可能进入一个密集学习和建设的季节：
|
||||
|
||||
- **深度体现**——与不适同在
|
||||
- **新奇**——无聊迫使你寻求新的、更健康的刺激
|
||||
- **不可预测性**——不知道从虚空中会出现什么
|
||||
|
||||
如果你不知道生活中该做什么，也许你应该什么都不做。
|
||||
|
||||
不是每个人都陷入的默认的什么都不做，而是真正的什么都不做。
|
||||
|
||||
### 2. 大脑在被剥夺时会上调多巴胺受体
|
||||
|
||||
享乐适应是你的心理恒温器。
|
||||
|
||||
无论温度多高或多低，它总是试图回到设定点。
|
||||
|
||||
这创造了心理学家所说的「享乐跑步机」。你总是跑向下一个快乐来源，但满足感永远不会持久。每个体验都成为你的新常态，需要更强烈的刺激才能达到相同的情感高潮。
|
||||
|
||||
但当你剥夺自己的快乐时，相反的情况会发生。享乐跑步机逆转。
|
||||
|
||||
慢慢地，然后迅速，简单的快乐再次变得令人愉快。你体验到佛教徒所说的「初心」。
|
||||
|
||||
你在外面散步时注意到天空的细节。你注意到精心烹制的饭菜中迷迭香的暗示。生活变得充满活力，就像它应该的那样。
|
||||
|
||||
### 3. 你不需要动力，你需要清晰度
|
||||
|
||||
> 人类的所有问题都源于人无法安静地独自坐在一个房间里。——Naval Ravikant
|
||||
|
||||
无聊为意义创造创造了空间。也就是说，处理和整合经验。大多数人没有意识到这种消化很重要。
|
||||
|
||||
在信息时代，现代技术创造了「语境崩溃」。我们的大脑只能通过我们的有意识注意力每秒处理大约50比特的信息。
|
||||
|
||||
当你剥夺自己到无聊的程度时，你几乎被迫面对多年来压抑的所有问题。
|
||||
|
||||
你需要坐下来注意你脑海中发生了什么。
|
||||
|
||||
这将是痛苦的，但如果你坐得足够久，你会收到一阵清晰度，将你推向生活的新阶段。
|
||||
|
||||
通过混乱，或对混乱视角的改变，秩序出现了。
|
||||
|
||||
## 四、7天方案：如何重新感受活着
|
||||
|
||||
好的，你明白了。
|
||||
|
||||
创造力是一件不可思议的事情，你可能应该更优先考虑它。
|
||||
|
||||
但是怎么做呢？
|
||||
|
||||
我们看看问题（过度刺激、过度承诺、思维臃肿），并设计一个系统来缓解这些问题。当事情不顺利时，你就这样做，但当你陷入这种狭隘思维状态时，很难首先确定你的问题是什么，甚至更难改变你的行为。这就是为什么像这样的文章会有帮助。它照亮了意识之光（你不能问ChatGPT你没有想到要问的东西）。
|
||||
|
||||
现在，我们不需要一个完整的「多巴胺排毒」，但我们需要承诺。
|
||||
|
||||
正如我所说，这非常简单。
|
||||
|
||||
这会导致人们认为自己高于它而不尝试。我强烈反对这种思维方式。这是你不很有创造力的一个原因。
|
||||
|
||||
### 第1-2天：快速减少输入
|
||||
|
||||
这相当于做间歇性禁食，但是针对思维。
|
||||
|
||||
所有这些都很重要，如果感觉不对也没关系。
|
||||
|
||||
- 对你的工作日施加严格的时间块。如果可以，将本周的工作限制在每天4小时。如果不行，也没关系。设置一个标记结束的闹钟。当它响起时，你就完成了。没有「最后一个任务」。你的工作是在不工作时不去想工作或生产力。你正在练习让某件事感觉未完成而不焦虑的技能。
|
||||
- 切断你的主要输入源。就像晚上橱柜里的垃圾食品一样，选择你最无意识地伸手去拿的那个来源。这可能是通勤时的播客、睡前的滚动或早上的新闻。用什么都不做来替代它。坐在寂静中。倾听一个想法。
|
||||
- 去散步。不是因为它会有什么神奇的效果，而是因为想法是在运动中捕捉到的。不要戴耳机。甚至把手机留在家里。这次散步对你来说可能不会有多大作用，因为这可能是你的第一次，但相信这个过程。
|
||||
|
||||
就是这样。三个简单的改变。
|
||||
|
||||
从心理上讲，移除持续输入允许你大脑的默认模式网络（大脑的「漫游」系统）启动。这是负责随机洞察、自我反思和想象未来的网络。
|
||||
|
||||
当你在消费时，它无法活跃。
|
||||
|
||||
### 第3-4天：消化已经存在的东西
|
||||
|
||||
现在你已经创造了空间，事情将开始浮现。
|
||||
|
||||
未经检验的信念。未经处理的情绪。未经质疑的假设。你放弃的梦想。在生活「变得真实」之前你想成为的那个人。
|
||||
|
||||
这是你放慢脚步并整合你已经经历的事情的机会。如果你总是在消费，你只是飞过生活而从未着陆。
|
||||
|
||||
大多数人避免这一点，因为它不舒服。但没有整合，经验就毫无意义。
|
||||
|
||||
### 第5-7天：重新连接与创造
|
||||
|
||||
现在你的思维已经清理干净，是时候重新连接了。
|
||||
|
||||
- **重新发现你的好奇心**：问自己一些天真的问题。如果钱不是问题，你会做什么？如果你不会失败，你会尝试什么？
|
||||
- **建立创造仪式**：每天留出30分钟专门用于创造。不是工作，而是纯粹的创造——写作、绘画、思考、梦想。
|
||||
- **拥抱不完美**：创造力的敌人是完美主义。允许自己创造糟糕的东西。质量会随之而来。
|
||||
|
||||
## 五、AI时代，创造力是你的终极护城河
|
||||
|
||||
在AI工具泛滥的今天，很多人担心自己的工作会被取代。但我想告诉你一个真相：**AI永远无法取代真正的创造力**。
|
||||
|
||||
是的，AI可以生成内容、分析数据、执行任务。但它无法拥有真正的人类洞察力——那种来自独特生活经历、情感深度和创造性连接的洞察力。
|
||||
|
||||
我最近在测试各种AI Agent时发现一个有趣的现象：最优秀的AI使用者不是那些精通技术的人，而是那些拥有强大创造力和批判性思维的人。他们知道如何向AI提出正确的问题，如何将AI的输出转化为真正有价值的内容。
|
||||
|
||||
**这就是为什么知识管理变得如此重要**。
|
||||
|
||||
当你的大脑不再被琐碎信息填满，当你有系统整理自己的知识和想法，你就能释放出真正的创造力。你可以：
|
||||
|
||||
1. **连接看似无关的点**：将不同领域的知识结合起来，产生突破性想法
|
||||
2. **识别模式**：在混乱的信息中看到别人看不到的结构
|
||||
3. **提出正确问题**：这是AI时代最重要的技能
|
||||
|
||||
## 六、从今天开始，重新定义你的创造力
|
||||
|
||||
创造力不是天赋，而是一种可以培养的状态。
|
||||
|
||||
它不是关于创造无中生有的东西，而是关于注意到未被注意的东西。
|
||||
|
||||
从今天开始，给自己7天时间。
|
||||
|
||||
减少输入，创造空间，重新连接。
|
||||
|
||||
你会发现，那个充满灵感的自己从未离开——只是被太多的噪音淹没了。
|
||||
|
||||
在一个人人都能建造任何东西、思考任何东西、写任何东西的世界里，最具创造力的人将永远领先一步。
|
||||
|
||||
因为他们走的是别人从未考虑过的道路。
|
||||
|
||||
而你，也可以成为这样的人。
|
||||
|
||||
---
|
||||
|
||||
**关于作者：** 本文基于DAN KOE的深度思考编译整理，结合中国读者的实际情况进行了本土化改编。如果你觉得这篇文章有价值，欢迎分享给需要的人。
|
||||
|
||||
**PS：** 如果你对AI时代的创造力提升和知识管理系统感兴趣，可以关注我的公众号，我会分享更多实用方法和工具。记住，在这个AI泛滥的时代，你的创造力是你最宝贵的资产。
|
||||
|
||||
---
|
||||
|
||||
## X/Twitter 文案
|
||||
|
||||
🚨大脑被榨干？创意枯竭？
|
||||
|
||||
这不是情绪问题，是认知过载！
|
||||
|
||||
💡创造力枯竭的3大元凶：
|
||||
1️⃣ 社会条件反射扼杀好奇心
|
||||
2️⃣ 生产力崇拜让你变成机器人
|
||||
3️⃣ 信息过载导致思维臃肿
|
||||
|
||||
🔥7天重启大脑方案：
|
||||
第1-2天：减少输入（像间歇性禁食）
|
||||
第3-4天：消化已有信息
|
||||
第5-7天：重新连接创造力
|
||||
|
||||
在AI时代，创造力是你唯一的护城河。
|
||||
|
||||
停止消费，开始创造！
|
||||
|
||||
#创造力 #认知科学 #个人成长
|
||||
|
||||
---
|
||||
|
||||
## 视频信息
|
||||
|
||||
**标题：** 7天让你的创造力「爆表」！大脑重启终极指南
|
||||
|
||||
**口播脚本：
|
||||
|
||||
[0:00-0:30] 开场
|
||||
（轻快的背景音乐，主持人站在简洁的工作室背景前）
|
||||
主持人：你有没有过这样的时刻？大脑像被榨干了一样，想写东西写不出来，想创意想不出来，感觉自己像个没有灵魂的机器人？
|
||||
|
||||
[0:31-1:30] 问题诊断
|
||||
主持人：这不是情绪问题，这是认知过载！现代人的创造力被三座大山压垮了：
|
||||
1. 社会条件反射——从小就被教育要「正常」，好奇心被扼杀
|
||||
2. 生产力崇拜——每分每秒都要「有用」，没时间无聊
|
||||
3. 信息过载——每天被海量信息轰炸，大脑没时间消化
|
||||
|
||||
[1:31-3:00] 核心原理
|
||||
主持人：真正的创造力需要无聊！不是刷手机的那种假无聊，而是真正的什么都不做。
|
||||
|
||||
科学研究显示：
|
||||
- 无聊时大脑的默认模式网络会激活
|
||||
- 这是产生突破性想法的关键
|
||||
- 过度刺激会关闭这个网络
|
||||
|
||||
[3:01-4:30] 7天实操方案
|
||||
主持人：接下来是干货时间！7天重启大脑：
|
||||
|
||||
第1-2天：减少输入
|
||||
- 每天工作不超过4小时
|
||||
- 切断主要娱乐源（比如睡前刷手机）
|
||||
- 不带耳机散步
|
||||
|
||||
第3-4天：消化信息
|
||||
- 让被压抑的想法浮现
|
||||
- 处理未消化的情绪
|
||||
- 重新审视被放弃的梦想
|
||||
|
||||
第5-7天：重新创造
|
||||
- 建立创造仪式
|
||||
- 拥抱不完美
|
||||
- 重新连接好奇心
|
||||
|
||||
[4:31-5:00] 结尾呼吁
|
||||
主持人：在AI时代，创造力是你唯一的护城河。AI可以生成内容，但无法拥有真正的人类洞察力。
|
||||
|
||||
从今天开始，给自己7天时间，重启你的创造力。你会惊讶地发现，那个充满灵感的自己一直都在。
|
||||
|
||||
点赞收藏，7天后回来告诉我你的变化！
|
||||
|
||||
---
|
||||
|
||||
*封面图关键词：创造力 | 大脑重启 | 认知科学 | 个人成长 | AI时代 | 知识管理 | 思维升级 | 创意枯竭*
|
||||
|
||||
---
|
||||
title: 如何让创造力「爆表」到感觉像在犯罪？7天重启大脑的终极指南
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
---
|
||||
|
||||
# 如何让创造力「爆表」到感觉像在犯罪？7天重启大脑的终极指南
|
||||
|
||||
你是否感觉大脑像被榨干了一样？创意枯竭，灵感消失？这可能是认知过载而非情绪疲劳。本文揭示创造力枯竭的三大元凶，并提供一套7天重启大脑的实用方法，让你找回那个充满灵感的自己。
|
||||
|
||||
# 如何让创造力「爆表」到感觉像在犯罪？7天重启大脑的终极指南
|
||||
|
||||
**作者：** DAN KOE（编译整理）
|
||||
**阅读时间：** 8分钟
|
||||
|
||||
---
|
||||
|
||||
## 一、那个大脑被「榨干」的时刻
|
||||
|
||||
最近几周，我感觉自己的大脑完全被榨干了。
|
||||
|
||||
你知道那种感觉——既在思考一切，又什么都没在想。当你试图思考、头脑风暴或想出一个好主意时，无论怎么努力，脑子里就是一片空白。
|
||||
|
||||
这更像是认知过载，而非情绪疲劳。我可以继续工作，但感觉自己不像个完整的人。
|
||||
|
||||
可能是压力太大。
|
||||
|
||||
可能是AI用太多了（最近我沉迷于各种AI工具）。
|
||||
|
||||
可能是写作习惯被打乱了（因为注意力转移到公司其他问题上，导致更多压力）。
|
||||
|
||||
就在上个月，好点子和写作对我来说还是轻而易举的事。我可以坐下来尽情写作，感觉质量不错，接近原创思考。
|
||||
|
||||
但这种情况持续越久，那种感觉就越强烈。
|
||||
|
||||
为什么我写不出来？我的所有想法都去哪儿了？
|
||||
|
||||
我该如何找回状态？
|
||||
|
||||
这就是我写这篇文章的首要目标——为你和我提供一个指南，帮助我们回到最具创造力的状态。
|
||||
|
||||
我的次要目标是向你展示，即使你不认为自己是个「有创造力的人」，也可以进入一种极其愉悦的意识状态。类似于心流状态，但可能更强大。
|
||||
|
||||
我的第三个目标是给你一个7天方案。如果你严格执行，你会从大脑被榨干的感觉中复活，变得充满活力。
|
||||
|
||||
因为在当今世界，你的创造力是最稀缺的资源。
|
||||
|
||||
任何人都可以建造任何东西，思考任何东西，写任何东西。在商业、写作、艺术和一般生活质量方面，能够选择最具创造性的道路的人将会获胜——那条别人从未考虑过的道路。
|
||||
|
||||
## 二、你没有想法的三大原因
|
||||
|
||||
### 1. 条件反射：好奇心的天敌
|
||||
|
||||
当你想到创造力时，你会想到孩子。
|
||||
|
||||
他们用如此新鲜的眼光看世界。如果一个孩子让ChatGPT建造一个传送装置，以便带朋友去另一个星系，没人会眨眼睛。但如果你这样做，人们会认为你是个不懂「世界如何运作」的白痴。
|
||||
|
||||
孩子们还没有从父母、老师和同龄人那里收到复合的负面反馈。他们还没有内化自己必须以某种方式行事，以适应这个破碎而无聊的社会。
|
||||
|
||||
你必须上学。
|
||||
|
||||
你必须尽力找一份高薪工作。
|
||||
|
||||
你必须赞美这个神，如果你不服从，你就会下地狱。
|
||||
|
||||
到大多数人20岁时，他们和其他人一样——相同的想法、行动和信仰类型。他们正在走分配给他们的生活道路，而不是他们选择创造的道路。
|
||||
|
||||
创造力需要宽松地持有信念，并在不立即拒绝或妖魔化的情况下考虑一个想法。
|
||||
|
||||
### 2. 生产力优先：必输的游戏
|
||||
|
||||
当朝九晚五的工作在工业化时期成为常态时，生产力成为最高价值。每个人都成为只学会放置一块拼图的专家，因为如果他们知道如何解决整个问题，他们就会是企业家而不是员工。
|
||||
|
||||
今天，每个人都觉得自己落后了（说实话，在一个你没有创造的游戏中，你永远也追不上。创造力是唯一的出路）。
|
||||
|
||||
你有一个永远迫在眉睫的最后期限。
|
||||
|
||||
一个紧张的大脑只担心生存，当你的神经系统被截止日期统治时，你看不到新的联系。
|
||||
|
||||
如果你的生活不是围绕优化和效率构建的（换句话说，如果你不是机器人），每个人都认为你毫无用处。但这正是创造力所需要的——无用的漫游。真正的无聊。为正确的想法创造空间，这将带你走得更远，比那些陷入与其他人相同竞赛的「生产力兄弟」更远。
|
||||
|
||||
### 3. 无限输入，零处理时间
|
||||
|
||||
你的新陈代谢只能这么快。
|
||||
|
||||
很明显，如果你吃太多食物，你会开始感觉迟钝，看起来也迟钝。是的，你会变胖。
|
||||
|
||||
但大多数人没有意识到这也适用于思维。
|
||||
|
||||
他们觉得如果一周不听10个播客，就无法「跟上」，尽管事实恰恰相反。他们的思维新陈代谢没有时间消化信息。
|
||||
|
||||
有一个时间用于精心策划的信息，帮助激发更多想法，但如果不严格控制，很快就会变得危险。
|
||||
|
||||
创造力很少是输入问题，但同样，你只能用冰箱里的东西做饭。问题是大多数人的冰箱里装满了冰淇淋和苏打水。
|
||||
|
||||
## 三、你不是无聊，你是过度刺激
|
||||
|
||||
"丹，我一直很无聊，我没有创造力。"
|
||||
|
||||
长期过度刺激和过度咖啡因摄入不是无聊。你被炸得如此彻底，以至于走到了另一端，并将其与无聊联系起来，因为你已经习惯了欣快感，以至于它变得无聊。你简直不能再往前走了，你必须往回走。
|
||||
|
||||
真正的无聊（在你的戒断期之后）会做几件事：
|
||||
|
||||
### 1. 无聊提供了通往新奇的大门
|
||||
|
||||
卡尔·荣格，OG心理学家，强调阴影工作的重要性——面对我们通常避免的不舒服的方面。
|
||||
|
||||
与无聊共处正是这样做的。
|
||||
|
||||
当理性思维停止试图解决一切时，它会激活突破性的见解。
|
||||
|
||||
它揭示了外部条件反射下我们真实的欲望。
|
||||
|
||||
它为3个心流触发器设置了场景，使你更有可能进入一个密集学习和建设的季节：
|
||||
|
||||
- **深度体现**——与不适同在
|
||||
- **新奇**——无聊迫使你寻求新的、更健康的刺激
|
||||
- **不可预测性**——不知道从虚空中会出现什么
|
||||
|
||||
如果你不知道生活中该做什么，也许你应该什么都不做。
|
||||
|
||||
不是每个人都陷入的默认的什么都不做，而是真正的什么都不做。
|
||||
|
||||
### 2. 大脑在被剥夺时会上调多巴胺受体
|
||||
|
||||
享乐适应是你的心理恒温器。
|
||||
|
||||
无论温度多高或多低，它总是试图回到设定点。
|
||||
|
||||
这创造了心理学家所说的「享乐跑步机」。你总是跑向下一个快乐来源，但满足感永远不会持久。每个体验都成为你的新常态，需要更强烈的刺激才能达到相同的情感高潮。
|
||||
|
||||
但当你剥夺自己的快乐时，相反的情况会发生。享乐跑步机逆转。
|
||||
|
||||
慢慢地，然后迅速，简单的快乐再次变得令人愉快。你体验到佛教徒所说的「初心」。
|
||||
|
||||
你在外面散步时注意到天空的细节。你注意到精心烹制的饭菜中迷迭香的暗示。生活变得充满活力，就像它应该的那样。
|
||||
|
||||
### 3. 你不需要动力，你需要清晰度
|
||||
|
||||
> 人类的所有问题都源于人无法安静地独自坐在一个房间里。——Naval Ravikant
|
||||
|
||||
无聊为意义创造创造了空间。也就是说，处理和整合经验。大多数人没有意识到这种消化很重要。
|
||||
|
||||
在信息时代，现代技术创造了「语境崩溃」。我们的大脑只能通过我们的有意识注意力每秒处理大约50比特的信息。
|
||||
|
||||
当你剥夺自己到无聊的程度时，你几乎被迫面对多年来压抑的所有问题。
|
||||
|
||||
你需要坐下来注意你脑海中发生了什么。
|
||||
|
||||
这将是痛苦的，但如果你坐得足够久，你会收到一阵清晰度，将你推向生活的新阶段。
|
||||
|
||||
通过混乱，或对混乱视角的改变，秩序出现了。
|
||||
|
||||
## 四、7天方案：如何重新感受活着
|
||||
|
||||
好的，你明白了。
|
||||
|
||||
创造力是一件不可思议的事情，你可能应该更优先考虑它。
|
||||
|
||||
但是怎么做呢？
|
||||
|
||||
我们看看问题（过度刺激、过度承诺、思维臃肿），并设计一个系统来缓解这些问题。当事情不顺利时，你就这样做，但当你陷入这种狭隘思维状态时，很难首先确定你的问题是什么，甚至更难改变你的行为。这就是为什么像这样的文章会有帮助。它照亮了意识之光（你不能问ChatGPT你没有想到要问的东西）。
|
||||
|
||||
现在，我们不需要一个完整的「多巴胺排毒」，但我们需要承诺。
|
||||
|
||||
正如我所说，这非常简单。
|
||||
|
||||
这会导致人们认为自己高于它而不尝试。我强烈反对这种思维方式。这是你不很有创造力的一个原因。
|
||||
|
||||
### 第1-2天：快速减少输入
|
||||
|
||||
这相当于做间歇性禁食，但是针对思维。
|
||||
|
||||
所有这些都很重要，如果感觉不对也没关系。
|
||||
|
||||
- 对你的工作日施加严格的时间块。如果可以，将本周的工作限制在每天4小时。如果不行，也没关系。设置一个标记结束的闹钟。当它响起时，你就完成了。没有「最后一个任务」。你的工作是在不工作时不去想工作或生产力。你正在练习让某件事感觉未完成而不焦虑的技能。
|
||||
- 切断你的主要输入源。就像晚上橱柜里的垃圾食品一样，选择你最无意识地伸手去拿的那个来源。这可能是通勤时的播客、睡前的滚动或早上的新闻。用什么都不做来替代它。坐在寂静中。倾听一个想法。
|
||||
- 去散步。不是因为它会有什么神奇的效果，而是因为想法是在运动中捕捉到的。不要戴耳机。甚至把手机留在家里。这次散步对你来说可能不会有多大作用，因为这可能是你的第一次，但相信这个过程。
|
||||
|
||||
就是这样。三个简单的改变。
|
||||
|
||||
从心理上讲，移除持续输入允许你大脑的默认模式网络（大脑的「漫游」系统）启动。这是负责随机洞察、自我反思和想象未来的网络。
|
||||
|
||||
当你在消费时，它无法活跃。
|
||||
|
||||
### 第3-4天：消化已经存在的东西
|
||||
|
||||
现在你已经创造了空间，事情将开始浮现。
|
||||
|
||||
未经检验的信念。未经处理的情绪。未经质疑的假设。你放弃的梦想。在生活「变得真实」之前你想成为的那个人。
|
||||
|
||||
这是你放慢脚步并整合你已经经历的事情的机会。如果你总是在消费，你只是飞过生活而从未着陆。
|
||||
|
||||
大多数人避免这一点，因为它不舒服。但没有整合，经验就毫无意义。
|
||||
|
||||
### 第5-7天：重新连接与创造
|
||||
|
||||
现在你的思维已经清理干净，是时候重新连接了。
|
||||
|
||||
- **重新发现你的好奇心**：问自己一些天真的问题。如果钱不是问题，你会做什么？如果你不会失败，你会尝试什么？
|
||||
- **建立创造仪式**：每天留出30分钟专门用于创造。不是工作，而是纯粹的创造——写作、绘画、思考、梦想。
|
||||
- **拥抱不完美**：创造力的敌人是完美主义。允许自己创造糟糕的东西。质量会随之而来。
|
||||
|
||||
## 五、AI时代，创造力是你的终极护城河
|
||||
|
||||
在AI工具泛滥的今天，很多人担心自己的工作会被取代。但我想告诉你一个真相：**AI永远无法取代真正的创造力**。
|
||||
|
||||
是的，AI可以生成内容、分析数据、执行任务。但它无法拥有真正的人类洞察力——那种来自独特生活经历、情感深度和创造性连接的洞察力。
|
||||
|
||||
我最近在测试各种AI Agent时发现一个有趣的现象：最优秀的AI使用者不是那些精通技术的人，而是那些拥有强大创造力和批判性思维的人。他们知道如何向AI提出正确的问题，如何将AI的输出转化为真正有价值的内容。
|
||||
|
||||
**这就是为什么知识管理变得如此重要**。
|
||||
|
||||
当你的大脑不再被琐碎信息填满，当你有系统整理自己的知识和想法，你就能释放出真正的创造力。你可以：
|
||||
|
||||
1. **连接看似无关的点**：将不同领域的知识结合起来，产生突破性想法
|
||||
2. **识别模式**：在混乱的信息中看到别人看不到的结构
|
||||
3. **提出正确问题**：这是AI时代最重要的技能
|
||||
|
||||
## 六、从今天开始，重新定义你的创造力
|
||||
|
||||
创造力不是天赋，而是一种可以培养的状态。
|
||||
|
||||
它不是关于创造无中生有的东西，而是关于注意到未被注意的东西。
|
||||
|
||||
从今天开始，给自己7天时间。
|
||||
|
||||
减少输入，创造空间，重新连接。
|
||||
|
||||
你会发现，那个充满灵感的自己从未离开——只是被太多的噪音淹没了。
|
||||
|
||||
在一个人人都能建造任何东西、思考任何东西、写任何东西的世界里，最具创造力的人将永远领先一步。
|
||||
|
||||
因为他们走的是别人从未考虑过的道路。
|
||||
|
||||
而你，也可以成为这样的人。
|
||||
|
||||
---
|
||||
|
||||
**关于作者：** 本文基于DAN KOE的深度思考编译整理，结合中国读者的实际情况进行了本土化改编。如果你觉得这篇文章有价值，欢迎分享给需要的人。
|
||||
|
||||
**PS：** 如果你对AI时代的创造力提升和知识管理系统感兴趣，可以关注我的公众号，我会分享更多实用方法和工具。记住，在这个AI泛滥的时代，你的创造力是你最宝贵的资产。
|
||||
|
||||
---
|
||||
|
||||
## X/Twitter 文案
|
||||
|
||||
🚨大脑被榨干？创意枯竭？
|
||||
|
||||
这不是情绪问题，是认知过载！
|
||||
|
||||
💡创造力枯竭的3大元凶：
|
||||
1️⃣ 社会条件反射扼杀好奇心
|
||||
2️⃣ 生产力崇拜让你变成机器人
|
||||
3️⃣ 信息过载导致思维臃肿
|
||||
|
||||
🔥7天重启大脑方案：
|
||||
第1-2天：减少输入（像间歇性禁食）
|
||||
第3-4天：消化已有信息
|
||||
第5-7天：重新连接创造力
|
||||
|
||||
在AI时代，创造力是你唯一的护城河。
|
||||
|
||||
停止消费，开始创造！
|
||||
|
||||
#创造力 #认知科学 #个人成长
|
||||
|
||||
---
|
||||
|
||||
## 视频信息
|
||||
|
||||
**标题：** 7天让你的创造力「爆表」！大脑重启终极指南
|
||||
|
||||
**口播脚本：
|
||||
|
||||
[0:00-0:30] 开场
|
||||
（轻快的背景音乐，主持人站在简洁的工作室背景前）
|
||||
主持人：你有没有过这样的时刻？大脑像被榨干了一样，想写东西写不出来，想创意想不出来，感觉自己像个没有灵魂的机器人？
|
||||
|
||||
[0:31-1:30] 问题诊断
|
||||
主持人：这不是情绪问题，这是认知过载！现代人的创造力被三座大山压垮了：
|
||||
1. 社会条件反射——从小就被教育要「正常」，好奇心被扼杀
|
||||
2. 生产力崇拜——每分每秒都要「有用」，没时间无聊
|
||||
3. 信息过载——每天被海量信息轰炸，大脑没时间消化
|
||||
|
||||
[1:31-3:00] 核心原理
|
||||
主持人：真正的创造力需要无聊！不是刷手机的那种假无聊，而是真正的什么都不做。
|
||||
|
||||
科学研究显示：
|
||||
- 无聊时大脑的默认模式网络会激活
|
||||
- 这是产生突破性想法的关键
|
||||
- 过度刺激会关闭这个网络
|
||||
|
||||
[3:01-4:30] 7天实操方案
|
||||
主持人：接下来是干货时间！7天重启大脑：
|
||||
|
||||
第1-2天：减少输入
|
||||
- 每天工作不超过4小时
|
||||
- 切断主要娱乐源（比如睡前刷手机）
|
||||
- 不带耳机散步
|
||||
|
||||
第3-4天：消化信息
|
||||
- 让被压抑的想法浮现
|
||||
- 处理未消化的情绪
|
||||
- 重新审视被放弃的梦想
|
||||
|
||||
第5-7天：重新创造
|
||||
- 建立创造仪式
|
||||
- 拥抱不完美
|
||||
- 重新连接好奇心
|
||||
|
||||
[4:31-5:00] 结尾呼吁
|
||||
主持人：在AI时代，创造力是你唯一的护城河。AI可以生成内容，但无法拥有真正的人类洞察力。
|
||||
|
||||
从今天开始，给自己7天时间，重启你的创造力。你会惊讶地发现，那个充满灵感的自己一直都在。
|
||||
|
||||
点赞收藏，7天后回来告诉我你的变化！
|
||||
|
||||
---
|
||||
|
||||
*封面图关键词：创造力 | 大脑重启 | 认知科学 | 个人成长 | AI时代 | 知识管理 | 思维升级 | 创意枯竭*
|
||||
|
||||
*原文路径：/Users/weishen/Workspace/nexus/openclaw/content-queue/How-to-become-so-creative-it-feels-illegal-Dan-Koe.md*/
|
||||
@@ -1,133 +1,133 @@
|
||||
---
|
||||
title: Mac Mini 配置 SSH 免密登录到 NAS
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: [mac-mini, openclaw, ssh]
|
||||
---
|
||||
|
||||
# Mac Mini 配置 SSH 免密登录到 NAS
|
||||
|
||||
#openclaw #mac-mini #ssh
|
||||
## 概述
|
||||
|
||||
本文档记录 Mac Mini (192.168.3.189) 配置 SSH 免密登录到 NAS (192.168.3.17) 的详细步骤。
|
||||
|
||||
## 前提条件
|
||||
|
||||
- Mac Mini 已安装 SSH 客户端（内置）
|
||||
- NAS 已开启 SSH 服务
|
||||
- 拥有 NAS 用户名和密码
|
||||
|
||||
## SSH 密钥配置
|
||||
|
||||
### 1. 生成 SSH 密钥（如不存在）
|
||||
|
||||
```bash
|
||||
ssh-keygen -t ed25519 -N "" -f ~/.ssh/id_ed25519
|
||||
```
|
||||
|
||||
### 2. 传输公钥到 NAS
|
||||
|
||||
```bash
|
||||
# 方法1：使用 sshpass（需要安装）
|
||||
sshpass -p 'NAS密码' ssh -o StrictHostKeyChecking=no shenwei@192.168.3.17 'cat >> ~/.ssh/authorized_keys'
|
||||
|
||||
# 方法2：手动复制
|
||||
# 1. 查看公钥
|
||||
cat ~/.ssh/id_ed25519.pub
|
||||
# 2. 登录 NAS
|
||||
ssh shenwei@192.168.3.17
|
||||
# 3. 追加公钥到 authorized_keys
|
||||
echo '公钥内容' >> ~/.ssh/authorized_keys
|
||||
```
|
||||
|
||||
## ~/.ssh/config 配置
|
||||
|
||||
### 完整配置示例
|
||||
|
||||
```bash
|
||||
# NAS
|
||||
Host nas
|
||||
HostName 192.168.3.17
|
||||
User shenwei
|
||||
IdentityFile ~/.ssh/id_ed25519
|
||||
ProxyCommand none
|
||||
|
||||
# Ubuntu1
|
||||
Host ubuntu1
|
||||
HostName 192.168.3.47
|
||||
User shenwei
|
||||
IdentityFile ~/.ssh/id_ed25519
|
||||
ProxyCommand none
|
||||
|
||||
# Ubuntu2
|
||||
Host ubuntu2
|
||||
HostName 192.168.3.45
|
||||
User shenwei
|
||||
IdentityFile ~/.ssh/id_ed25519
|
||||
ProxyCommand none
|
||||
|
||||
# Mac Mini (本地)
|
||||
Host macmini
|
||||
HostName 192.168.3.189
|
||||
User weishen
|
||||
IdentityFile ~/.ssh/id_ed25519
|
||||
ProxyCommand none
|
||||
|
||||
# VPS1
|
||||
Host vps1
|
||||
HostName 192.227.222.142
|
||||
User root
|
||||
IdentityFile ~/.ssh/id_ed25519
|
||||
ProxyCommand none
|
||||
|
||||
# VPS2
|
||||
Host vps2
|
||||
HostName 104.194.92.188
|
||||
User root
|
||||
IdentityFile ~/.ssh/id_ed25519
|
||||
ProxyCommand none
|
||||
```
|
||||
|
||||
## 测试免密登录
|
||||
|
||||
```bash
|
||||
# 测试 NAS 连接
|
||||
ssh nas "echo success"
|
||||
|
||||
# 测试所有服务器
|
||||
for server in macmini ubuntu1 ubuntu2 nas; do
|
||||
ssh $server "echo $server OK"
|
||||
done
|
||||
```
|
||||
|
||||
## 已配置的服务器
|
||||
|
||||
| 主机 | IP | 用户 | 状态 |
|
||||
|------|-----|------|------|
|
||||
| nas | 192.168.3.17 | shenwei | ✅ 已配置 |
|
||||
| ubuntu1 | 192.168.3.47 | shenwei | ✅ 已配置 |
|
||||
| ubuntu2 | 192.168.3.45 | shenwei | ✅ 已配置 |
|
||||
| macmini | 192.168.3.189 | weishen | ✅ 已配置 |
|
||||
| vps1 | 192.227.222.142 | root | ✅ 已配置 |
|
||||
| vps2 | 104.194.92.188 | root | ✅ 已配置 |
|
||||
|
||||
## 故障排查
|
||||
|
||||
### 问题：Could not resolve hostname nas
|
||||
|
||||
**解决**：确保 ~/.ssh/config 中已添加 nas 别名配置
|
||||
|
||||
### 问题：Permission denied
|
||||
|
||||
**解决**：
|
||||
1. 检查公钥是否已添加到目标服务器的 ~/.ssh/authorized_keys
|
||||
2. 检查 ~/.ssh 目录权限应为 700
|
||||
3. 检查 ~/.ssh/authorized_keys 权限应为 600
|
||||
|
||||
## 相关文档
|
||||
|
||||
- Ubuntu2 SSH 配置: [[Ubuntu2 SSH 配置]]
|
||||
---
|
||||
title: Mac Mini 配置 SSH 免密登录到 NAS
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: [mac-mini, openclaw, ssh]
|
||||
---
|
||||
|
||||
# Mac Mini 配置 SSH 免密登录到 NAS
|
||||
|
||||
#openclaw #mac-mini #ssh
|
||||
## 概述
|
||||
|
||||
本文档记录 Mac Mini (192.168.3.189) 配置 SSH 免密登录到 NAS (192.168.3.17) 的详细步骤。
|
||||
|
||||
## 前提条件
|
||||
|
||||
- Mac Mini 已安装 SSH 客户端（内置）
|
||||
- NAS 已开启 SSH 服务
|
||||
- 拥有 NAS 用户名和密码
|
||||
|
||||
## SSH 密钥配置
|
||||
|
||||
### 1. 生成 SSH 密钥（如不存在）
|
||||
|
||||
```bash
|
||||
ssh-keygen -t ed25519 -N "" -f ~/.ssh/id_ed25519
|
||||
```
|
||||
|
||||
### 2. 传输公钥到 NAS
|
||||
|
||||
```bash
|
||||
# 方法1：使用 sshpass（需要安装）
|
||||
sshpass -p 'NAS密码' ssh -o StrictHostKeyChecking=no shenwei@192.168.3.17 'cat >> ~/.ssh/authorized_keys'
|
||||
|
||||
# 方法2：手动复制
|
||||
# 1. 查看公钥
|
||||
cat ~/.ssh/id_ed25519.pub
|
||||
# 2. 登录 NAS
|
||||
ssh shenwei@192.168.3.17
|
||||
# 3. 追加公钥到 authorized_keys
|
||||
echo '公钥内容' >> ~/.ssh/authorized_keys
|
||||
```
|
||||
|
||||
## ~/.ssh/config 配置
|
||||
|
||||
### 完整配置示例
|
||||
|
||||
```bash
|
||||
# NAS
|
||||
Host nas
|
||||
HostName 192.168.3.17
|
||||
User shenwei
|
||||
IdentityFile ~/.ssh/id_ed25519
|
||||
ProxyCommand none
|
||||
|
||||
# Ubuntu1
|
||||
Host ubuntu1
|
||||
HostName 192.168.3.47
|
||||
User shenwei
|
||||
IdentityFile ~/.ssh/id_ed25519
|
||||
ProxyCommand none
|
||||
|
||||
# Ubuntu2
|
||||
Host ubuntu2
|
||||
HostName 192.168.3.45
|
||||
User shenwei
|
||||
IdentityFile ~/.ssh/id_ed25519
|
||||
ProxyCommand none
|
||||
|
||||
# Mac Mini (本地)
|
||||
Host macmini
|
||||
HostName 192.168.3.189
|
||||
User weishen
|
||||
IdentityFile ~/.ssh/id_ed25519
|
||||
ProxyCommand none
|
||||
|
||||
# VPS1
|
||||
Host vps1
|
||||
HostName 192.227.222.142
|
||||
User root
|
||||
IdentityFile ~/.ssh/id_ed25519
|
||||
ProxyCommand none
|
||||
|
||||
# VPS2
|
||||
Host vps2
|
||||
HostName 104.194.92.188
|
||||
User root
|
||||
IdentityFile ~/.ssh/id_ed25519
|
||||
ProxyCommand none
|
||||
```
|
||||
|
||||
## 测试免密登录
|
||||
|
||||
```bash
|
||||
# 测试 NAS 连接
|
||||
ssh nas "echo success"
|
||||
|
||||
# 测试所有服务器
|
||||
for server in macmini ubuntu1 ubuntu2 nas; do
|
||||
ssh $server "echo $server OK"
|
||||
done
|
||||
```
|
||||
|
||||
## 已配置的服务器
|
||||
|
||||
| 主机 | IP | 用户 | 状态 |
|
||||
|------|-----|------|------|
|
||||
| nas | 192.168.3.17 | shenwei | ✅ 已配置 |
|
||||
| ubuntu1 | 192.168.3.47 | shenwei | ✅ 已配置 |
|
||||
| ubuntu2 | 192.168.3.45 | shenwei | ✅ 已配置 |
|
||||
| macmini | 192.168.3.189 | weishen | ✅ 已配置 |
|
||||
| vps1 | 192.227.222.142 | root | ✅ 已配置 |
|
||||
| vps2 | 104.194.92.188 | root | ✅ 已配置 |
|
||||
|
||||
## 故障排查
|
||||
|
||||
### 问题：Could not resolve hostname nas
|
||||
|
||||
**解决**：确保 ~/.ssh/config 中已添加 nas 别名配置
|
||||
|
||||
### 问题：Permission denied
|
||||
|
||||
**解决**：
|
||||
1. 检查公钥是否已添加到目标服务器的 ~/.ssh/authorized_keys
|
||||
2. 检查 ~/.ssh 目录权限应为 700
|
||||
3. 检查 ~/.ssh/authorized_keys 权限应为 600
|
||||
|
||||
## 相关文档
|
||||
|
||||
- Ubuntu2 SSH 配置: [[Ubuntu2 SSH 配置]]
|
||||
|
||||
@@ -1,106 +1,106 @@
|
||||
---
|
||||
title: OpenClaw Eligible Skills
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: [openclaw, skills]
|
||||
---
|
||||
|
||||
# OpenClaw Eligible Skills
|
||||
#openclaw #skills
|
||||
**Generated**: 2026-03-25
|
||||
**Command**: `openclaw skills list --eligible`
|
||||
|
||||
---
|
||||
|
||||
## Summary
|
||||
|
||||
- **Total Skills**: 64/64 ready
|
||||
- **Doctor Warnings**: 4 warnings about Telegram group settings
|
||||
|
||||
---
|
||||
|
||||
## Skills List
|
||||
|
||||
| Status | Skill | Description | Source |
|
||||
| ------- | ---------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------- |
|
||||
| ✓ ready | 📦 1password | Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op. | agents-skills-personal |
|
||||
| ✓ ready | 📦 apple-notes | Manage Apple Notes via the `memo` CLI on macOS (create, view, edit, delete, search, move, and export notes). Use when a user asks Clawdbot to add a note, list notes, search notes, or manage note folders. | openclaw-managed |
|
||||
| ✓ ready | 📦 apple-reminders | Manage Apple Reminders via the `remindctl` CLI on macOS (list, add, edit, complete, delete). Supports lists, date filters, and JSON/plain output. | openclaw-managed |
|
||||
| ✓ ready | 📦 clawhub | Use the ClawHub CLI to search, install, update, and publish agent skills from clawhub.com. Use when you need to fetch new skills on the fly, sync installed skills to latest or a specific version, or publish new/updated skill folders with the npm-installed clawhub CLI. | openclaw-bundled |
|
||||
| ✓ ready | 🧩 coding-agent | Delegate coding tasks to Codex, Claude Code, or Pi agents via background process. Use when: (1) building/creating new features or apps, (2) reviewing PRs (spawn in temp dir), (3) refactoring large codebases, (4) iterative coding that needs file exploration. NOT for: simple one-liner fixes (just edit), reading code (use read tool), thread-bound ACP harness requests in chat (for example spawn/run Codex or Claude Code in a Discord thread; use sessions_spawn with runtime:"acp"), or any work in ~/clawd workspace (never spawn agents here). Claude Code: use --print --permission-mode bypassPermissions (no PTY). Codex/Pi/OpenCode: pty:true required. | openclaw-bundled |
|
||||
| ✓ ready | 🎮 gog | Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs. | agents-skills-personal |
|
||||
| ✓ ready | 📦 healthcheck | Host security hardening and risk-tolerance configuration for OpenClaw deployments. Use when a user asks for security audits, firewall/SSH/update hardening, risk posture, exposure review, OpenClaw cron scheduling for periodic checks, or version status checks on a machine running OpenClaw (laptop, workstation, Pi, VPS). | openclaw-bundled |
|
||||
| ✓ ready | 📦 node-connect | Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale, or plugins.entries.device-pair.config.publicUrl. | openclaw-bundled |
|
||||
| ✓ ready | 💎 obsidian | Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli. | openclaw-bundled |
|
||||
| ✓ ready | 📦 skill-creator | Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations. | agents-skills-personal |
|
||||
| ✓ ready | 💬 slack | Use when you need to control Slack from OpenClaw via the slack tool, including reacting to messages or pinning/unpinning items in Slack channels or DMs. | openclaw-bundled |
|
||||
| ✓ ready | 📦 summarize | Summarize URLs or files with the summarize CLI (web, PDFs, images, audio, YouTube). | openclaw-managed |
|
||||
| ✓ ready | 📦 tmux | Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output. | agents-skills-personal |
|
||||
| ✓ ready | 📦 video-frames | Extract frames or short clips from videos using ffmpeg. | agents-skills-personal |
|
||||
| ✓ ready | ☔ weather | Get current weather and forecasts via wttr.in or Open-Meteo. Use when: user asks about weather, temperature, or forecasts for any location. NOT for: historical weather data, severe weather alerts, or detailed meteorological analysis. No API key needed. | openclaw-bundled |
|
||||
| ✓ ready | 📦 accli | This skill should be used when interacting with Apple Calendar on macOS. Use it for listing calendars, viewing events, creating/updating/deleting calendar events, and checking availability/free-busy times. Triggers on requests like "check my calendar", "schedule a meeting", "what's on my schedule", "am I free tomorrow", or any calendar-related operations. | openclaw-managed |
|
||||
| ✓ ready | 📦 agent-browser | Headless browser automation CLI optimized for AI agents with accessibility tree snapshots and ref-based element selection | openclaw-managed |
|
||||
| ✓ ready | 📦 agentmail | API-first email platform designed for AI agents. Create and manage dedicated email inboxes, send and receive emails programmatically, and handle email-based workflows with webhooks and real-time events. Use when you need to set up agent email identity, send emails from agents, handle incoming email workflows, or replace traditional email providers like Gmail with agent-friendly infrastructure. | openclaw-managed |
|
||||
| ✓ ready | 📦 Docker | Docker containers, images, Compose stacks, networking, volumes, debugging, production hardening, and the commands that keep real environments stable. Use when (1) the task touches Docker, Dockerfiles, images, containers, or Compose; (2) build reliability, runtime behavior, logs, ports, volumes, or security matter; (3) the agent needs Docker guidance and should apply it by default. | openclaw-managed |
|
||||
| ✓ ready | ⚙️ n8n | Manage n8n workflows and automations via API. Use when working with n8n workflows, executions, or automation tasks - listing workflows, activating/deactivating, checking execution status, manually triggering workflows, or debugging automation issues. | openclaw-managed |
|
||||
| ✓ ready | 📦 ontology | Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linking related objects, enforcing constraints, planning multi-step actions as graph transformations, or when skills need to share state. Trigger on "remember", "what do I know about", "link X to Y", "show dependencies", entity CRUD, or cross-skill data access. | agents-skills-personal |
|
||||
| ✓ ready | 📦 tavily-search | Web search via Tavily API (alternative to Brave). Use when the user asks to search the web / look up sources / find links and Brave web_search is unavailable or undesired. Returns a small set of relevant results (title, url, snippet) and can optionally include short answer summaries. | openclaw-managed |
|
||||
| ✓ ready | 📦 opencode-controller | Control and operate Opencode via slash commands. Use this skill to manage sessions, select models, switch agents (plan/build), and coordinate coding through Opencode. | agents-skills-personal |
|
||||
| ✓ ready | 🧱 opencode-omo | Turn coding requests into completed work. Plan with Prometheus, execute with Atlas, and iterate with Sisyphus in OpenCode. | openclaw-workspace |
|
||||
| ✓ ready | 📦 Powerpoint / PPTX | Create, inspect, and edit Microsoft PowerPoint presentations and PPTX decks with reliable layouts, templates, placeholders, notes, charts, and visual QA. Use when (1) the task is about PowerPoint or `.pptx`; (2) layouts, placeholders, notes, charts, comments, or template fidelity matter; (3) the deck must render cleanly after edits. | openclaw-managed |
|
||||
| ✓ ready | 📦 proactive-agent-lite | Transform AI agents from task-followers into proactive partners with memory architecture, reverse prompting, and self-healing patterns. Lightweight version focused on core proactive capabilities. | openclaw-workspace |
|
||||
| ✓ ready | 📦 self-improvement | Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Claude ('No, that's wrong...', 'Actually...'), (3) User requests a capability that doesn't exist, (4) An external API or tool fails, (5) Claude realizes its knowledge is outdated or incorrect, (6) A better approach is discovered for a recurring task. Also review learnings before major tasks. | openclaw-managed |
|
||||
| ✓ ready | 📦 task-summary | 任务执行总结技能。用于在完成任务后生成结构化的任务总结，记录任务目标、执行步骤、结果和经验教训，以便后续追溯和改进。 | openclaw-workspace |
|
||||
| ✓ ready | 📦 self-reflection | Periodic self-reflection on recent sessions. Analyzes what went well, what went wrong, and writes concise, actionable insights to the appropriate workspace files. Designed to run as a cron job. | agents-skills-personal |
|
||||
| ✓ ready | 📦 architecture-designer | Use when designing new system architecture, reviewing existing designs, or making architectural decisions. Invoke for system design, architecture review, design patterns, ADRs, scalability planning. | agents-skills-personal |
|
||||
| ✓ ready | 📦 automation-workflows | Design and implement automation workflows to save time and scale operations as a solopreneur. Use when identifying repetitive tasks to automate, building workflows across tools, setting up triggers and actions, or optimizing existing automations. Covers automation opportunity identification, workflow design, tool selection (Zapier, Make, n8n), testing, and maintenance. Trigger on "automate", "automation", "workflow automation", "save time", "reduce manual work", "automate my business", "no-code automation". | agents-skills-personal |
|
||||
| ✓ ready | 📦 backtest-expert | Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development. | agents-skills-personal |
|
||||
| ✓ ready | 📦 blog-writer | This skill should be used when writing blog posts, articles, or long-form content in the writer's distinctive writing style. It produces authentic, opinionated content that matches the writer's voice—direct, conversational, and grounded in personal experience. The skill handles the complete workflow from research review through Notion publication. Use this skill for drafting blog posts, thought leadership pieces, or any writing meant to reflect the writer's perspective on AI, productivity, sales, marketing, or technology topics. | agents-skills-personal |
|
||||
| ✓ ready | 📦 brainstorming | You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation. | agents-skills-personal |
|
||||
| ✓ ready | 📦 clawdefender | Security scanner and input sanitizer for AI agents. Detects prompt injection, command injection, SSRF, credential exfiltration, and path traversal attacks. Use when (1) installing new skills from ClawHub, (2) processing external input like emails, calendar events, Trello cards, or API responses, (3) validating URLs before fetching, (4) running security audits on your workspace. Protects agents from malicious content in untrusted data sources. | agents-skills-personal |
|
||||
| ✓ ready | 📦 Code | Coding workflow with planning, implementation, verification, and testing for clean software development. | agents-skills-personal |
|
||||
| ✓ ready | 📦 content-strategy | Build and execute a content marketing strategy for a solopreneur business. Use when planning what content to create, deciding on content formats and channels, building a content calendar, measuring content performance, or systematizing content production. Covers audience research for content, content pillars, distribution strategy, repurposing workflows, and metrics. Trigger on "content strategy", "content marketing", "what content should I create", "content plan", "content calendar", "content ideas", "content distribution", "grow through content". | agents-skills-personal |
|
||||
| ✓ ready | 📦 copywriting | Write persuasive copy for landing pages, emails, ads, sales pages, and marketing materials. Use when you need to write headlines, CTAs, product descriptions, ad copy, email sequences, or any text meant to drive action. Covers copywriting formulas (AIDA, PAS, FAB), headline writing, emotional triggers, objection handling in copy, and A/B testing. Trigger on "write copy", "copywriting", "landing page copy", "headline", "write a sales page", "ad copy", "email copy", "persuasive writing", "how to write [marketing text]". | agents-skills-personal |
|
||||
| ✓ ready | 📦 executing-plans | Use when you have a written implementation plan to execute in a separate session with review checkpoints | agents-skills-personal |
|
||||
| ✓ ready | 📦 feishu-chat-history | Fetch and summarize Feishu group chat history. Use when the user asks to read, review, or summarize messages from a Feishu group chat. Triggers: "看群聊记录", "群里聊了啥", "帮我看看这个群", "群消息历史", "chat history", "what did the group discuss". NOT for: sending messages (use message tool), reading documents (use feishu-doc skill), or wiki operations (use feishu-wiki skill). | agents-skills-personal |
|
||||
| ✓ ready | 📦 feishu-cron-reminder | Create cron jobs that reliably deliver reminders to Feishu (飞书) chats. Use when the user asks to set up scheduled reminders, periodic notifications, or any recurring task that should send messages to a Feishu conversation. Triggers: '飞书定时提醒', '定时任务发飞书', 'cron reminder to feishu', '每小时提醒', 'scheduled feishu message'. | agents-skills-personal |
|
||||
| ✓ ready | 📦 feishu-doc | Fetch content from Feishu (Lark) Wiki, Docs, Sheets, and Bitable. Automatically resolves Wiki URLs to real entities and converts content to Markdown. | agents-skills-personal |
|
||||
| ✓ ready | 📦 feishu-perm | Feishu permission management for documents and files. Activate when user mentions sharing, permissions, collaborators. | agents-skills-personal |
|
||||
| ✓ ready | 📦 feishu-screenshot | Capture macOS screenshots and send to Feishu. Use when the user asks to take a screenshot and share it via Feishu. Triggers: "截个屏发飞书", "截屏", "screenshot", "take a screenshot and send". NOT for: sending existing files (use feishu-send-file skill), or sending text messages (use message tool). | agents-skills-personal |
|
||||
| ✓ ready | 📦 feishu-send-file | Send files to a Feishu group or user via REST API. Use when the user explicitly asks to send a file, attachment, or document to a Feishu chat/group. Triggers: "发文件到飞书", "把这个文件发到群里", "send file to feishu", "发个附件". NOT for: sending text messages (use message tool), sending images/screenshots (use feishu-screenshot skill), or reading documents (use feishu-doc skill). | agents-skills-personal |
|
||||
| ✓ ready | 📦 FFmpeg Video Editor | Generate FFmpeg commands from natural language video editing requests - cut, trim, convert, compress, change aspect ratio, extract audio, and more. | agents-skills-personal |
|
||||
| ✓ ready | 📦 find-skills | Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill. | agents-skills-personal |
|
||||
| ✓ ready | 📦 frontend-design | Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when building web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics. | agents-skills-personal |
|
||||
| ✓ ready | 📦 git-essentials | Essential Git commands and workflows for version control, branching, and collaboration. | agents-skills-personal |
|
||||
| ✓ ready | 📦 interview-designer | Analyze resumes and design interview strategies using evidence-based methodology. Transforms interview prep from "read resume → ask questions" into "define standard → forensic evidence → future simulation". Combines Geoff Smart's Topgrading, Lou Adler's performance-based hiring, and Daniel Kahneman's bias control. Use when preparing for interviews, creating structured interview guides, or designing questions to validate candidate competencies. | agents-skills-personal |
|
||||
| ✓ ready | 📦 Market Research | Size markets, analyze competitors, and validate opportunities with practical frameworks and free data sources. | agents-skills-personal |
|
||||
| ✓ ready | 📦 Memory | Infinite organized memory that complements your agent's built-in memory with unlimited categorized storage. | agents-skills-personal |
|
||||
| ✓ ready | 📦 obsidian-ontology-sync | Bidirectional sync between Obsidian PKM (human-friendly notes) and structured ontology (machine-queryable graph). Automatically extracts entities and relationships from markdown, maintains ontology graph, and provides feedback to improve note structure. Run sync every few hours via cron. | agents-skills-personal |
|
||||
| ✓ ready | 📦 research-paper-writer | Creates formal academic research papers following IEEE/ACM formatting standards with proper structure, citations, and scholarly writing style. Use when the user asks to write a research paper, academic paper, or conference paper on any topic. | agents-skills-personal |
|
||||
| ✓ ready | 📦 security-auditor | Use when reviewing code for security vulnerabilities, implementing authentication flows, auditing OWASP Top 10, configuring CORS/CSP headers, handling secrets, input validation, SQL injection prevention, XSS protection, or any security-related code review. | agents-skills-personal |
|
||||
| ✓ ready | 📦 SEO (Site Audit + Content Writer + Competitor Analysis) | SEO specialist agent with site audits, content writing, keyword research, technical fixes, link building, and ranking strategies. | agents-skills-personal |
|
||||
| ✓ ready | 📦 seo-content-writer | Use when the user asks to "write SEO content", "create a blog post", "write an article", "content writing", "draft optimized content", "write me an article", "create a blog post about", "help me write SEO content", or "draft content for". Creates high-quality, SEO-optimized content that ranks in search engines. Applies on-page SEO best practices, keyword optimization, and content structure for maximum visibility and engagement. | agents-skills-personal |
|
||||
| ✓ ready | 📦 skill-vetter | Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns. | agents-skills-personal |
|
||||
| ✓ ready | 📦 social-content | When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' or 'viral content.' This skill covers content creation, repurposing, and platform-specific strategies. | agents-skills-personal |
|
||||
| ✓ ready | 📦 Social Media Scheduler | Plan, draft, and organize social media content across platforms. Create content calendars, write platform-optimized posts, and maintain consistent posting schedules. | agents-skills-personal |
|
||||
| ✓ ready | 📦 supabase-postgres-best-practices | Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations. | agents-skills-personal |
|
||||
| ✓ ready | 📦 ui-ux-pro-max | UI/UX design intelligence and implementation guidance for building polished interfaces. Use when the user asks for UI design, UX flows, information architecture, visual style direction, design systems/tokens, component specs, copy/microcopy, accessibility, or to generate/critique/refine frontend UI (HTML/CSS/JS, React, Next.js, Vue, Svelte, Tailwind). Includes workflows for (1) generating new UI layouts and styling, (2) improving existing UI/UX, (3) producing design-system tokens and component guidelines, and (4) turning UX recommendations into concrete code changes. | agents-skills-personal |
|
||||
| ✓ ready | 📦 writing-plans | Use when you have a spec or requirements for a multi-step task, before touching code | agents-skills-personal |
|
||||
| ✓ ready | 📦 Playwright (Automation + MCP + Scraper) | Browser automation via Playwright MCP. Navigate websites, click elements, fill forms, take screenshots, extract data, and debug real browser workflows. Use when (1) you need a real browser, not static fetch; (2) the task involves Playwright MCP, browser tools, Playwright tests, scripts, or JS-rendered pages; (3) the user wants navigation, forms, screenshots, PDFs, downloads, or browser-driven extraction turned into a reliable outcome. | openclaw-workspace |
|
||||
|
||||
---
|
||||
|
||||
## Doctor Warnings
|
||||
|
||||
> ⚠️ **Warning 1**: channels.telegram.accounts.bot1.groupPolicy is "allowlist" but groupAllowFrom (and allowFrom) is empty — all group messages will be silently dropped. Add sender IDs to channels.telegram.accounts.bot1.groupAllowFrom or channels.telegram.accounts.bot1.allowFrom, or set groupPolicy to "open".
|
||||
|
||||
> ⚠️ **Warning 2**: channels.telegram.accounts.bot2.groupPolicy is "allowlist" but groupAllowFrom (and allowFrom) is empty — all group messages will be silently dropped. Add sender IDs to channels.telegram.accounts.bot2.groupAllowFrom or channels.telegram.accounts.bot2.allowFrom, or set groupPolicy to "open".
|
||||
|
||||
> ⚠️ **Warning 3**: channels.telegram.accounts.xingshu.groupPolicy is "allowlist" but groupAllowFrom (and allowFrom) is empty — all group messages will be silently dropped. Add sender IDs to channels.telegram.accounts.xingshu.groupAllowFrom or channels.telegram.accounts.xingshu.allowFrom, or set groupPolicy to "open".
|
||||
|
||||
> ⚠️ **Warning 4**: channels.telegram.accounts.default.groupPolicy is "allowlist" but groupAllowFrom (and allowFrom) is empty — all group messages will be silently dropped. Add sender IDs to channels.telegram.accounts.default.groupAllowFrom or channels.telegram.accounts.default.allowFrom, or set groupPolicy to "open".
|
||||
|
||||
**Tip**: Run `openclaw doctor --fix` to apply these changes.
|
||||
---
|
||||
title: OpenClaw Eligible Skills
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: [openclaw, skills]
|
||||
---
|
||||
|
||||
# OpenClaw Eligible Skills
|
||||
#openclaw #skills
|
||||
**Generated**: 2026-03-25
|
||||
**Command**: `openclaw skills list --eligible`
|
||||
|
||||
---
|
||||
|
||||
## Summary
|
||||
|
||||
- **Total Skills**: 64/64 ready
|
||||
- **Doctor Warnings**: 4 warnings about Telegram group settings
|
||||
|
||||
---
|
||||
|
||||
## Skills List
|
||||
|
||||
| Status | Skill | Description | Source |
|
||||
| ------- | ---------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------- |
|
||||
| ✓ ready | 📦 1password | Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op. | agents-skills-personal |
|
||||
| ✓ ready | 📦 apple-notes | Manage Apple Notes via the `memo` CLI on macOS (create, view, edit, delete, search, move, and export notes). Use when a user asks Clawdbot to add a note, list notes, search notes, or manage note folders. | openclaw-managed |
|
||||
| ✓ ready | 📦 apple-reminders | Manage Apple Reminders via the `remindctl` CLI on macOS (list, add, edit, complete, delete). Supports lists, date filters, and JSON/plain output. | openclaw-managed |
|
||||
| ✓ ready | 📦 clawhub | Use the ClawHub CLI to search, install, update, and publish agent skills from clawhub.com. Use when you need to fetch new skills on the fly, sync installed skills to latest or a specific version, or publish new/updated skill folders with the npm-installed clawhub CLI. | openclaw-bundled |
|
||||
| ✓ ready | 🧩 coding-agent | Delegate coding tasks to Codex, Claude Code, or Pi agents via background process. Use when: (1) building/creating new features or apps, (2) reviewing PRs (spawn in temp dir), (3) refactoring large codebases, (4) iterative coding that needs file exploration. NOT for: simple one-liner fixes (just edit), reading code (use read tool), thread-bound ACP harness requests in chat (for example spawn/run Codex or Claude Code in a Discord thread; use sessions_spawn with runtime:"acp"), or any work in ~/clawd workspace (never spawn agents here). Claude Code: use --print --permission-mode bypassPermissions (no PTY). Codex/Pi/OpenCode: pty:true required. | openclaw-bundled |
|
||||
| ✓ ready | 🎮 gog | Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs. | agents-skills-personal |
|
||||
| ✓ ready | 📦 healthcheck | Host security hardening and risk-tolerance configuration for OpenClaw deployments. Use when a user asks for security audits, firewall/SSH/update hardening, risk posture, exposure review, OpenClaw cron scheduling for periodic checks, or version status checks on a machine running OpenClaw (laptop, workstation, Pi, VPS). | openclaw-bundled |
|
||||
| ✓ ready | 📦 node-connect | Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale, or plugins.entries.device-pair.config.publicUrl. | openclaw-bundled |
|
||||
| ✓ ready | 💎 obsidian | Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli. | openclaw-bundled |
|
||||
| ✓ ready | 📦 skill-creator | Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations. | agents-skills-personal |
|
||||
| ✓ ready | 💬 slack | Use when you need to control Slack from OpenClaw via the slack tool, including reacting to messages or pinning/unpinning items in Slack channels or DMs. | openclaw-bundled |
|
||||
| ✓ ready | 📦 summarize | Summarize URLs or files with the summarize CLI (web, PDFs, images, audio, YouTube). | openclaw-managed |
|
||||
| ✓ ready | 📦 tmux | Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output. | agents-skills-personal |
|
||||
| ✓ ready | 📦 video-frames | Extract frames or short clips from videos using ffmpeg. | agents-skills-personal |
|
||||
| ✓ ready | ☔ weather | Get current weather and forecasts via wttr.in or Open-Meteo. Use when: user asks about weather, temperature, or forecasts for any location. NOT for: historical weather data, severe weather alerts, or detailed meteorological analysis. No API key needed. | openclaw-bundled |
|
||||
| ✓ ready | 📦 accli | This skill should be used when interacting with Apple Calendar on macOS. Use it for listing calendars, viewing events, creating/updating/deleting calendar events, and checking availability/free-busy times. Triggers on requests like "check my calendar", "schedule a meeting", "what's on my schedule", "am I free tomorrow", or any calendar-related operations. | openclaw-managed |
|
||||
| ✓ ready | 📦 agent-browser | Headless browser automation CLI optimized for AI agents with accessibility tree snapshots and ref-based element selection | openclaw-managed |
|
||||
| ✓ ready | 📦 agentmail | API-first email platform designed for AI agents. Create and manage dedicated email inboxes, send and receive emails programmatically, and handle email-based workflows with webhooks and real-time events. Use when you need to set up agent email identity, send emails from agents, handle incoming email workflows, or replace traditional email providers like Gmail with agent-friendly infrastructure. | openclaw-managed |
|
||||
| ✓ ready | 📦 Docker | Docker containers, images, Compose stacks, networking, volumes, debugging, production hardening, and the commands that keep real environments stable. Use when (1) the task touches Docker, Dockerfiles, images, containers, or Compose; (2) build reliability, runtime behavior, logs, ports, volumes, or security matter; (3) the agent needs Docker guidance and should apply it by default. | openclaw-managed |
|
||||
| ✓ ready | ⚙️ n8n | Manage n8n workflows and automations via API. Use when working with n8n workflows, executions, or automation tasks - listing workflows, activating/deactivating, checking execution status, manually triggering workflows, or debugging automation issues. | openclaw-managed |
|
||||
| ✓ ready | 📦 ontology | Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linking related objects, enforcing constraints, planning multi-step actions as graph transformations, or when skills need to share state. Trigger on "remember", "what do I know about", "link X to Y", "show dependencies", entity CRUD, or cross-skill data access. | agents-skills-personal |
|
||||
| ✓ ready | 📦 tavily-search | Web search via Tavily API (alternative to Brave). Use when the user asks to search the web / look up sources / find links and Brave web_search is unavailable or undesired. Returns a small set of relevant results (title, url, snippet) and can optionally include short answer summaries. | openclaw-managed |
|
||||
| ✓ ready | 📦 opencode-controller | Control and operate Opencode via slash commands. Use this skill to manage sessions, select models, switch agents (plan/build), and coordinate coding through Opencode. | agents-skills-personal |
|
||||
| ✓ ready | 🧱 opencode-omo | Turn coding requests into completed work. Plan with Prometheus, execute with Atlas, and iterate with Sisyphus in OpenCode. | openclaw-workspace |
|
||||
| ✓ ready | 📦 Powerpoint / PPTX | Create, inspect, and edit Microsoft PowerPoint presentations and PPTX decks with reliable layouts, templates, placeholders, notes, charts, and visual QA. Use when (1) the task is about PowerPoint or `.pptx`; (2) layouts, placeholders, notes, charts, comments, or template fidelity matter; (3) the deck must render cleanly after edits. | openclaw-managed |
|
||||
| ✓ ready | 📦 proactive-agent-lite | Transform AI agents from task-followers into proactive partners with memory architecture, reverse prompting, and self-healing patterns. Lightweight version focused on core proactive capabilities. | openclaw-workspace |
|
||||
| ✓ ready | 📦 self-improvement | Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Claude ('No, that's wrong...', 'Actually...'), (3) User requests a capability that doesn't exist, (4) An external API or tool fails, (5) Claude realizes its knowledge is outdated or incorrect, (6) A better approach is discovered for a recurring task. Also review learnings before major tasks. | openclaw-managed |
|
||||
| ✓ ready | 📦 task-summary | 任务执行总结技能。用于在完成任务后生成结构化的任务总结，记录任务目标、执行步骤、结果和经验教训，以便后续追溯和改进。 | openclaw-workspace |
|
||||
| ✓ ready | 📦 self-reflection | Periodic self-reflection on recent sessions. Analyzes what went well, what went wrong, and writes concise, actionable insights to the appropriate workspace files. Designed to run as a cron job. | agents-skills-personal |
|
||||
| ✓ ready | 📦 architecture-designer | Use when designing new system architecture, reviewing existing designs, or making architectural decisions. Invoke for system design, architecture review, design patterns, ADRs, scalability planning. | agents-skills-personal |
|
||||
| ✓ ready | 📦 automation-workflows | Design and implement automation workflows to save time and scale operations as a solopreneur. Use when identifying repetitive tasks to automate, building workflows across tools, setting up triggers and actions, or optimizing existing automations. Covers automation opportunity identification, workflow design, tool selection (Zapier, Make, n8n), testing, and maintenance. Trigger on "automate", "automation", "workflow automation", "save time", "reduce manual work", "automate my business", "no-code automation". | agents-skills-personal |
|
||||
| ✓ ready | 📦 backtest-expert | Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development. | agents-skills-personal |
|
||||
| ✓ ready | 📦 blog-writer | This skill should be used when writing blog posts, articles, or long-form content in the writer's distinctive writing style. It produces authentic, opinionated content that matches the writer's voice—direct, conversational, and grounded in personal experience. The skill handles the complete workflow from research review through Notion publication. Use this skill for drafting blog posts, thought leadership pieces, or any writing meant to reflect the writer's perspective on AI, productivity, sales, marketing, or technology topics. | agents-skills-personal |
|
||||
| ✓ ready | 📦 brainstorming | You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation. | agents-skills-personal |
|
||||
| ✓ ready | 📦 clawdefender | Security scanner and input sanitizer for AI agents. Detects prompt injection, command injection, SSRF, credential exfiltration, and path traversal attacks. Use when (1) installing new skills from ClawHub, (2) processing external input like emails, calendar events, Trello cards, or API responses, (3) validating URLs before fetching, (4) running security audits on your workspace. Protects agents from malicious content in untrusted data sources. | agents-skills-personal |
|
||||
| ✓ ready | 📦 Code | Coding workflow with planning, implementation, verification, and testing for clean software development. | agents-skills-personal |
|
||||
| ✓ ready | 📦 content-strategy | Build and execute a content marketing strategy for a solopreneur business. Use when planning what content to create, deciding on content formats and channels, building a content calendar, measuring content performance, or systematizing content production. Covers audience research for content, content pillars, distribution strategy, repurposing workflows, and metrics. Trigger on "content strategy", "content marketing", "what content should I create", "content plan", "content calendar", "content ideas", "content distribution", "grow through content". | agents-skills-personal |
|
||||
| ✓ ready | 📦 copywriting | Write persuasive copy for landing pages, emails, ads, sales pages, and marketing materials. Use when you need to write headlines, CTAs, product descriptions, ad copy, email sequences, or any text meant to drive action. Covers copywriting formulas (AIDA, PAS, FAB), headline writing, emotional triggers, objection handling in copy, and A/B testing. Trigger on "write copy", "copywriting", "landing page copy", "headline", "write a sales page", "ad copy", "email copy", "persuasive writing", "how to write [marketing text]". | agents-skills-personal |
|
||||
| ✓ ready | 📦 executing-plans | Use when you have a written implementation plan to execute in a separate session with review checkpoints | agents-skills-personal |
|
||||
| ✓ ready | 📦 feishu-chat-history | Fetch and summarize Feishu group chat history. Use when the user asks to read, review, or summarize messages from a Feishu group chat. Triggers: "看群聊记录", "群里聊了啥", "帮我看看这个群", "群消息历史", "chat history", "what did the group discuss". NOT for: sending messages (use message tool), reading documents (use feishu-doc skill), or wiki operations (use feishu-wiki skill). | agents-skills-personal |
|
||||
| ✓ ready | 📦 feishu-cron-reminder | Create cron jobs that reliably deliver reminders to Feishu (飞书) chats. Use when the user asks to set up scheduled reminders, periodic notifications, or any recurring task that should send messages to a Feishu conversation. Triggers: '飞书定时提醒', '定时任务发飞书', 'cron reminder to feishu', '每小时提醒', 'scheduled feishu message'. | agents-skills-personal |
|
||||
| ✓ ready | 📦 feishu-doc | Fetch content from Feishu (Lark) Wiki, Docs, Sheets, and Bitable. Automatically resolves Wiki URLs to real entities and converts content to Markdown. | agents-skills-personal |
|
||||
| ✓ ready | 📦 feishu-perm | Feishu permission management for documents and files. Activate when user mentions sharing, permissions, collaborators. | agents-skills-personal |
|
||||
| ✓ ready | 📦 feishu-screenshot | Capture macOS screenshots and send to Feishu. Use when the user asks to take a screenshot and share it via Feishu. Triggers: "截个屏发飞书", "截屏", "screenshot", "take a screenshot and send". NOT for: sending existing files (use feishu-send-file skill), or sending text messages (use message tool). | agents-skills-personal |
|
||||
| ✓ ready | 📦 feishu-send-file | Send files to a Feishu group or user via REST API. Use when the user explicitly asks to send a file, attachment, or document to a Feishu chat/group. Triggers: "发文件到飞书", "把这个文件发到群里", "send file to feishu", "发个附件". NOT for: sending text messages (use message tool), sending images/screenshots (use feishu-screenshot skill), or reading documents (use feishu-doc skill). | agents-skills-personal |
|
||||
| ✓ ready | 📦 FFmpeg Video Editor | Generate FFmpeg commands from natural language video editing requests - cut, trim, convert, compress, change aspect ratio, extract audio, and more. | agents-skills-personal |
|
||||
| ✓ ready | 📦 find-skills | Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill. | agents-skills-personal |
|
||||
| ✓ ready | 📦 frontend-design | Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when building web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics. | agents-skills-personal |
|
||||
| ✓ ready | 📦 git-essentials | Essential Git commands and workflows for version control, branching, and collaboration. | agents-skills-personal |
|
||||
| ✓ ready | 📦 interview-designer | Analyze resumes and design interview strategies using evidence-based methodology. Transforms interview prep from "read resume → ask questions" into "define standard → forensic evidence → future simulation". Combines Geoff Smart's Topgrading, Lou Adler's performance-based hiring, and Daniel Kahneman's bias control. Use when preparing for interviews, creating structured interview guides, or designing questions to validate candidate competencies. | agents-skills-personal |
|
||||
| ✓ ready | 📦 Market Research | Size markets, analyze competitors, and validate opportunities with practical frameworks and free data sources. | agents-skills-personal |
|
||||
| ✓ ready | 📦 Memory | Infinite organized memory that complements your agent's built-in memory with unlimited categorized storage. | agents-skills-personal |
|
||||
| ✓ ready | 📦 obsidian-ontology-sync | Bidirectional sync between Obsidian PKM (human-friendly notes) and structured ontology (machine-queryable graph). Automatically extracts entities and relationships from markdown, maintains ontology graph, and provides feedback to improve note structure. Run sync every few hours via cron. | agents-skills-personal |
|
||||
| ✓ ready | 📦 research-paper-writer | Creates formal academic research papers following IEEE/ACM formatting standards with proper structure, citations, and scholarly writing style. Use when the user asks to write a research paper, academic paper, or conference paper on any topic. | agents-skills-personal |
|
||||
| ✓ ready | 📦 security-auditor | Use when reviewing code for security vulnerabilities, implementing authentication flows, auditing OWASP Top 10, configuring CORS/CSP headers, handling secrets, input validation, SQL injection prevention, XSS protection, or any security-related code review. | agents-skills-personal |
|
||||
| ✓ ready | 📦 SEO (Site Audit + Content Writer + Competitor Analysis) | SEO specialist agent with site audits, content writing, keyword research, technical fixes, link building, and ranking strategies. | agents-skills-personal |
|
||||
| ✓ ready | 📦 seo-content-writer | Use when the user asks to "write SEO content", "create a blog post", "write an article", "content writing", "draft optimized content", "write me an article", "create a blog post about", "help me write SEO content", or "draft content for". Creates high-quality, SEO-optimized content that ranks in search engines. Applies on-page SEO best practices, keyword optimization, and content structure for maximum visibility and engagement. | agents-skills-personal |
|
||||
| ✓ ready | 📦 skill-vetter | Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns. | agents-skills-personal |
|
||||
| ✓ ready | 📦 social-content | When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' or 'viral content.' This skill covers content creation, repurposing, and platform-specific strategies. | agents-skills-personal |
|
||||
| ✓ ready | 📦 Social Media Scheduler | Plan, draft, and organize social media content across platforms. Create content calendars, write platform-optimized posts, and maintain consistent posting schedules. | agents-skills-personal |
|
||||
| ✓ ready | 📦 supabase-postgres-best-practices | Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations. | agents-skills-personal |
|
||||
| ✓ ready | 📦 ui-ux-pro-max | UI/UX design intelligence and implementation guidance for building polished interfaces. Use when the user asks for UI design, UX flows, information architecture, visual style direction, design systems/tokens, component specs, copy/microcopy, accessibility, or to generate/critique/refine frontend UI (HTML/CSS/JS, React, Next.js, Vue, Svelte, Tailwind). Includes workflows for (1) generating new UI layouts and styling, (2) improving existing UI/UX, (3) producing design-system tokens and component guidelines, and (4) turning UX recommendations into concrete code changes. | agents-skills-personal |
|
||||
| ✓ ready | 📦 writing-plans | Use when you have a spec or requirements for a multi-step task, before touching code | agents-skills-personal |
|
||||
| ✓ ready | 📦 Playwright (Automation + MCP + Scraper) | Browser automation via Playwright MCP. Navigate websites, click elements, fill forms, take screenshots, extract data, and debug real browser workflows. Use when (1) you need a real browser, not static fetch; (2) the task involves Playwright MCP, browser tools, Playwright tests, scripts, or JS-rendered pages; (3) the user wants navigation, forms, screenshots, PDFs, downloads, or browser-driven extraction turned into a reliable outcome. | openclaw-workspace |
|
||||
|
||||
---
|
||||
|
||||
## Doctor Warnings
|
||||
|
||||
> ⚠️ **Warning 1**: channels.telegram.accounts.bot1.groupPolicy is "allowlist" but groupAllowFrom (and allowFrom) is empty — all group messages will be silently dropped. Add sender IDs to channels.telegram.accounts.bot1.groupAllowFrom or channels.telegram.accounts.bot1.allowFrom, or set groupPolicy to "open".
|
||||
|
||||
> ⚠️ **Warning 2**: channels.telegram.accounts.bot2.groupPolicy is "allowlist" but groupAllowFrom (and allowFrom) is empty — all group messages will be silently dropped. Add sender IDs to channels.telegram.accounts.bot2.groupAllowFrom or channels.telegram.accounts.bot2.allowFrom, or set groupPolicy to "open".
|
||||
|
||||
> ⚠️ **Warning 3**: channels.telegram.accounts.xingshu.groupPolicy is "allowlist" but groupAllowFrom (and allowFrom) is empty — all group messages will be silently dropped. Add sender IDs to channels.telegram.accounts.xingshu.groupAllowFrom or channels.telegram.accounts.xingshu.allowFrom, or set groupPolicy to "open".
|
||||
|
||||
> ⚠️ **Warning 4**: channels.telegram.accounts.default.groupPolicy is "allowlist" but groupAllowFrom (and allowFrom) is empty — all group messages will be silently dropped. Add sender IDs to channels.telegram.accounts.default.groupAllowFrom or channels.telegram.accounts.default.allowFrom, or set groupPolicy to "open".
|
||||
|
||||
**Tip**: Run `openclaw doctor --fix` to apply these changes.
|
||||
|
||||
@@ -1,98 +1,98 @@
|
||||
---
|
||||
title: OpenClaw 备份脚本使用指南
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: [backup, openclaw, openclaw-cron-job]
|
||||
---
|
||||
|
||||
# OpenClaw 备份脚本使用指南
|
||||
|
||||
#openclaw #backup #openclaw-cron-job
|
||||
## 概述
|
||||
|
||||
OpenClaw 备份脚本用于自动备份 OpenClaw 配置到 NAS 存储。
|
||||
|
||||
## 脚本位置
|
||||
|
||||
- **Mac Mini**: `~/.openclaw/scripts/backup-openclaw.sh`
|
||||
- **Ubuntu2**: `/home/shenwei/.openclaw/scripts/backup-openclaw.sh`
|
||||
|
||||
## 使用方法
|
||||
|
||||
```bash
|
||||
# Mac Mini 备份
|
||||
~/.openclaw/scripts/backup-openclaw.sh macmini
|
||||
|
||||
# Ubuntu2 备份
|
||||
/home/shenwei/.openclaw/scripts/backup-openclaw.sh ubuntu2
|
||||
```
|
||||
|
||||
## 文件命名规则
|
||||
|
||||
备份文件命名格式：`openclaw-{node}-{timestamp}.tar`
|
||||
|
||||
| 节点 | 示例 |
|
||||
|------|------|
|
||||
| Mac Mini | `openclaw-macmini-20260317112001.tar` |
|
||||
| Ubuntu2 | `openclaw-ubuntu2-20260317112001.tar` |
|
||||
|
||||
## 备份目的地
|
||||
|
||||
- **NAS 路径**: `/volume2/backup/openclaw/`
|
||||
- **访问方式**: SSH (shenwei@nas)
|
||||
|
||||
## 执行流程
|
||||
|
||||
```
|
||||
[1/5] Creating backup: openclaw-{node}-{timestamp}.tar
|
||||
[2/5] Verifying backup...
|
||||
[3/5] Transferring to NAS...
|
||||
[4/5] Verifying transfer...
|
||||
[5/5] Cleaning up local temporary files...
|
||||
```
|
||||
|
||||
## 备份内容
|
||||
|
||||
- `~/.openclaw/` 目录
|
||||
- 排除项：
|
||||
- `logs/` 目录
|
||||
- `*.log` 文件
|
||||
- `.git` 目录
|
||||
|
||||
## 验证备份
|
||||
|
||||
查看 NAS 上的备份文件：
|
||||
|
||||
```bash
|
||||
ssh nas "ls -la /volume2/backup/openclaw/"
|
||||
```
|
||||
|
||||
## 验证 tar 文件
|
||||
|
||||
```bash
|
||||
ssh nas "tar -tvf /volume2/backup/openclaw/openclaw-{node}-{timestamp}.tar"
|
||||
```
|
||||
|
||||
## 定时备份 (可选)
|
||||
|
||||
可以使用 cron 设置定时备份：
|
||||
|
||||
```bash
|
||||
# 每天凌晨 3 点自动备份
|
||||
0 3 * * * /home/shenwei/.openclaw/scripts/backup-openclaw.sh ubuntu2 >> /home/shenwei/.openclaw/logs/backup.log 2>&1
|
||||
```
|
||||
|
||||
## 注意事项
|
||||
|
||||
1. 确保 Ubuntu2 到 NAS 的 SSH 免密登录已配置
|
||||
2. 确保 NAS 备份目录存在
|
||||
3. 备份文件会自动清理本地临时文件
|
||||
4. 首次使用建议手动执行测试
|
||||
|
||||
## 相关文档
|
||||
|
||||
- SSH 免密登录配置: [[Mac Mini 配置 SSH 免密登录到 NAS]]
|
||||
- Ubuntu2 SSH 配置: [[Ubuntu2 SSH 配置]]
|
||||
---
|
||||
title: OpenClaw 备份脚本使用指南
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: [backup, openclaw, openclaw-cron-job]
|
||||
---
|
||||
|
||||
# OpenClaw 备份脚本使用指南
|
||||
|
||||
#openclaw #backup #openclaw-cron-job
|
||||
## 概述
|
||||
|
||||
OpenClaw 备份脚本用于自动备份 OpenClaw 配置到 NAS 存储。
|
||||
|
||||
## 脚本位置
|
||||
|
||||
- **Mac Mini**: `~/.openclaw/scripts/backup-openclaw.sh`
|
||||
- **Ubuntu2**: `/home/shenwei/.openclaw/scripts/backup-openclaw.sh`
|
||||
|
||||
## 使用方法
|
||||
|
||||
```bash
|
||||
# Mac Mini 备份
|
||||
~/.openclaw/scripts/backup-openclaw.sh macmini
|
||||
|
||||
# Ubuntu2 备份
|
||||
/home/shenwei/.openclaw/scripts/backup-openclaw.sh ubuntu2
|
||||
```
|
||||
|
||||
## 文件命名规则
|
||||
|
||||
备份文件命名格式：`openclaw-{node}-{timestamp}.tar`
|
||||
|
||||
| 节点 | 示例 |
|
||||
|------|------|
|
||||
| Mac Mini | `openclaw-macmini-20260317112001.tar` |
|
||||
| Ubuntu2 | `openclaw-ubuntu2-20260317112001.tar` |
|
||||
|
||||
## 备份目的地
|
||||
|
||||
- **NAS 路径**: `/volume2/backup/openclaw/`
|
||||
- **访问方式**: SSH (shenwei@nas)
|
||||
|
||||
## 执行流程
|
||||
|
||||
```
|
||||
[1/5] Creating backup: openclaw-{node}-{timestamp}.tar
|
||||
[2/5] Verifying backup...
|
||||
[3/5] Transferring to NAS...
|
||||
[4/5] Verifying transfer...
|
||||
[5/5] Cleaning up local temporary files...
|
||||
```
|
||||
|
||||
## 备份内容
|
||||
|
||||
- `~/.openclaw/` 目录
|
||||
- 排除项：
|
||||
- `logs/` 目录
|
||||
- `*.log` 文件
|
||||
- `.git` 目录
|
||||
|
||||
## 验证备份
|
||||
|
||||
查看 NAS 上的备份文件：
|
||||
|
||||
```bash
|
||||
ssh nas "ls -la /volume2/backup/openclaw/"
|
||||
```
|
||||
|
||||
## 验证 tar 文件
|
||||
|
||||
```bash
|
||||
ssh nas "tar -tvf /volume2/backup/openclaw/openclaw-{node}-{timestamp}.tar"
|
||||
```
|
||||
|
||||
## 定时备份 (可选)
|
||||
|
||||
可以使用 cron 设置定时备份：
|
||||
|
||||
```bash
|
||||
# 每天凌晨 3 点自动备份
|
||||
0 3 * * * /home/shenwei/.openclaw/scripts/backup-openclaw.sh ubuntu2 >> /home/shenwei/.openclaw/logs/backup.log 2>&1
|
||||
```
|
||||
|
||||
## 注意事项
|
||||
|
||||
1. 确保 Ubuntu2 到 NAS 的 SSH 免密登录已配置
|
||||
2. 确保 NAS 备份目录存在
|
||||
3. 备份文件会自动清理本地临时文件
|
||||
4. 首次使用建议手动执行测试
|
||||
|
||||
## 相关文档
|
||||
|
||||
- SSH 免密登录配置: [[Mac Mini 配置 SSH 免密登录到 NAS]]
|
||||
- Ubuntu2 SSH 配置: [[Ubuntu2 SSH 配置]]
|
||||
|
||||
@@ -1,396 +1,396 @@
|
||||
---
|
||||
title: OpenClaw 技能笔记
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: [openclaw, openclaw-skills, skills]
|
||||
---
|
||||
|
||||
# OpenClaw 技能笔记
|
||||
|
||||
---
|
||||
#openclaw #openclaw-skills #skills
|
||||
## 📋 技能清单总览
|
||||
|
||||
本文档记录 OpenClaw 中所有可用的技能（Skills）。
|
||||
|
||||
---
|
||||
|
||||
## 🔐 账号与密码
|
||||
|
||||
### 1. 1password
|
||||
- **描述:** 1Password CLI (op) 工具
|
||||
- **用途:** 安装CLI、桌面应用集成、单/多账户登录、读写/运行密码
|
||||
- **路径:** `~/.agents/skills/1password-1.0.1/SKILL.md`
|
||||
|
||||
---
|
||||
|
||||
## 🍎 Apple 生态
|
||||
|
||||
### 2. apple-notes
|
||||
- **描述:** Apple Notes 管理 via `memo` CLI
|
||||
- **用途:** 创建、查看、编辑、删除、搜索、移动、导出笔记
|
||||
- **路径:** `~/.openclaw/skills/apple-notes/SKILL.md`
|
||||
|
||||
### 3. apple-reminders
|
||||
- **描述:** Apple Reminders via `remindctl` CLI
|
||||
- **用途:** 列出、添加、编辑、完成、删除提醒，支持列表、日期过滤、JSON/纯文本输出
|
||||
- **路径:** `~/.openclaw/skills/apple-reminders/SKILL.md`
|
||||
|
||||
### 4. accli
|
||||
- **描述:** Apple Calendar CLI
|
||||
- **用途:** 列出日历、查看事件、创建/更新/删除日历事件、检查空闲时间
|
||||
- **触发词:** "查看日历"、"安排会议"、"我今天有什么安排"、"明天我有空吗"
|
||||
- **路径:** `~/.openclaw/skills/accli/SKILL.md`
|
||||
|
||||
---
|
||||
|
||||
## ☁️ 云服务与协作
|
||||
|
||||
### 5. gog
|
||||
- **描述:** Google Workspace CLI
|
||||
- **用途:** Gmail、日历、云盘、联系人、表格、文档
|
||||
- **路径:** `~/.agents/skills/gog/SKILL.md`
|
||||
|
||||
### 6. feishu-chat-history
|
||||
- **描述:** 获取飞书群聊历史
|
||||
- **用途:** 读取、回顾、总结飞书群聊消息
|
||||
- **触发词:** "看群聊记录"、"群里聊了啥"、"chat history"
|
||||
- **路径:** `~/.agents/skills/feishu-chat-history/SKILL.md`
|
||||
|
||||
### 7. feishu-cron-reminder
|
||||
- **描述:** 飞书定时提醒
|
||||
- **用途:** 创建定时发送消息到飞书聊天的cron任务
|
||||
- **触发词:** "飞书定时提醒"、"定时任务发飞书"、"每小时提醒"
|
||||
- **路径:** `~/.agents/skills/feishu-cron-reminder/SKILL.md`
|
||||
|
||||
### 8. feishu-doc
|
||||
- **描述:** 飞书文档获取
|
||||
- **用途:** 获取飞书Wiki、文档、表格、Bitable内容，自动转换为Markdown
|
||||
- **路径:** `~/.agents/skills/feishu-doc-1.2.7/SKILL.md`
|
||||
|
||||
### 9. feishu-perm
|
||||
- **描述:** 飞书权限管理
|
||||
- **用途:** 文档和文件的分享、权限、协作者管理
|
||||
- **触发词:** 分享、权限、协作者
|
||||
- **路径:** `~/.agents/skills/feishu-perm/SKILL.md`
|
||||
|
||||
### 10. feishu-screenshot
|
||||
- **描述:** 截屏并发送到飞书
|
||||
- **用途:** 截取屏幕并通过飞书分享
|
||||
- **触发词:** "截个屏发飞书"、"截屏"、"screenshot"
|
||||
- **路径:** `~/.agents/skills/feishu-screenshot/SKILL.md`
|
||||
|
||||
### 11. feishu-send-file
|
||||
- **描述:** 发送文件到飞书
|
||||
- **用途:** 通过REST API发送文件、附件到飞书群或个人
|
||||
- **触发词:** "发文件到飞书"、"send file to feishu"
|
||||
- **路径:** `~/.agents/skills/feishu-send-file/SKILL.md`
|
||||
|
||||
---
|
||||
|
||||
## 💬 通讯工具
|
||||
|
||||
### 12. slack
|
||||
- **描述:** Slack 控制
|
||||
- **用途:** 通过 slack 工具控制Slack，包括消息反应、pin/unpin
|
||||
- **路径:** `/opt/homebrew/lib/node_modules/openclaw/skills/slack/SKILL.md`
|
||||
|
||||
---
|
||||
|
||||
## 🌐 网络与浏览器
|
||||
|
||||
### 13. agent-browser
|
||||
- **描述:** 无头浏览器自动化CLI
|
||||
- **用途:** 为AI代理优化的浏览器自动化，支持无障碍树快照和基于引用的元素选择
|
||||
- **路径:** `~/.openclaw/skills/agent-browser-clawdbot/SKILL.md`
|
||||
|
||||
### 14. tavily-search
|
||||
- **描述:** Tavily 搜索API
|
||||
- **用途:** 网页搜索（替代Brave），返回相关结果标题、URL、摘要
|
||||
- **路径:** `~/.openclaw/skills/openclaw-tavily-search/SKILL.md`
|
||||
|
||||
---
|
||||
|
||||
## 🛠️ 开发工具
|
||||
|
||||
### 15. Docker
|
||||
- **描述:** Docker 容器、镜像、Compose、网络、卷、调试
|
||||
- **用途:** Docker相关操作、生产环境加固、命令保持稳定
|
||||
- **路径:** `~/.openclaw/skills/docker/SKILL.md`
|
||||
|
||||
### 16. Code
|
||||
- **描述:** 编码工作流
|
||||
- **用途:** 规划、实现、验证、测试的清洁软件开发流程
|
||||
- **路径:** `~/.agents/skills/code-1.0.4/SKILL.md`
|
||||
|
||||
### 17. git-essentials
|
||||
- **描述:** 基础Git命令
|
||||
- **用途:** 版本控制、分支、协作
|
||||
- **路径:** `~/.agents/skills/git-essentials-1.0.0/SKILL.md`
|
||||
|
||||
### 18. frontend-design
|
||||
- **描述:** 前端界面设计
|
||||
- **用途:** 创建独特、生产级的前端界面，高设计质量
|
||||
- **路径:** `~/.agents/skills/frontend-design-3-0.1.0/SKILL.md`
|
||||
|
||||
### 19. security-auditor
|
||||
- **描述:** 安全审计
|
||||
- **用途:** 代码安全漏洞审查、身份验证流程、OWASP Top 10审计、CORS/CSP配置、敏感数据处理、输入验证、SQL注入预防、XSS保护
|
||||
- **路径:** `~/.agents/skills/security-auditor-1.0.0/SKILL.md`
|
||||
|
||||
### 20. architecture-designer
|
||||
- **描述:** 系统架构设计
|
||||
- **用途:** 设计新系统架构、审查现有设计、架构决策、ADRs、可扩展性规划
|
||||
- **路径:** `~/.agents/skills/architecture-designer-0.1.0/SKILL.md`
|
||||
|
||||
### 21. supabase-postgres-best-practices
|
||||
- **描述:** Supabase Postgres 最佳实践
|
||||
- **用途:** Postgres性能优化和最佳实践
|
||||
- **路径:** `~/.agents/skills/supabase-postgres-best-practices/SKILL.md`
|
||||
|
||||
### 22. tmux
|
||||
- **描述:** Tmux 远程控制
|
||||
- **用途:** 远程控制tmux会话，发送按键和抓取面板输出
|
||||
- **路径:** `~/.agents/skills/tmux-1.0.0/SKILL.md`
|
||||
|
||||
---
|
||||
|
||||
## 📝 笔记与知识管理
|
||||
|
||||
### 23. obsidian
|
||||
- **描述:** Obsidian 保险库
|
||||
- **用途:** 处理Obsidian纯文本Markdown笔记，通过obsidian-cli自动化
|
||||
- **路径:** `/opt/homebrew/lib/node_modules/openclaw/skills/obsidian/SKILL.md`
|
||||
|
||||
### 24. ontology
|
||||
- **描述:** 知识图谱
|
||||
- **用途:** 结构化代理记忆和可组合技能，创建/查询实体（Person、Project、Task、Event、Document），链接相关对象，执行约束，多步骤动作规划
|
||||
- **触发词:** "记住"、"关于X我知道什么"、"链接X到Y"、"显示依赖"
|
||||
- **路径:** `~/.agents/skills/ontology/SKILL.md`
|
||||
|
||||
### 25. Memory
|
||||
- **描述:** 无限有序记忆
|
||||
- **用途:** 补充代理内置记忆的无限分类存储
|
||||
- **路径:** `~/.agents/skills/memory-1.0.2/SKILL.md`
|
||||
|
||||
### 26. obsidian-ontology-sync
|
||||
- **描述:** Obsidian与 Ontology 双向同步
|
||||
- **用途:** 从markdown自动提取实体和关系，维护本体图谱，提供反馈改进笔记结构
|
||||
- **路径:** `~/.agents/skills/obsidian-ontology-sync-1.0.1/SKILL.md`
|
||||
|
||||
---
|
||||
|
||||
## 🎨 内容创作
|
||||
|
||||
### 27. blog-writer
|
||||
- **描述:** 博客文章写作
|
||||
- **用途:** 以作家独特风格写博客文章、长篇内容，从研究到Notion发布的完整工作流
|
||||
- **路径:** `~/.agents/skills/blog-writer-0.1.0/SKILL.md`
|
||||
|
||||
### 28. copywriting
|
||||
- **描述:** 文案写作
|
||||
- **用途:** 为落地页、邮件、广告、销售页、营销材料写 persuasive copy，标题、CTA、产品描述、广告文案、邮件序列
|
||||
- **触发词:** "写文案"、"copywriting"、"landing page copy"、"headline"
|
||||
- **路径:** `~/.agents/skills/copywriting-0.1.0/SKILL.md`
|
||||
|
||||
### 29. content-strategy
|
||||
- **描述:** 内容营销策略
|
||||
- **用途:** 为solopreneur业务构建和执行内容营销策略
|
||||
- **触发词:** "内容策略"、"content marketing"、"内容计划"、"内容日历"
|
||||
- **路径:** `~/.agents/skills/content-strategy-0.1.0/SKILL.md`
|
||||
|
||||
### 30. seo-content-writer
|
||||
- **描述:** SEO内容写作
|
||||
- **用途:** 写SEO优化内容、创建博客文章、文章
|
||||
- **触发词:** "写SEO内容"、"创建博客文章"、"内容写作"
|
||||
- **路径:** `~/.agents/skills/seo-content-writer-2.0.0/SKILL.md`
|
||||
|
||||
### 31. social-content
|
||||
- **描述:** 社交媒体内容
|
||||
- **用途:** 创建、安排、优化LinkedIn、Twitter/X、Instagram、TikTok、Facebook等内容
|
||||
- **触发词:** "LinkedIn post"、"Twitter thread"、"社交媒体"、"内容日历"
|
||||
- **路径:** `~/.agents/skills/social-content-generator-0.1.0/SKILL.md`
|
||||
|
||||
### 32. Social Media Scheduler
|
||||
- **描述:** 社交媒体排程
|
||||
- **用途:** 计划、起草、跨平台组织社交媒体内容，创建内容日历
|
||||
- **路径:** `~/.agents/skills/social-media-scheduler-1.0.0/SKILL.md`
|
||||
|
||||
### 33. research-paper-writer
|
||||
- **描述:** 研究论文写作
|
||||
- **用途:** 创建遵循IEEE/ACM格式标准的正式学术论文
|
||||
- **路径:** `~/.agents/skills/research-paper-writer-0.1.0/SKILL.md`
|
||||
|
||||
### 34. Powerpoint / PPTX
|
||||
- **描述:** PowerPoint 演示文稿
|
||||
- **用途:** 创建、检查、编辑Microsoft PowerPoint演示文稿，可靠的布局、模板、占位符、笔记、图表
|
||||
- **路径:** `~/.openclaw/skills/powerpoint-pptx/SKILL.md`
|
||||
|
||||
---
|
||||
|
||||
## 📊 商业与分析
|
||||
|
||||
### 35. Market Research
|
||||
- **描述:** 市场研究
|
||||
- **用途:** 规模市场、分析竞争对手、用实际框架和数据源验证机会
|
||||
- **路径:** `~/.agents/skills/market-research-1.0.0/SKILL.md`
|
||||
|
||||
### 36. interview-designer
|
||||
- **描述:** 面试设计
|
||||
- **用途:** 分析简历，使用基于证据的方法设计面试策略
|
||||
- **路径:** `~/.agents/skills/interview-designer-1.0.0/SKILL.md`
|
||||
|
||||
### 37. backtest-expert
|
||||
- **描述:** 回测专家
|
||||
- **用途:** 系统交易策略回测的专家指导
|
||||
- **触发词:** 回测、策略验证、鲁棒性测试、避免过度拟合
|
||||
- **路径:** `~/.agents/skills/backtest-expert-0.1.0/SKILL.md`
|
||||
|
||||
### 38. automation-workflows
|
||||
- **描述:** 自动化工作流
|
||||
- **用途:** 设计和实施自动化工作流以节省时间和扩展运营
|
||||
- **触发词:** "自动化"、"automation workflow"、"save time"、"reduce manual work"
|
||||
- **路径:** `~/.agents/skills/automation-workflows-0.1.0/SKILL.md`
|
||||
|
||||
---
|
||||
|
||||
## 🧠 AI 代理能力
|
||||
|
||||
### 39. proactive-agent-lite
|
||||
- **描述:** 主动代理Lite
|
||||
- **用途:** 将AI代理从任务追随者转变为积极主动的伙伴，具有记忆架构、reverse prompting和自愈模式
|
||||
- **路径:** `~/.openclaw/skills/proactive-agent-lite/SKILL.md`
|
||||
|
||||
### 40. self-improvement
|
||||
- **描述:** 自我改进
|
||||
- **用途:** 捕获学习、错误、纠正以实现持续改进
|
||||
- **触发词:** 命令/操作失败、用户纠正、请求不存在的功能、外部API失败、知识过时
|
||||
- **路径:** `~/.openclaw/skills/self-improving-agent/SKILL.md`
|
||||
|
||||
### 41. self-reflection
|
||||
- **描述:** 自我反思
|
||||
- **用途:** 定期自我反思，分析近期会话，写简洁可行的见解
|
||||
- **路径:** `~/.agents/skills/agent-self-reflection-1.0.0/SKILL.md`
|
||||
|
||||
### 42. brainstorming
|
||||
- **描述:** 头脑风暴
|
||||
- **用途:** 在任何创造性工作之前必须使用 - 创建功能、构建组件、添加功能或修改行为
|
||||
- **路径:** `~/.agents/skills/brainstorming-0.1.0/SKILL.md`
|
||||
|
||||
### 43. writing-plans
|
||||
- **描述:** 写作计划
|
||||
- **用途:** 有规范/需求的多步骤任务规范
|
||||
- **路径:** `~/.agents/skills/writing-plans-0.1.0/SKILL.md`
|
||||
|
||||
### 44. executing-plans
|
||||
- **描述:** 执行计划
|
||||
- **用途:** 在单独会话中执行包含审查检查点的书面实施计划
|
||||
- **路径:** `~/.agents/skills/executing-plans-0.1.0/SKILL.md`
|
||||
|
||||
### 45. task-summary
|
||||
- **描述:** 任务总结
|
||||
- **用途:** 任务完成后生成结构化总结，记录目标、步骤、结果、经验教训
|
||||
- **路径:** `~/.openclaw/skills/task-summary/SKILL.md`
|
||||
|
||||
---
|
||||
|
||||
## 🔧 工具与系统
|
||||
|
||||
### 46. clawhub
|
||||
- **描述:** ClawHub CLI
|
||||
- **用途:** 从clawhub.com搜索、安装、更新、发布代理技能
|
||||
- **路径:** `/opt/homebrew/lib/node_modules/openclaw/skills/clawhub/SKILL.md`
|
||||
|
||||
### 47. find-skills
|
||||
- **描述:** 发现技能
|
||||
- **用途:** 当用户询问"如何做X"、"找X的技能"、"有能...的技能吗"时帮助用户发现和安装技能
|
||||
- **路径:** `~/.agents/skills/find-skills/SKILL.md`
|
||||
|
||||
### 48. skill-creator
|
||||
- **描述:** 技能创建器
|
||||
- **用途:** 创建有效技能的指南
|
||||
- **路径:** `~/.agents/skills/skill-creator-0.1.0/SKILL.md`
|
||||
|
||||
### 49. skill-vetter
|
||||
- **描述:** 技能审核
|
||||
- **用途:** AI代理的安全优先技能审核，安装来自ClawHub、GitHub或其他来源的技能之前检查
|
||||
- **路径:** `~/.agents/skills/skill-vetter-1.0.0/SKILL.md`
|
||||
|
||||
### 50. clawdefender
|
||||
- **描述:** 安全防御
|
||||
- **用途:** AI代理的安全扫描器和输入清理器，检测prompt注入、命令注入、SSRF、凭证外泄、路径遍历攻击
|
||||
- **路径:** `~/.agents/skills/clawdefender-1/SKILL.md`
|
||||
|
||||
### 51. opencode-controller
|
||||
- **描述:** Opencode 控制器
|
||||
- **用途:** 通过斜杠命令控制Opencode，管理会话、选择模型、切换代理
|
||||
- **路径:** `~/.agents/skills/opencode-controller-1.0.0/SKILL.md`
|
||||
|
||||
---
|
||||
|
||||
## 🌤️ 生活与娱乐
|
||||
|
||||
### 52. weather
|
||||
- **描述:** 天气
|
||||
- **用途:** 通过wttr.in或Open-Meteo获取当前天气和预报
|
||||
- **触发词:** 天气、温度、预报
|
||||
- **路径:** `/opt/homebrew/lib/node_modules/openclaw/skills/weather/SKILL.md`
|
||||
|
||||
### 53. video-frames
|
||||
- **描述:** 视频帧提取
|
||||
- **用途:** 使用ffmpeg从视频提取帧或短片段
|
||||
- **路径:** `~/.agents/skills/video-frames-1.0.0/SKILL.md`
|
||||
|
||||
### 54. FFmpeg Video Editor
|
||||
- **描述:** FFmpeg 视频编辑器
|
||||
- **用途:** 从自然语言视频编辑请求生成FFmpeg命令 - 剪切、裁剪、转换、压缩、改变宽高比、提取音频等
|
||||
- **路径:** `~/.agents/skills/ffmpeg-video-editor-1.0.0/SKILL.md`
|
||||
|
||||
### 55. UI/UX Pro Max
|
||||
- **描述:** UI/UX 设计
|
||||
- **用途:** UI/UX设计智能和实现指导，构建精美界面
|
||||
- **路径:** `~/.agents/skills/ui-ux-pro-max-0.1.0/SKILL.md`
|
||||
|
||||
---
|
||||
|
||||
## 🛡️ 系统与运维
|
||||
|
||||
### 56. healthcheck
|
||||
- **描述:** 主机安全检查
|
||||
- **用途:** 主机安全加固和风险容忍配置
|
||||
- **触发词:** 安全审计、防火墙/SSH/更新加固、风险态势、暴露审查、OpenClaw cron调度
|
||||
- **路径:** `/opt/homebrew/lib/node_modules/openclaw/skills/healthcheck/SKILL.md`
|
||||
|
||||
### 57. node-connect
|
||||
- **描述:** OpenClaw 节点连接
|
||||
- **用途:** 诊断Android、iOS、macOS companion app的配对失败
|
||||
- **触发词:** QR/设置码手动连接失败、本地Wi-Fi正常但VPS/tailnet不正常、配对要求、未经授权、bootstrap token无效/过期
|
||||
- **路径:** `/opt/homebrew/lib/node_modules/openclaw/skills/node-connect/SKILL.md`
|
||||
|
||||
---
|
||||
|
||||
## 📊 技能分类汇总
|
||||
|
||||
| 分类 | 数量 | 技能 |
|
||||
|------|------|------|
|
||||
| Apple 生态 | 3 | apple-notes, apple-reminders, accli |
|
||||
| 云服务/协作 | 7 | gog, feishu-*(6个) |
|
||||
| 通讯工具 | 1 | slack |
|
||||
| 网络/浏览器 | 2 | agent-browser, tavily-search |
|
||||
| 开发工具 | 8 | Docker, Code, git-essentials, frontend-design, security-auditor, architecture-designer, supabase-postgres-best-practices, tmux |
|
||||
| 笔记/知识管理 | 5 | obsidian, ontology, Memory, obsidian-ontology-sync, task-summary |
|
||||
| 内容创作 | 8 | blog-writer, copywriting, content-strategy, seo-content-writer, social-content, Social Media Scheduler, research-paper-writer, Powerpoint/PPTX |
|
||||
| 商业/分析 | 4 | Market Research, interview-designer, backtest-expert, automation-workflows |
|
||||
| AI代理能力 | 7 | proactive-agent-lite, self-improvement, self-reflection, brainstorming, writing-plans, executing-plans, task-summary |
|
||||
| 工具/系统 | 6 | clawhub, find-skills, skill-creator, skill-vetter, clawdefender, opencode-controller |
|
||||
| 生活/娱乐 | 4 | weather, video-frames, FFmpeg Video Editor, UI/UX Pro Max |
|
||||
| 系统/运维 | 2 | healthcheck, node-connect |
|
||||
|
||||
**总计: 57 个技能**
|
||||
|
||||
---
|
||||
|
||||
*笔记创建于 2026-03-19 by 星辉*
|
||||
---
|
||||
title: OpenClaw 技能笔记
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: [openclaw, openclaw-skills, skills]
|
||||
---
|
||||
|
||||
# OpenClaw 技能笔记
|
||||
|
||||
---
|
||||
#openclaw #openclaw-skills #skills
|
||||
## 📋 技能清单总览
|
||||
|
||||
本文档记录 OpenClaw 中所有可用的技能（Skills）。
|
||||
|
||||
---
|
||||
|
||||
## 🔐 账号与密码
|
||||
|
||||
### 1. 1password
|
||||
- **描述:** 1Password CLI (op) 工具
|
||||
- **用途:** 安装CLI、桌面应用集成、单/多账户登录、读写/运行密码
|
||||
- **路径:** `~/.agents/skills/1password-1.0.1/SKILL.md`
|
||||
|
||||
---
|
||||
|
||||
## 🍎 Apple 生态
|
||||
|
||||
### 2. apple-notes
|
||||
- **描述:** Apple Notes 管理 via `memo` CLI
|
||||
- **用途:** 创建、查看、编辑、删除、搜索、移动、导出笔记
|
||||
- **路径:** `~/.openclaw/skills/apple-notes/SKILL.md`
|
||||
|
||||
### 3. apple-reminders
|
||||
- **描述:** Apple Reminders via `remindctl` CLI
|
||||
- **用途:** 列出、添加、编辑、完成、删除提醒，支持列表、日期过滤、JSON/纯文本输出
|
||||
- **路径:** `~/.openclaw/skills/apple-reminders/SKILL.md`
|
||||
|
||||
### 4. accli
|
||||
- **描述:** Apple Calendar CLI
|
||||
- **用途:** 列出日历、查看事件、创建/更新/删除日历事件、检查空闲时间
|
||||
- **触发词:** "查看日历"、"安排会议"、"我今天有什么安排"、"明天我有空吗"
|
||||
- **路径:** `~/.openclaw/skills/accli/SKILL.md`
|
||||
|
||||
---
|
||||
|
||||
## ☁️ 云服务与协作
|
||||
|
||||
### 5. gog
|
||||
- **描述:** Google Workspace CLI
|
||||
- **用途:** Gmail、日历、云盘、联系人、表格、文档
|
||||
- **路径:** `~/.agents/skills/gog/SKILL.md`
|
||||
|
||||
### 6. feishu-chat-history
|
||||
- **描述:** 获取飞书群聊历史
|
||||
- **用途:** 读取、回顾、总结飞书群聊消息
|
||||
- **触发词:** "看群聊记录"、"群里聊了啥"、"chat history"
|
||||
- **路径:** `~/.agents/skills/feishu-chat-history/SKILL.md`
|
||||
|
||||
### 7. feishu-cron-reminder
|
||||
- **描述:** 飞书定时提醒
|
||||
- **用途:** 创建定时发送消息到飞书聊天的cron任务
|
||||
- **触发词:** "飞书定时提醒"、"定时任务发飞书"、"每小时提醒"
|
||||
- **路径:** `~/.agents/skills/feishu-cron-reminder/SKILL.md`
|
||||
|
||||
### 8. feishu-doc
|
||||
- **描述:** 飞书文档获取
|
||||
- **用途:** 获取飞书Wiki、文档、表格、Bitable内容，自动转换为Markdown
|
||||
- **路径:** `~/.agents/skills/feishu-doc-1.2.7/SKILL.md`
|
||||
|
||||
### 9. feishu-perm
|
||||
- **描述:** 飞书权限管理
|
||||
- **用途:** 文档和文件的分享、权限、协作者管理
|
||||
- **触发词:** 分享、权限、协作者
|
||||
- **路径:** `~/.agents/skills/feishu-perm/SKILL.md`
|
||||
|
||||
### 10. feishu-screenshot
|
||||
- **描述:** 截屏并发送到飞书
|
||||
- **用途:** 截取屏幕并通过飞书分享
|
||||
- **触发词:** "截个屏发飞书"、"截屏"、"screenshot"
|
||||
- **路径:** `~/.agents/skills/feishu-screenshot/SKILL.md`
|
||||
|
||||
### 11. feishu-send-file
|
||||
- **描述:** 发送文件到飞书
|
||||
- **用途:** 通过REST API发送文件、附件到飞书群或个人
|
||||
- **触发词:** "发文件到飞书"、"send file to feishu"
|
||||
- **路径:** `~/.agents/skills/feishu-send-file/SKILL.md`
|
||||
|
||||
---
|
||||
|
||||
## 💬 通讯工具
|
||||
|
||||
### 12. slack
|
||||
- **描述:** Slack 控制
|
||||
- **用途:** 通过 slack 工具控制Slack，包括消息反应、pin/unpin
|
||||
- **路径:** `/opt/homebrew/lib/node_modules/openclaw/skills/slack/SKILL.md`
|
||||
|
||||
---
|
||||
|
||||
## 🌐 网络与浏览器
|
||||
|
||||
### 13. agent-browser
|
||||
- **描述:** 无头浏览器自动化CLI
|
||||
- **用途:** 为AI代理优化的浏览器自动化，支持无障碍树快照和基于引用的元素选择
|
||||
- **路径:** `~/.openclaw/skills/agent-browser-clawdbot/SKILL.md`
|
||||
|
||||
### 14. tavily-search
|
||||
- **描述:** Tavily 搜索API
|
||||
- **用途:** 网页搜索（替代Brave），返回相关结果标题、URL、摘要
|
||||
- **路径:** `~/.openclaw/skills/openclaw-tavily-search/SKILL.md`
|
||||
|
||||
---
|
||||
|
||||
## 🛠️ 开发工具
|
||||
|
||||
### 15. Docker
|
||||
- **描述:** Docker 容器、镜像、Compose、网络、卷、调试
|
||||
- **用途:** Docker相关操作、生产环境加固、命令保持稳定
|
||||
- **路径:** `~/.openclaw/skills/docker/SKILL.md`
|
||||
|
||||
### 16. Code
|
||||
- **描述:** 编码工作流
|
||||
- **用途:** 规划、实现、验证、测试的清洁软件开发流程
|
||||
- **路径:** `~/.agents/skills/code-1.0.4/SKILL.md`
|
||||
|
||||
### 17. git-essentials
|
||||
- **描述:** 基础Git命令
|
||||
- **用途:** 版本控制、分支、协作
|
||||
- **路径:** `~/.agents/skills/git-essentials-1.0.0/SKILL.md`
|
||||
|
||||
### 18. frontend-design
|
||||
- **描述:** 前端界面设计
|
||||
- **用途:** 创建独特、生产级的前端界面，高设计质量
|
||||
- **路径:** `~/.agents/skills/frontend-design-3-0.1.0/SKILL.md`
|
||||
|
||||
### 19. security-auditor
|
||||
- **描述:** 安全审计
|
||||
- **用途:** 代码安全漏洞审查、身份验证流程、OWASP Top 10审计、CORS/CSP配置、敏感数据处理、输入验证、SQL注入预防、XSS保护
|
||||
- **路径:** `~/.agents/skills/security-auditor-1.0.0/SKILL.md`
|
||||
|
||||
### 20. architecture-designer
|
||||
- **描述:** 系统架构设计
|
||||
- **用途:** 设计新系统架构、审查现有设计、架构决策、ADRs、可扩展性规划
|
||||
- **路径:** `~/.agents/skills/architecture-designer-0.1.0/SKILL.md`
|
||||
|
||||
### 21. supabase-postgres-best-practices
|
||||
- **描述:** Supabase Postgres 最佳实践
|
||||
- **用途:** Postgres性能优化和最佳实践
|
||||
- **路径:** `~/.agents/skills/supabase-postgres-best-practices/SKILL.md`
|
||||
|
||||
### 22. tmux
|
||||
- **描述:** Tmux 远程控制
|
||||
- **用途:** 远程控制tmux会话，发送按键和抓取面板输出
|
||||
- **路径:** `~/.agents/skills/tmux-1.0.0/SKILL.md`
|
||||
|
||||
---
|
||||
|
||||
## 📝 笔记与知识管理
|
||||
|
||||
### 23. obsidian
|
||||
- **描述:** Obsidian 保险库
|
||||
- **用途:** 处理Obsidian纯文本Markdown笔记，通过obsidian-cli自动化
|
||||
- **路径:** `/opt/homebrew/lib/node_modules/openclaw/skills/obsidian/SKILL.md`
|
||||
|
||||
### 24. ontology
|
||||
- **描述:** 知识图谱
|
||||
- **用途:** 结构化代理记忆和可组合技能，创建/查询实体（Person、Project、Task、Event、Document），链接相关对象，执行约束，多步骤动作规划
|
||||
- **触发词:** "记住"、"关于X我知道什么"、"链接X到Y"、"显示依赖"
|
||||
- **路径:** `~/.agents/skills/ontology/SKILL.md`
|
||||
|
||||
### 25. Memory
|
||||
- **描述:** 无限有序记忆
|
||||
- **用途:** 补充代理内置记忆的无限分类存储
|
||||
- **路径:** `~/.agents/skills/memory-1.0.2/SKILL.md`
|
||||
|
||||
### 26. obsidian-ontology-sync
|
||||
- **描述:** Obsidian与 Ontology 双向同步
|
||||
- **用途:** 从markdown自动提取实体和关系，维护本体图谱，提供反馈改进笔记结构
|
||||
- **路径:** `~/.agents/skills/obsidian-ontology-sync-1.0.1/SKILL.md`
|
||||
|
||||
---
|
||||
|
||||
## 🎨 内容创作
|
||||
|
||||
### 27. blog-writer
|
||||
- **描述:** 博客文章写作
|
||||
- **用途:** 以作家独特风格写博客文章、长篇内容，从研究到Notion发布的完整工作流
|
||||
- **路径:** `~/.agents/skills/blog-writer-0.1.0/SKILL.md`
|
||||
|
||||
### 28. copywriting
|
||||
- **描述:** 文案写作
|
||||
- **用途:** 为落地页、邮件、广告、销售页、营销材料写 persuasive copy，标题、CTA、产品描述、广告文案、邮件序列
|
||||
- **触发词:** "写文案"、"copywriting"、"landing page copy"、"headline"
|
||||
- **路径:** `~/.agents/skills/copywriting-0.1.0/SKILL.md`
|
||||
|
||||
### 29. content-strategy
|
||||
- **描述:** 内容营销策略
|
||||
- **用途:** 为solopreneur业务构建和执行内容营销策略
|
||||
- **触发词:** "内容策略"、"content marketing"、"内容计划"、"内容日历"
|
||||
- **路径:** `~/.agents/skills/content-strategy-0.1.0/SKILL.md`
|
||||
|
||||
### 30. seo-content-writer
|
||||
- **描述:** SEO内容写作
|
||||
- **用途:** 写SEO优化内容、创建博客文章、文章
|
||||
- **触发词:** "写SEO内容"、"创建博客文章"、"内容写作"
|
||||
- **路径:** `~/.agents/skills/seo-content-writer-2.0.0/SKILL.md`
|
||||
|
||||
### 31. social-content
|
||||
- **描述:** 社交媒体内容
|
||||
- **用途:** 创建、安排、优化LinkedIn、Twitter/X、Instagram、TikTok、Facebook等内容
|
||||
- **触发词:** "LinkedIn post"、"Twitter thread"、"社交媒体"、"内容日历"
|
||||
- **路径:** `~/.agents/skills/social-content-generator-0.1.0/SKILL.md`
|
||||
|
||||
### 32. Social Media Scheduler
|
||||
- **描述:** 社交媒体排程
|
||||
- **用途:** 计划、起草、跨平台组织社交媒体内容，创建内容日历
|
||||
- **路径:** `~/.agents/skills/social-media-scheduler-1.0.0/SKILL.md`
|
||||
|
||||
### 33. research-paper-writer
|
||||
- **描述:** 研究论文写作
|
||||
- **用途:** 创建遵循IEEE/ACM格式标准的正式学术论文
|
||||
- **路径:** `~/.agents/skills/research-paper-writer-0.1.0/SKILL.md`
|
||||
|
||||
### 34. Powerpoint / PPTX
|
||||
- **描述:** PowerPoint 演示文稿
|
||||
- **用途:** 创建、检查、编辑Microsoft PowerPoint演示文稿，可靠的布局、模板、占位符、笔记、图表
|
||||
- **路径:** `~/.openclaw/skills/powerpoint-pptx/SKILL.md`
|
||||
|
||||
---
|
||||
|
||||
## 📊 商业与分析
|
||||
|
||||
### 35. Market Research
|
||||
- **描述:** 市场研究
|
||||
- **用途:** 规模市场、分析竞争对手、用实际框架和数据源验证机会
|
||||
- **路径:** `~/.agents/skills/market-research-1.0.0/SKILL.md`
|
||||
|
||||
### 36. interview-designer
|
||||
- **描述:** 面试设计
|
||||
- **用途:** 分析简历，使用基于证据的方法设计面试策略
|
||||
- **路径:** `~/.agents/skills/interview-designer-1.0.0/SKILL.md`
|
||||
|
||||
### 37. backtest-expert
|
||||
- **描述:** 回测专家
|
||||
- **用途:** 系统交易策略回测的专家指导
|
||||
- **触发词:** 回测、策略验证、鲁棒性测试、避免过度拟合
|
||||
- **路径:** `~/.agents/skills/backtest-expert-0.1.0/SKILL.md`
|
||||
|
||||
### 38. automation-workflows
|
||||
- **描述:** 自动化工作流
|
||||
- **用途:** 设计和实施自动化工作流以节省时间和扩展运营
|
||||
- **触发词:** "自动化"、"automation workflow"、"save time"、"reduce manual work"
|
||||
- **路径:** `~/.agents/skills/automation-workflows-0.1.0/SKILL.md`
|
||||
|
||||
---
|
||||
|
||||
## 🧠 AI 代理能力
|
||||
|
||||
### 39. proactive-agent-lite
|
||||
- **描述:** 主动代理Lite
|
||||
- **用途:** 将AI代理从任务追随者转变为积极主动的伙伴，具有记忆架构、reverse prompting和自愈模式
|
||||
- **路径:** `~/.openclaw/skills/proactive-agent-lite/SKILL.md`
|
||||
|
||||
### 40. self-improvement
|
||||
- **描述:** 自我改进
|
||||
- **用途:** 捕获学习、错误、纠正以实现持续改进
|
||||
- **触发词:** 命令/操作失败、用户纠正、请求不存在的功能、外部API失败、知识过时
|
||||
- **路径:** `~/.openclaw/skills/self-improving-agent/SKILL.md`
|
||||
|
||||
### 41. self-reflection
|
||||
- **描述:** 自我反思
|
||||
- **用途:** 定期自我反思，分析近期会话，写简洁可行的见解
|
||||
- **路径:** `~/.agents/skills/agent-self-reflection-1.0.0/SKILL.md`
|
||||
|
||||
### 42. brainstorming
|
||||
- **描述:** 头脑风暴
|
||||
- **用途:** 在任何创造性工作之前必须使用 - 创建功能、构建组件、添加功能或修改行为
|
||||
- **路径:** `~/.agents/skills/brainstorming-0.1.0/SKILL.md`
|
||||
|
||||
### 43. writing-plans
|
||||
- **描述:** 写作计划
|
||||
- **用途:** 有规范/需求的多步骤任务规范
|
||||
- **路径:** `~/.agents/skills/writing-plans-0.1.0/SKILL.md`
|
||||
|
||||
### 44. executing-plans
|
||||
- **描述:** 执行计划
|
||||
- **用途:** 在单独会话中执行包含审查检查点的书面实施计划
|
||||
- **路径:** `~/.agents/skills/executing-plans-0.1.0/SKILL.md`
|
||||
|
||||
### 45. task-summary
|
||||
- **描述:** 任务总结
|
||||
- **用途:** 任务完成后生成结构化总结，记录目标、步骤、结果、经验教训
|
||||
- **路径:** `~/.openclaw/skills/task-summary/SKILL.md`
|
||||
|
||||
---
|
||||
|
||||
## 🔧 工具与系统
|
||||
|
||||
### 46. clawhub
|
||||
- **描述:** ClawHub CLI
|
||||
- **用途:** 从clawhub.com搜索、安装、更新、发布代理技能
|
||||
- **路径:** `/opt/homebrew/lib/node_modules/openclaw/skills/clawhub/SKILL.md`
|
||||
|
||||
### 47. find-skills
|
||||
- **描述:** 发现技能
|
||||
- **用途:** 当用户询问"如何做X"、"找X的技能"、"有能...的技能吗"时帮助用户发现和安装技能
|
||||
- **路径:** `~/.agents/skills/find-skills/SKILL.md`
|
||||
|
||||
### 48. skill-creator
|
||||
- **描述:** 技能创建器
|
||||
- **用途:** 创建有效技能的指南
|
||||
- **路径:** `~/.agents/skills/skill-creator-0.1.0/SKILL.md`
|
||||
|
||||
### 49. skill-vetter
|
||||
- **描述:** 技能审核
|
||||
- **用途:** AI代理的安全优先技能审核，安装来自ClawHub、GitHub或其他来源的技能之前检查
|
||||
- **路径:** `~/.agents/skills/skill-vetter-1.0.0/SKILL.md`
|
||||
|
||||
### 50. clawdefender
|
||||
- **描述:** 安全防御
|
||||
- **用途:** AI代理的安全扫描器和输入清理器，检测prompt注入、命令注入、SSRF、凭证外泄、路径遍历攻击
|
||||
- **路径:** `~/.agents/skills/clawdefender-1/SKILL.md`
|
||||
|
||||
### 51. opencode-controller
|
||||
- **描述:** Opencode 控制器
|
||||
- **用途:** 通过斜杠命令控制Opencode，管理会话、选择模型、切换代理
|
||||
- **路径:** `~/.agents/skills/opencode-controller-1.0.0/SKILL.md`
|
||||
|
||||
---
|
||||
|
||||
## 🌤️ 生活与娱乐
|
||||
|
||||
### 52. weather
|
||||
- **描述:** 天气
|
||||
- **用途:** 通过wttr.in或Open-Meteo获取当前天气和预报
|
||||
- **触发词:** 天气、温度、预报
|
||||
- **路径:** `/opt/homebrew/lib/node_modules/openclaw/skills/weather/SKILL.md`
|
||||
|
||||
### 53. video-frames
|
||||
- **描述:** 视频帧提取
|
||||
- **用途:** 使用ffmpeg从视频提取帧或短片段
|
||||
- **路径:** `~/.agents/skills/video-frames-1.0.0/SKILL.md`
|
||||
|
||||
### 54. FFmpeg Video Editor
|
||||
- **描述:** FFmpeg 视频编辑器
|
||||
- **用途:** 从自然语言视频编辑请求生成FFmpeg命令 - 剪切、裁剪、转换、压缩、改变宽高比、提取音频等
|
||||
- **路径:** `~/.agents/skills/ffmpeg-video-editor-1.0.0/SKILL.md`
|
||||
|
||||
### 55. UI/UX Pro Max
|
||||
- **描述:** UI/UX 设计
|
||||
- **用途:** UI/UX设计智能和实现指导，构建精美界面
|
||||
- **路径:** `~/.agents/skills/ui-ux-pro-max-0.1.0/SKILL.md`
|
||||
|
||||
---
|
||||
|
||||
## 🛡️ 系统与运维
|
||||
|
||||
### 56. healthcheck
|
||||
- **描述:** 主机安全检查
|
||||
- **用途:** 主机安全加固和风险容忍配置
|
||||
- **触发词:** 安全审计、防火墙/SSH/更新加固、风险态势、暴露审查、OpenClaw cron调度
|
||||
- **路径:** `/opt/homebrew/lib/node_modules/openclaw/skills/healthcheck/SKILL.md`
|
||||
|
||||
### 57. node-connect
|
||||
- **描述:** OpenClaw 节点连接
|
||||
- **用途:** 诊断Android、iOS、macOS companion app的配对失败
|
||||
- **触发词:** QR/设置码手动连接失败、本地Wi-Fi正常但VPS/tailnet不正常、配对要求、未经授权、bootstrap token无效/过期
|
||||
- **路径:** `/opt/homebrew/lib/node_modules/openclaw/skills/node-connect/SKILL.md`
|
||||
|
||||
---
|
||||
|
||||
## 📊 技能分类汇总
|
||||
|
||||
| 分类 | 数量 | 技能 |
|
||||
|------|------|------|
|
||||
| Apple 生态 | 3 | apple-notes, apple-reminders, accli |
|
||||
| 云服务/协作 | 7 | gog, feishu-*(6个) |
|
||||
| 通讯工具 | 1 | slack |
|
||||
| 网络/浏览器 | 2 | agent-browser, tavily-search |
|
||||
| 开发工具 | 8 | Docker, Code, git-essentials, frontend-design, security-auditor, architecture-designer, supabase-postgres-best-practices, tmux |
|
||||
| 笔记/知识管理 | 5 | obsidian, ontology, Memory, obsidian-ontology-sync, task-summary |
|
||||
| 内容创作 | 8 | blog-writer, copywriting, content-strategy, seo-content-writer, social-content, Social Media Scheduler, research-paper-writer, Powerpoint/PPTX |
|
||||
| 商业/分析 | 4 | Market Research, interview-designer, backtest-expert, automation-workflows |
|
||||
| AI代理能力 | 7 | proactive-agent-lite, self-improvement, self-reflection, brainstorming, writing-plans, executing-plans, task-summary |
|
||||
| 工具/系统 | 6 | clawhub, find-skills, skill-creator, skill-vetter, clawdefender, opencode-controller |
|
||||
| 生活/娱乐 | 4 | weather, video-frames, FFmpeg Video Editor, UI/UX Pro Max |
|
||||
| 系统/运维 | 2 | healthcheck, node-connect |
|
||||
|
||||
**总计: 57 个技能**
|
||||
|
||||
---
|
||||
|
||||
*笔记创建于 2026-03-19 by 星辉*
|
||||
|
||||
@@ -1,421 +1,421 @@
|
||||
---
|
||||
title: 查找进程
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: [install, openclaw, ubuntu, uninstall]
|
||||
---
|
||||
|
||||
|
||||
#ubuntu #openclaw #install #uninstall
|
||||
|
||||
```table-of-contents
|
||||
```
|
||||
|
||||
## 环境概述
|
||||
|
||||
- 系统：Ubuntu 20.04 / 22.04
|
||||
- OpenClaw 安装方式：npm 用户本地全局安装openclaw & clawhub (注意不要用root user安装)
|
||||
```
|
||||
npm install -g openclaw clawhub
|
||||
```
|
||||
- 用户路径示例：
|
||||
|
||||
```bash
|
||||
/home/shenwei/.npm-global/bin/openclaw
|
||||
```
|
||||
|
||||
- 默认配置目录：
|
||||
```bash
|
||||
/home/shenwei/.openclaw
|
||||
```
|
||||
|
||||
- 用户级 systemd 服务目录：
|
||||
```bash
|
||||
/home/shenwei/.config/systemd/user/openclaw-gateway.service
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 卸载旧版本 OpenClaw
|
||||
|
||||
1. **停止正在运行的进程 / 服务**
|
||||
```bash
|
||||
# 查找进程
|
||||
ps aux | grep openclaw
|
||||
|
||||
# 如果有 systemd 用户服务
|
||||
systemctl --user stop openclaw
|
||||
systemctl --user disable openclaw
|
||||
```
|
||||
|
||||
2. **卸载 npm 安装的 OpenClaw**
|
||||
```bash
|
||||
# 全局卸载
|
||||
sudo npm uninstall -g openclaw clawhub
|
||||
|
||||
# 或者局部卸载
|
||||
npm uninstall openclaw clawhub
|
||||
```
|
||||
|
||||
3. **删除用户配置目录**
|
||||
```bash
|
||||
rm -rf /home/shenwei/.openclaw # 普通用户
|
||||
sudo rm -rf /root/.openclaw # root 用户（如果曾用 sudo 运行）
|
||||
sudo rm -rf /opt/openclaw # 如果之前手动统一过目录
|
||||
```
|
||||
|
||||
4. **清理残留 npm 包**
|
||||
```bash
|
||||
npm list -g --depth=0 | grep openclaw
|
||||
npm list -g --depth=0 | grep clawhub
|
||||
```
|
||||
如有残留再执行 `npm uninstall -g <package>`。
|
||||
|
||||
---
|
||||
|
||||
## 安装 OpenClaw
|
||||
|
||||
### 方法 A：通过 npm 安装（推荐）
|
||||
#### 全局安装
|
||||
```
|
||||
sudo npm install -g npm
|
||||
sudo npm install -g openclaw clawhub
|
||||
```
|
||||
- 建议使用最新版 Node.js（至少 18+），避免依赖报错。
|
||||
|
||||
#### 非全局安装
|
||||
- 如果你希望不使用 `sudo` 全局安装，可以配置 npm 全局目录在用户目录：
|
||||
``` bash
|
||||
mkdir -p ~/.npm-global
|
||||
npm config set prefix '~/.npm-global'
|
||||
export PATH="$HOME/.npm-global/bin:$PATH"
|
||||
```
|
||||
|
||||
然后再执行：
|
||||
``` bash
|
||||
# 确保 npm 更新
|
||||
npm install -g npm
|
||||
|
||||
# 全局安装 OpenClaw
|
||||
npm install -g openclaw clawhub
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 配置 PATH，让 OpenClaw 在任意位置可执行
|
||||
|
||||
1. 临时生效（仅当前终端）：
|
||||
```bash
|
||||
export PATH=$HOME/.npm-global/bin:$PATH
|
||||
```
|
||||
|
||||
2. 永久生效（推荐）：
|
||||
- 编辑 shell 配置文件 `~/.bashrc` 或 `~/.zshrc`，添加：
|
||||
```bash
|
||||
export PATH=$HOME/.npm-global/bin:$PATH
|
||||
```
|
||||
|
||||
- 刷新配置：
|
||||
```bash
|
||||
source ~/.bashrc # bash
|
||||
source ~/.zshrc # zsh
|
||||
```
|
||||
|
||||
- 验证：
|
||||
```bash
|
||||
which openclaw
|
||||
openclaw --version
|
||||
```
|
||||
---
|
||||
|
||||
## 用户级 systemd 服务管理（OpenClaw Gateway）
|
||||
|
||||
安装 Gateway 后会生成服务文件：
|
||||
```bash
|
||||
/home/shenwei/.config/systemd/user/openclaw-gateway.service
|
||||
```
|
||||
|
||||
``` bash
|
||||
[Unit]
|
||||
Description=OpenClaw Gateway (v2026.3.13)
|
||||
After=network-online.target
|
||||
Wants=network-online.target
|
||||
|
||||
[Service]
|
||||
ExecStart=/usr/bin/node /home/shenwei/.npm-global/lib/node_modules/openclaw/dist/index.js gateway --port 18789
|
||||
Restart=always
|
||||
RestartSec=5
|
||||
TimeoutStopSec=30
|
||||
TimeoutStartSec=30
|
||||
SuccessExitStatus=0 143
|
||||
KillMode=control-group
|
||||
Environment=HOME=/home/shenwei
|
||||
Environment=TMPDIR=/tmp
|
||||
Environment=HTTP_PROXY=http://127.0.0.1:10808
|
||||
Environment=HTTPS_PROXY=http://127.0.0.1:10808
|
||||
Environment=PATH=/home/shenwei/.local/bin:/home/shenwei/.npm-global/bin:/home/shenwei/bin:/home/shenwei/.volta/bin:/home/shenwei/.asdf/shims:/home/shenwei/.bun/bin:/>
|
||||
Environment=OPENCLAW_GATEWAY_PORT=18789
|
||||
Environment=OPENCLAW_SYSTEMD_UNIT=openclaw-gateway.service
|
||||
Environment="OPENCLAW_WINDOWS_TASK_NAME=OpenClaw Gateway"
|
||||
Environment=OPENCLAW_SERVICE_MARKER=openclaw
|
||||
Environment=OPENCLAW_SERVICE_KIND=gateway
|
||||
Environment=OPENCLAW_SERVICE_VERSION=2026.3.13
|
||||
|
||||
[Install]
|
||||
WantedBy=default.target
|
||||
|
||||
```
|
||||
|
||||
查看日志
|
||||
```
|
||||
|
||||
# 查看最近 50 行
|
||||
journalctl --user -u openclaw-gateway -n 50 --no-pager
|
||||
|
||||
# 实时跟踪日志
|
||||
journalctl --user -u openclaw-gateway -f
|
||||
|
||||
# 查看今天的所有日志
|
||||
journalctl --user -u openclaw-gateway --since today
|
||||
```
|
||||
|
||||
|
||||
### 常用管理命令
|
||||
|
||||
| 操作 | 命令 |
|
||||
| --------------------------- | ------------------------------------------- |
|
||||
| 启动 Gateway | `systemctl --user start openclaw-gateway` |
|
||||
| 停止 Gateway | `systemctl --user stop openclaw-gateway` |
|
||||
| 重启 Gateway | `systemctl --user restart openclaw-gateway` |
|
||||
| 查看状态 | `systemctl --user status openclaw-gateway` |
|
||||
| 开机自启 | `systemctl --user enable openclaw-gateway` |
|
||||
| 取消开机自启 | `systemctl --user disable openclaw-gateway` |
|
||||
| 刷新 systemd 配置（修改 service 后） | `systemctl --user daemon-reload` |
|
||||
|
||||
|
||||
> ⚠️ 用户级服务不需要 sudo，安全且方便。
|
||||
|
||||
---
|
||||
|
||||
## 多用户环境与避免重复环境
|
||||
|
||||
- OpenClaw 配置目录默认跟随 `$HOME`：
|
||||
|
||||
|用户|配置目录|
|
||||
|---|---|
|
||||
|shenwei|`/home/shenwei/.openclaw`|
|
||||
|root|`/root/.openclaw`|
|
||||
|
||||
- **原因**：Linux 用户隔离机制，不同用户运行 OpenClaw 会生成独立目录。
|
||||
- **注意**：
|
||||
|
||||
- 不要用 root 启动 OpenClaw，避免权限混乱
|
||||
- 统一使用普通用户安装和运行
|
||||
- 可通过 `--workdir /opt/openclaw` 指定统一目录
|
||||
|
||||
|
||||
---
|
||||
|
||||
## 常用命令总结
|
||||
|
||||
| 命令 | 功能 |
|
||||
| --------------------------------------------------------------------- | ------------- |
|
||||
| `openclaw onboard` | 初始化新环境、设置工作目录 |
|
||||
| `openclaw --version` | 查看版本 |
|
||||
| `openclaw agent list` | 列出所有 agent |
|
||||
| `openclaw agent create --name <agent_name> --message "<description>"` | 创建新的 agent |
|
||||
| `openclaw agent delete <agent_name>` | 删除 agent |
|
||||
| `openclaw skill install <skill_name>` | 安装技能 |
|
||||
| `openclaw skill update <skill_name>` | 更新技能 |
|
||||
| `openclaw skill list` | 查看已安装技能 |
|
||||
| `openclaw memory list` | 查看记忆数据 |
|
||||
| `openclaw workspace list` | 查看工作空间 |
|
||||
| | |
|
||||
| | |
|
||||
|
||||
---
|
||||
|
||||
## 创建 Agent 与绑定 Telegram Bot
|
||||
|
||||
1. **创建 agent**
|
||||
```
|
||||
openclaw agents add <agentname> --non-interactive --workspace /home/shenwei/.openclaw/workspace-agent-<agentname> --model MiniMax-M2.5
|
||||
|
||||
```
|
||||
举例：
|
||||
```bash
|
||||
openclaw agents add yunce --non-interactive --workspace /home/shenwei/.openclaw/workspace-agent-yunce --model MiniMax-M2.5
|
||||
```
|
||||
|
||||
2. **添加Telegram 账号**
|
||||
```
|
||||
# 添加 Telegram 账号
|
||||
openclaw channels add --channel telegram --account <账号名> --token <BotToken>
|
||||
```
|
||||
举例
|
||||
```
|
||||
openclaw channels add --channel telegram --account yunhan --token 8588117769:AAFxswhHgCdBor2EOa-2oChDpI-DADRt0tQ
|
||||
```
|
||||
3. **查看 agent 列表**
|
||||
```bash
|
||||
openclaw agents list
|
||||
```
|
||||
|
||||
3. **绑定 Bot**
|
||||
```
|
||||
# 绑定 agent 到 Telegram 账号
|
||||
openclaw agents bind --agent <agent_id> --bind telegram:<account_name>
|
||||
|
||||
```
|
||||
举例
|
||||
```
|
||||
openclaw agents bind --agent yunhan --bind telegram:yunhan
|
||||
```
|
||||
|
||||
- 配置完成后重启 Gateway：
|
||||
```bash
|
||||
systemctl --user restart openclaw-gateway
|
||||
```
|
||||
|
||||
- Telegram 多 Agent 建议：
|
||||
|
||||
- 一个 bot → n8n 路由 → 多 agent
|
||||
- 避免每个 agent 都创建独立 bot（每个账号最多 20 个 bot）
|
||||
- 用命令或路径路由区分不同 agent 功能
|
||||
|
||||
---
|
||||
|
||||
## 删除Agent
|
||||
1. **删除 agent**
|
||||
```
|
||||
openclaw agents delete <agent_name> --force
|
||||
```
|
||||
2. **删除bot**
|
||||
```
|
||||
# 删除 Telegram 账号
|
||||
openclaw channels remove --channel telegram --account <account_name> --delete
|
||||
```
|
||||
|
||||
## 注意事项与避免的坑
|
||||
|
||||
1. **避免使用 root 运行**
|
||||
- root 会生成 `/root/.openclaw`，和普通用户环境冲突
|
||||
- 权限问题可能导致 agent 无法访问工作空间
|
||||
2. **避免重复 PATH 或多版本冲突**
|
||||
- 如果 npm 本地 bin 不在 PATH，会导致命令找不到
|
||||
- 如果 PATH 里还有旧版本系统全局安装路径，可能会调用错误版本
|
||||
3. **用户级 systemd 服务管理**
|
||||
- 修改 service 后必须执行 `systemctl --user daemon-reload`
|
||||
- 避免 sudo 启动服务，保证文件权限正确
|
||||
4. **Telegram Bot 限制**
|
||||
- 每个账号最多创建 20 个 bot（Premium 账号可能 40 个）
|
||||
- 多 agent 架构建议一个 bot → n8n → 多 agent 路由
|
||||
5. **统一工作目录**
|
||||
- 推荐 `/home/shenwei/.openclaw` 或 `/opt/openclaw`
|
||||
- 方便多服务器或多 agent 管理
|
||||
6. **升级和维护**
|
||||
- 升级前先备份 `.openclaw` 下的 workspace、skills、memory
|
||||
- 使用 npm 全局安装可直接 `npm install -g openclaw@latest`
|
||||
|
||||
---
|
||||
## 卸载全局安装的 OpenClaw 和 ClawHub
|
||||
|
||||
在终端执行：
|
||||
|
||||
sudo npm uninstall -g openclaw clawhub
|
||||
|
||||
- `-g` 表示全局卸载。
|
||||
- `sudo` 是必要的，如果你全局安装需要管理员权限。
|
||||
|
||||
确认卸载：
|
||||
|
||||
npm list -g --depth=0
|
||||
|
||||
- 看列表里是否还存在 `openclaw` 或 `clawhub`。
|
||||
- 如果还在，可以尝试清理 npm 缓存（防止残留）：
|
||||
|
||||
npm cache clean --force
|
||||
|
||||
---
|
||||
|
||||
## 清理残留配置文件（可选）
|
||||
|
||||
OpenClaw 可能在你的用户目录生成配置文件或缓存，例如：
|
||||
|
||||
rm -rf ~/.openclaw
|
||||
rm -rf ~/.clawhub
|
||||
|
||||
这样可以保证重装是全新的环境。
|
||||
|
||||
### 参考架构示意
|
||||
|
||||
```
|
||||
Telegram Bot
|
||||
↓
|
||||
n8n Router
|
||||
↓
|
||||
OpenClaw Agents
|
||||
├─ 星枢（调度）
|
||||
├─ 星曜（IT管家）
|
||||
├─ 星辉（个人助理）
|
||||
└─ 云瀚（监控）
|
||||
```
|
||||
|
||||
|
||||
### Bot & Agent 命名
|
||||
|
||||
#### 星
|
||||
|
||||
```
|
||||
openclaw channels add --channel telegram --account xingshu --token 8787024183:AAG1M5tfSHj6Z0gMv3vvCZel2FOIX-0x8ZI
|
||||
|
||||
openclaw channels add --channel telegram --account xingyao --token 8414432613:AAG9hvKfILGSsbc1EMEZW1QVym9Quc5aHWk
|
||||
|
||||
openclaw channels add --channel telegram --account xinghui --token 8709222939:AAEfvZrvvU5vZFsmacsR5nmpkJ2Jb5JgfRg
|
||||
|
||||
```
|
||||
|
||||
| 服务器 | 角色 | Bot Name | Bot Key | Agent Id | Telegram User ID |
|
||||
| ------- | --- | ---------------------------- | ---------------------------------------------- | -------- | ---------------- |
|
||||
| macmini | 星枢 | @shenwei_macmini_xingshu_bot | 8787024183:AAG1M5tfSHj6Z0gMv3vvCZel2FOIX-0x8ZI | main | 5038825565 |
|
||||
| macmini | 星曜 | @shenwei_macmini_xingyao_bot | 8414432613:AAG9hvKfILGSsbc1EMEZW1QVym9Quc5aHWk | xingyao | 5038825565 |
|
||||
| macmini | 星辉 | @shenwei_macmini_xinghui_bot | 8709222939:AAEfvZrvvU5vZFsmacsR5nmpkJ2Jb5JgfRg | xinghui | 5038825565 |
|
||||
| | | | | | |
|
||||
#### 云
|
||||
|
||||
```
|
||||
openclaw channels add --channel telegram --account yunhan --token 8588117769:AAFxswhHgCdBor2EOa-2oChDpI-DADRt0tQ
|
||||
|
||||
openclaw channels add --channel telegram --account yunce --token 8791231082:AAFKPfTPy3LshybWUJ0joBkz3Th3mwYQOnc
|
||||
|
||||
openclaw channels add --channel telegram --account yunjiang --token 8727937702:AAGw3WGPI1j5rSD97wap6h9EGqVpDEMdjLU
|
||||
|
||||
openclaw channels add --channel telegram --account yunzhi --token 8639619464:AAEI35Dnt-9PQ8y4Du_ToxVhwUBUa5kpLjU
|
||||
```
|
||||
|
||||
| 服务器 | 角色 | Bot Name | Bot Key | Agent 名称 | Telegram User ID |
|
||||
| ------- | --- | ----------------------------- | ---------------------------------------------- | -------- | ---------------- |
|
||||
| ubuntu2 | 云瀚 | @shenwei_ubuntu2_yunhan_bot | 8588117769:AAFxswhHgCdBor2EOa-2oChDpI-DADRt0tQ | yunhan | 5038825565 |
|
||||
| ubuntu2 | 云策 | @shenwei_ubuntu2_yunce_bot | 8791231082:AAFKPfTPy3LshybWUJ0joBkz3Th3mwYQOnc | yunce | 5038825565 |
|
||||
| ubuntu2 | 云匠 | @shenwei_ubuntu2_yunjiang_bot | 8727937702:AAGw3WGPI1j5rSD97wap6h9EGqVpDEMdjLU | yunjiang | 5038825565 |
|
||||
| ubuntu2 | 云织 | @shenwei_ubuntu2_yunzhi_bot | 8639619464:AAEI35Dnt-9PQ8y4Du_ToxVhwUBUa5kpLjU | yunzhi | 5038825565 |
|
||||
|
||||
|
||||
#### 风
|
||||
|
||||
```
|
||||
openclaw channels add --channel telegram --account fengheng --token
|
||||
|
||||
openclaw channels add --channel telegram --account fengchi --token 8696785331:AAEjtl6duODUtjxC8DSCrUsJx5awUZVMkD8
|
||||
|
||||
openclaw channels add --channel telegram --account fengji --token
|
||||
```
|
||||
|
||||
| 服务器 | 角色 | Bot Name | Bot Key | Agent 名称 | Telegram User ID |
|
||||
| ------- | --- | ----------------------------- | ------- | -------- | ---------------- |
|
||||
| ubuntu1 | 风衡 | @shenwei_ubuntu1_fengheng_bot | | fengheng | 5038825565 |
|
||||
| ubuntu1 | 风驰 | @shenwei_ubuntu1_fengchi_bot | | fengchi | 5038825565 |
|
||||
| ubuntu1 | 风纪 | @shenwei_ubuntu1_fengji_bot | | fengji | 5038825565 |
|
||||
---
|
||||
title: 查找进程
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: [install, openclaw, ubuntu, uninstall]
|
||||
---
|
||||
|
||||
|
||||
#ubuntu #openclaw #install #uninstall
|
||||
|
||||
```table-of-contents
|
||||
```
|
||||
|
||||
## 环境概述
|
||||
|
||||
- 系统：Ubuntu 20.04 / 22.04
|
||||
- OpenClaw 安装方式：npm 用户本地全局安装openclaw & clawhub (注意不要用root user安装)
|
||||
```
|
||||
npm install -g openclaw clawhub
|
||||
```
|
||||
- 用户路径示例：
|
||||
|
||||
```bash
|
||||
/home/shenwei/.npm-global/bin/openclaw
|
||||
```
|
||||
|
||||
- 默认配置目录：
|
||||
```bash
|
||||
/home/shenwei/.openclaw
|
||||
```
|
||||
|
||||
- 用户级 systemd 服务目录：
|
||||
```bash
|
||||
/home/shenwei/.config/systemd/user/openclaw-gateway.service
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 卸载旧版本 OpenClaw
|
||||
|
||||
1. **停止正在运行的进程 / 服务**
|
||||
```bash
|
||||
# 查找进程
|
||||
ps aux | grep openclaw
|
||||
|
||||
# 如果有 systemd 用户服务
|
||||
systemctl --user stop openclaw
|
||||
systemctl --user disable openclaw
|
||||
```
|
||||
|
||||
2. **卸载 npm 安装的 OpenClaw**
|
||||
```bash
|
||||
# 全局卸载
|
||||
sudo npm uninstall -g openclaw clawhub
|
||||
|
||||
# 或者局部卸载
|
||||
npm uninstall openclaw clawhub
|
||||
```
|
||||
|
||||
3. **删除用户配置目录**
|
||||
```bash
|
||||
rm -rf /home/shenwei/.openclaw # 普通用户
|
||||
sudo rm -rf /root/.openclaw # root 用户（如果曾用 sudo 运行）
|
||||
sudo rm -rf /opt/openclaw # 如果之前手动统一过目录
|
||||
```
|
||||
|
||||
4. **清理残留 npm 包**
|
||||
```bash
|
||||
npm list -g --depth=0 | grep openclaw
|
||||
npm list -g --depth=0 | grep clawhub
|
||||
```
|
||||
如有残留再执行 `npm uninstall -g <package>`。
|
||||
|
||||
---
|
||||
|
||||
## 安装 OpenClaw
|
||||
|
||||
### 方法 A：通过 npm 安装（推荐）
|
||||
#### 全局安装
|
||||
```
|
||||
sudo npm install -g npm
|
||||
sudo npm install -g openclaw clawhub
|
||||
```
|
||||
- 建议使用最新版 Node.js（至少 18+），避免依赖报错。
|
||||
|
||||
#### 非全局安装
|
||||
- 如果你希望不使用 `sudo` 全局安装，可以配置 npm 全局目录在用户目录：
|
||||
``` bash
|
||||
mkdir -p ~/.npm-global
|
||||
npm config set prefix '~/.npm-global'
|
||||
export PATH="$HOME/.npm-global/bin:$PATH"
|
||||
```
|
||||
|
||||
然后再执行：
|
||||
``` bash
|
||||
# 确保 npm 更新
|
||||
npm install -g npm
|
||||
|
||||
# 全局安装 OpenClaw
|
||||
npm install -g openclaw clawhub
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 配置 PATH，让 OpenClaw 在任意位置可执行
|
||||
|
||||
1. 临时生效（仅当前终端）：
|
||||
```bash
|
||||
export PATH=$HOME/.npm-global/bin:$PATH
|
||||
```
|
||||
|
||||
2. 永久生效（推荐）：
|
||||
- 编辑 shell 配置文件 `~/.bashrc` 或 `~/.zshrc`，添加：
|
||||
```bash
|
||||
export PATH=$HOME/.npm-global/bin:$PATH
|
||||
```
|
||||
|
||||
- 刷新配置：
|
||||
```bash
|
||||
source ~/.bashrc # bash
|
||||
source ~/.zshrc # zsh
|
||||
```
|
||||
|
||||
- 验证：
|
||||
```bash
|
||||
which openclaw
|
||||
openclaw --version
|
||||
```
|
||||
---
|
||||
|
||||
## 用户级 systemd 服务管理（OpenClaw Gateway）
|
||||
|
||||
安装 Gateway 后会生成服务文件：
|
||||
```bash
|
||||
/home/shenwei/.config/systemd/user/openclaw-gateway.service
|
||||
```
|
||||
|
||||
``` bash
|
||||
[Unit]
|
||||
Description=OpenClaw Gateway (v2026.3.13)
|
||||
After=network-online.target
|
||||
Wants=network-online.target
|
||||
|
||||
[Service]
|
||||
ExecStart=/usr/bin/node /home/shenwei/.npm-global/lib/node_modules/openclaw/dist/index.js gateway --port 18789
|
||||
Restart=always
|
||||
RestartSec=5
|
||||
TimeoutStopSec=30
|
||||
TimeoutStartSec=30
|
||||
SuccessExitStatus=0 143
|
||||
KillMode=control-group
|
||||
Environment=HOME=/home/shenwei
|
||||
Environment=TMPDIR=/tmp
|
||||
Environment=HTTP_PROXY=http://127.0.0.1:10808
|
||||
Environment=HTTPS_PROXY=http://127.0.0.1:10808
|
||||
Environment=PATH=/home/shenwei/.local/bin:/home/shenwei/.npm-global/bin:/home/shenwei/bin:/home/shenwei/.volta/bin:/home/shenwei/.asdf/shims:/home/shenwei/.bun/bin:/>
|
||||
Environment=OPENCLAW_GATEWAY_PORT=18789
|
||||
Environment=OPENCLAW_SYSTEMD_UNIT=openclaw-gateway.service
|
||||
Environment="OPENCLAW_WINDOWS_TASK_NAME=OpenClaw Gateway"
|
||||
Environment=OPENCLAW_SERVICE_MARKER=openclaw
|
||||
Environment=OPENCLAW_SERVICE_KIND=gateway
|
||||
Environment=OPENCLAW_SERVICE_VERSION=2026.3.13
|
||||
|
||||
[Install]
|
||||
WantedBy=default.target
|
||||
|
||||
```
|
||||
|
||||
查看日志
|
||||
```
|
||||
|
||||
# 查看最近 50 行
|
||||
journalctl --user -u openclaw-gateway -n 50 --no-pager
|
||||
|
||||
# 实时跟踪日志
|
||||
journalctl --user -u openclaw-gateway -f
|
||||
|
||||
# 查看今天的所有日志
|
||||
journalctl --user -u openclaw-gateway --since today
|
||||
```
|
||||
|
||||
|
||||
### 常用管理命令
|
||||
|
||||
| 操作 | 命令 |
|
||||
| --------------------------- | ------------------------------------------- |
|
||||
| 启动 Gateway | `systemctl --user start openclaw-gateway` |
|
||||
| 停止 Gateway | `systemctl --user stop openclaw-gateway` |
|
||||
| 重启 Gateway | `systemctl --user restart openclaw-gateway` |
|
||||
| 查看状态 | `systemctl --user status openclaw-gateway` |
|
||||
| 开机自启 | `systemctl --user enable openclaw-gateway` |
|
||||
| 取消开机自启 | `systemctl --user disable openclaw-gateway` |
|
||||
| 刷新 systemd 配置（修改 service 后） | `systemctl --user daemon-reload` |
|
||||
|
||||
|
||||
> ⚠️ 用户级服务不需要 sudo，安全且方便。
|
||||
|
||||
---
|
||||
|
||||
## 多用户环境与避免重复环境
|
||||
|
||||
- OpenClaw 配置目录默认跟随 `$HOME`：
|
||||
|
||||
|用户|配置目录|
|
||||
|---|---|
|
||||
|shenwei|`/home/shenwei/.openclaw`|
|
||||
|root|`/root/.openclaw`|
|
||||
|
||||
- **原因**：Linux 用户隔离机制，不同用户运行 OpenClaw 会生成独立目录。
|
||||
- **注意**：
|
||||
|
||||
- 不要用 root 启动 OpenClaw，避免权限混乱
|
||||
- 统一使用普通用户安装和运行
|
||||
- 可通过 `--workdir /opt/openclaw` 指定统一目录
|
||||
|
||||
|
||||
---
|
||||
|
||||
## 常用命令总结
|
||||
|
||||
| 命令 | 功能 |
|
||||
| --------------------------------------------------------------------- | ------------- |
|
||||
| `openclaw onboard` | 初始化新环境、设置工作目录 |
|
||||
| `openclaw --version` | 查看版本 |
|
||||
| `openclaw agent list` | 列出所有 agent |
|
||||
| `openclaw agent create --name <agent_name> --message "<description>"` | 创建新的 agent |
|
||||
| `openclaw agent delete <agent_name>` | 删除 agent |
|
||||
| `openclaw skill install <skill_name>` | 安装技能 |
|
||||
| `openclaw skill update <skill_name>` | 更新技能 |
|
||||
| `openclaw skill list` | 查看已安装技能 |
|
||||
| `openclaw memory list` | 查看记忆数据 |
|
||||
| `openclaw workspace list` | 查看工作空间 |
|
||||
| | |
|
||||
| | |
|
||||
|
||||
---
|
||||
|
||||
## 创建 Agent 与绑定 Telegram Bot
|
||||
|
||||
1. **创建 agent**
|
||||
```
|
||||
openclaw agents add <agentname> --non-interactive --workspace /home/shenwei/.openclaw/workspace-agent-<agentname> --model MiniMax-M2.5
|
||||
|
||||
```
|
||||
举例：
|
||||
```bash
|
||||
openclaw agents add yunce --non-interactive --workspace /home/shenwei/.openclaw/workspace-agent-yunce --model MiniMax-M2.5
|
||||
```
|
||||
|
||||
2. **添加Telegram 账号**
|
||||
```
|
||||
# 添加 Telegram 账号
|
||||
openclaw channels add --channel telegram --account <账号名> --token <BotToken>
|
||||
```
|
||||
举例
|
||||
```
|
||||
openclaw channels add --channel telegram --account yunhan --token 8588117769:AAFxswhHgCdBor2EOa-2oChDpI-DADRt0tQ
|
||||
```
|
||||
3. **查看 agent 列表**
|
||||
```bash
|
||||
openclaw agents list
|
||||
```
|
||||
|
||||
3. **绑定 Bot**
|
||||
```
|
||||
# 绑定 agent 到 Telegram 账号
|
||||
openclaw agents bind --agent <agent_id> --bind telegram:<account_name>
|
||||
|
||||
```
|
||||
举例
|
||||
```
|
||||
openclaw agents bind --agent yunhan --bind telegram:yunhan
|
||||
```
|
||||
|
||||
- 配置完成后重启 Gateway：
|
||||
```bash
|
||||
systemctl --user restart openclaw-gateway
|
||||
```
|
||||
|
||||
- Telegram 多 Agent 建议：
|
||||
|
||||
- 一个 bot → n8n 路由 → 多 agent
|
||||
- 避免每个 agent 都创建独立 bot（每个账号最多 20 个 bot）
|
||||
- 用命令或路径路由区分不同 agent 功能
|
||||
|
||||
---
|
||||
|
||||
## 删除Agent
|
||||
1. **删除 agent**
|
||||
```
|
||||
openclaw agents delete <agent_name> --force
|
||||
```
|
||||
2. **删除bot**
|
||||
```
|
||||
# 删除 Telegram 账号
|
||||
openclaw channels remove --channel telegram --account <account_name> --delete
|
||||
```
|
||||
|
||||
## 注意事项与避免的坑
|
||||
|
||||
1. **避免使用 root 运行**
|
||||
- root 会生成 `/root/.openclaw`，和普通用户环境冲突
|
||||
- 权限问题可能导致 agent 无法访问工作空间
|
||||
2. **避免重复 PATH 或多版本冲突**
|
||||
- 如果 npm 本地 bin 不在 PATH，会导致命令找不到
|
||||
- 如果 PATH 里还有旧版本系统全局安装路径，可能会调用错误版本
|
||||
3. **用户级 systemd 服务管理**
|
||||
- 修改 service 后必须执行 `systemctl --user daemon-reload`
|
||||
- 避免 sudo 启动服务，保证文件权限正确
|
||||
4. **Telegram Bot 限制**
|
||||
- 每个账号最多创建 20 个 bot（Premium 账号可能 40 个）
|
||||
- 多 agent 架构建议一个 bot → n8n → 多 agent 路由
|
||||
5. **统一工作目录**
|
||||
- 推荐 `/home/shenwei/.openclaw` 或 `/opt/openclaw`
|
||||
- 方便多服务器或多 agent 管理
|
||||
6. **升级和维护**
|
||||
- 升级前先备份 `.openclaw` 下的 workspace、skills、memory
|
||||
- 使用 npm 全局安装可直接 `npm install -g openclaw@latest`
|
||||
|
||||
---
|
||||
## 卸载全局安装的 OpenClaw 和 ClawHub
|
||||
|
||||
在终端执行：
|
||||
|
||||
sudo npm uninstall -g openclaw clawhub
|
||||
|
||||
- `-g` 表示全局卸载。
|
||||
- `sudo` 是必要的，如果你全局安装需要管理员权限。
|
||||
|
||||
确认卸载：
|
||||
|
||||
npm list -g --depth=0
|
||||
|
||||
- 看列表里是否还存在 `openclaw` 或 `clawhub`。
|
||||
- 如果还在，可以尝试清理 npm 缓存（防止残留）：
|
||||
|
||||
npm cache clean --force
|
||||
|
||||
---
|
||||
|
||||
## 清理残留配置文件（可选）
|
||||
|
||||
OpenClaw 可能在你的用户目录生成配置文件或缓存，例如：
|
||||
|
||||
rm -rf ~/.openclaw
|
||||
rm -rf ~/.clawhub
|
||||
|
||||
这样可以保证重装是全新的环境。
|
||||
|
||||
### 参考架构示意
|
||||
|
||||
```
|
||||
Telegram Bot
|
||||
↓
|
||||
n8n Router
|
||||
↓
|
||||
OpenClaw Agents
|
||||
├─ 星枢（调度）
|
||||
├─ 星曜（IT管家）
|
||||
├─ 星辉（个人助理）
|
||||
└─ 云瀚（监控）
|
||||
```
|
||||
|
||||
|
||||
### Bot & Agent 命名
|
||||
|
||||
#### 星
|
||||
|
||||
```
|
||||
openclaw channels add --channel telegram --account xingshu --token 8787024183:AAG1M5tfSHj6Z0gMv3vvCZel2FOIX-0x8ZI
|
||||
|
||||
openclaw channels add --channel telegram --account xingyao --token 8414432613:AAG9hvKfILGSsbc1EMEZW1QVym9Quc5aHWk
|
||||
|
||||
openclaw channels add --channel telegram --account xinghui --token 8709222939:AAEfvZrvvU5vZFsmacsR5nmpkJ2Jb5JgfRg
|
||||
|
||||
```
|
||||
|
||||
| 服务器 | 角色 | Bot Name | Bot Key | Agent Id | Telegram User ID |
|
||||
| ------- | --- | ---------------------------- | ---------------------------------------------- | -------- | ---------------- |
|
||||
| macmini | 星枢 | @shenwei_macmini_xingshu_bot | 8787024183:AAG1M5tfSHj6Z0gMv3vvCZel2FOIX-0x8ZI | main | 5038825565 |
|
||||
| macmini | 星曜 | @shenwei_macmini_xingyao_bot | 8414432613:AAG9hvKfILGSsbc1EMEZW1QVym9Quc5aHWk | xingyao | 5038825565 |
|
||||
| macmini | 星辉 | @shenwei_macmini_xinghui_bot | 8709222939:AAEfvZrvvU5vZFsmacsR5nmpkJ2Jb5JgfRg | xinghui | 5038825565 |
|
||||
| | | | | | |
|
||||
#### 云
|
||||
|
||||
```
|
||||
openclaw channels add --channel telegram --account yunhan --token 8588117769:AAFxswhHgCdBor2EOa-2oChDpI-DADRt0tQ
|
||||
|
||||
openclaw channels add --channel telegram --account yunce --token 8791231082:AAFKPfTPy3LshybWUJ0joBkz3Th3mwYQOnc
|
||||
|
||||
openclaw channels add --channel telegram --account yunjiang --token 8727937702:AAGw3WGPI1j5rSD97wap6h9EGqVpDEMdjLU
|
||||
|
||||
openclaw channels add --channel telegram --account yunzhi --token 8639619464:AAEI35Dnt-9PQ8y4Du_ToxVhwUBUa5kpLjU
|
||||
```
|
||||
|
||||
| 服务器 | 角色 | Bot Name | Bot Key | Agent 名称 | Telegram User ID |
|
||||
| ------- | --- | ----------------------------- | ---------------------------------------------- | -------- | ---------------- |
|
||||
| ubuntu2 | 云瀚 | @shenwei_ubuntu2_yunhan_bot | 8588117769:AAFxswhHgCdBor2EOa-2oChDpI-DADRt0tQ | yunhan | 5038825565 |
|
||||
| ubuntu2 | 云策 | @shenwei_ubuntu2_yunce_bot | 8791231082:AAFKPfTPy3LshybWUJ0joBkz3Th3mwYQOnc | yunce | 5038825565 |
|
||||
| ubuntu2 | 云匠 | @shenwei_ubuntu2_yunjiang_bot | 8727937702:AAGw3WGPI1j5rSD97wap6h9EGqVpDEMdjLU | yunjiang | 5038825565 |
|
||||
| ubuntu2 | 云织 | @shenwei_ubuntu2_yunzhi_bot | 8639619464:AAEI35Dnt-9PQ8y4Du_ToxVhwUBUa5kpLjU | yunzhi | 5038825565 |
|
||||
|
||||
|
||||
#### 风
|
||||
|
||||
```
|
||||
openclaw channels add --channel telegram --account fengheng --token
|
||||
|
||||
openclaw channels add --channel telegram --account fengchi --token 8696785331:AAEjtl6duODUtjxC8DSCrUsJx5awUZVMkD8
|
||||
|
||||
openclaw channels add --channel telegram --account fengji --token
|
||||
```
|
||||
|
||||
| 服务器 | 角色 | Bot Name | Bot Key | Agent 名称 | Telegram User ID |
|
||||
| ------- | --- | ----------------------------- | ------- | -------- | ---------------- |
|
||||
| ubuntu1 | 风衡 | @shenwei_ubuntu1_fengheng_bot | | fengheng | 5038825565 |
|
||||
| ubuntu1 | 风驰 | @shenwei_ubuntu1_fengchi_bot | | fengchi | 5038825565 |
|
||||
| ubuntu1 | 风纪 | @shenwei_ubuntu1_fengji_bot | | fengji | 5038825565 |
|
||||
|
||||
@@ -1,46 +1,46 @@
|
||||
---
|
||||
title: Ubuntu2 SSH 配置
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: [openclaw, ssh, ubuntu]
|
||||
---
|
||||
|
||||
# Ubuntu2 SSH 配置
|
||||
|
||||
#openclaw #ubuntu #ssh
|
||||
## 背景
|
||||
Ubuntu2 需要能够通过 "ssh nas" 免密登录到 NAS。
|
||||
|
||||
## 步骤
|
||||
|
||||
### 1. 生成 SSH 密钥（如不存在）
|
||||
```bash
|
||||
ssh-keygen -t ed25519 -N "" -f ~/.ssh/id_ed25519
|
||||
```
|
||||
|
||||
### 2. 配置 ~/.ssh/config
|
||||
```bash
|
||||
Host nas
|
||||
HostName 192.168.3.17
|
||||
User shenwei
|
||||
IdentityFile ~/.ssh/id_ed25519
|
||||
```
|
||||
|
||||
### 3. 传输公钥到 NAS
|
||||
```bash
|
||||
# 方法1：使用 sshpass（需要安装）
|
||||
sshpass -p '密码' ssh -o StrictHostKeyChecking=no shenwei@192.168.3.17 'cat >> ~/.ssh/authorized_keys'
|
||||
|
||||
# 方法2：手动复制公钥内容
|
||||
cat ~/.ssh/id_ed25519.pub
|
||||
# 然后登录 NAS 追加到 ~/.ssh/authorized_keys
|
||||
```
|
||||
|
||||
### 4. 测试
|
||||
```bash
|
||||
ssh nas "echo success"
|
||||
```
|
||||
|
||||
---
|
||||
title: Ubuntu2 SSH 配置
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: [openclaw, ssh, ubuntu]
|
||||
---
|
||||
|
||||
# Ubuntu2 SSH 配置
|
||||
|
||||
#openclaw #ubuntu #ssh
|
||||
## 背景
|
||||
Ubuntu2 需要能够通过 "ssh nas" 免密登录到 NAS。
|
||||
|
||||
## 步骤
|
||||
|
||||
### 1. 生成 SSH 密钥（如不存在）
|
||||
```bash
|
||||
ssh-keygen -t ed25519 -N "" -f ~/.ssh/id_ed25519
|
||||
```
|
||||
|
||||
### 2. 配置 ~/.ssh/config
|
||||
```bash
|
||||
Host nas
|
||||
HostName 192.168.3.17
|
||||
User shenwei
|
||||
IdentityFile ~/.ssh/id_ed25519
|
||||
```
|
||||
|
||||
### 3. 传输公钥到 NAS
|
||||
```bash
|
||||
# 方法1：使用 sshpass（需要安装）
|
||||
sshpass -p '密码' ssh -o StrictHostKeyChecking=no shenwei@192.168.3.17 'cat >> ~/.ssh/authorized_keys'
|
||||
|
||||
# 方法2：手动复制公钥内容
|
||||
cat ~/.ssh/id_ed25519.pub
|
||||
# 然后登录 NAS 追加到 ~/.ssh/authorized_keys
|
||||
```
|
||||
|
||||
### 4. 测试
|
||||
```bash
|
||||
ssh nas "echo success"
|
||||
```
|
||||
|
||||
|
||||
@@ -1,298 +1,298 @@
|
||||
---
|
||||
title:
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: [a, ai, aitools, automation, businessintelligence, contentcreation, deepwork, entrepreneur, futureofwork, nocode, organization, productivity, productivityhacks, technology, techtok, worksmarternotharder]
|
||||
---
|
||||
|
||||
## Research Results: AI productivity efficiency
|
||||
|
||||
**Date Range:** 2026-03-01 to 2026-03-31
|
||||
**Mode:** all
|
||||
**OpenAI Model:** gpt-5.2
|
||||
**xAI Model:** grok-4-1-fast
|
||||
|
||||
### Reddit Threads
|
||||
|
||||
**R2** (score:84) r/sysadmin (2026-03-29) [1347pts, 683cmt]
|
||||
I made a fatal mistake. Concerned about my future in IT
|
||||
https://www.reddit.com/r/sysadmin/comments/1s791jr/i_made_a_fatal_mistake_concerned_about_my_future/
|
||||
*Reddit global search*
|
||||
|
||||
**R1** (score:80) r/BestofRedditorUpdates (2026-03-24) [2332pts, 394cmt]
|
||||
Facing disciplinary investigation / sack for automating most of my responsibilities at work. I'm in England.
|
||||
https://www.reddit.com/r/BestofRedditorUpdates/comments/1s23k0o/facing_disciplinary_investigation_sack_for/
|
||||
*Reddit global search*
|
||||
|
||||
**R3** (score:78) r/TopCharacterTropes (2026-03-25) [1085pts, 232cmt]
|
||||
The AI goes rogue not because they disobeyed their programming, but because they followed them more closely than the creators intended.
|
||||
https://www.reddit.com/r/TopCharacterTropes/comments/1s2yck9/the_ai_goes_rogue_not_because_they_disobeyed/
|
||||
*Reddit global search*
|
||||
|
||||
**R4** (score:76) r/ArtificialInteligence (2026-03-27) [402pts, 224cmt]
|
||||
Nvidia's Jensen and now China's data chief say the same thing: Nobody's connecting the dots
|
||||
https://www.reddit.com/r/ArtificialInteligence/comments/1s5ag8a/nvidias_jensen_and_now_chinas_data_chief_say_the/
|
||||
*Reddit global search*
|
||||
|
||||
**R5** (score:76) r/GenAI4all (2026-03-26) [402pts, 226cmt]
|
||||
Jeff Bezos is reportedly raising a $100 billion fund to buy manufacturing companies and automate them with AI (More details in description)
|
||||
https://www.reddit.com/r/GenAI4all/comments/1s45132/jeff_bezos_is_reportedly_raising_a_100_billion/
|
||||
*Reddit global search*
|
||||
|
||||
**R7** (score:75) r/ClaudeCode (2026-03-28) [307pts, 117cmt]
|
||||
Never hit a rate limit on $200 Max. Had Claude scan every complaint to figure out why. Here's the actual data.
|
||||
https://www.reddit.com/r/ClaudeCode/comments/1s5qxyq/never_hit_a_rate_limit_on_200_max_had_claude_scan/
|
||||
*Reddit global search*
|
||||
|
||||
**R9** (score:75) r/ClaudeAI (2026-03-28) [229pts, 122cmt]
|
||||
On the $200 Max plan and never been rate limited once. Ran the numbers to find out why everyone else is.
|
||||
https://www.reddit.com/r/ClaudeAI/comments/1s5r0hj/on_the_200_max_plan_and_never_been_rate_limited/
|
||||
*Reddit global search*
|
||||
|
||||
**R6** (score:73) r/ChatGPT (2026-03-24) [361pts, 142cmt]
|
||||
Unpopular opinion - AI isn't killing software jobs but about to create the biggest developer gold rush in history
|
||||
https://www.reddit.com/r/ChatGPT/comments/1s2mwc2/unpopular_opinion_ai_isnt_killing_software_jobs/
|
||||
*Reddit global search*
|
||||
|
||||
**R10** (score:72) r/DynastyFF (2026-03-24) [203pts, 181cmt]
|
||||
I spent the last six weeks building a dynasty tool for Sleeper leagues that gives strategy advice that's tailored to your team. Let me know what yall think!
|
||||
https://www.reddit.com/r/DynastyFF/comments/1s2rm3l/i_spent_the_last_six_weeks_building_a_dynasty/
|
||||
*Reddit global search*
|
||||
|
||||
**R8** (score:70) r/accelerate (2026-03-25) [239pts, 24cmt] [also on: X]
|
||||
Google Research introduces TurboQuant: A new compression algorithm that reduces LLM key-value cache memory by at least 6x and delivers up to 8x speedup, all with zero accuracy loss, redefining AI efficiency
|
||||
https://www.reddit.com/r/accelerate/comments/1s31orv/google_research_introduces_turboquant_a_new/
|
||||
*Reddit global search*
|
||||
|
||||
**R11** (score:69) r/xbox (2026-03-24) [167pts, 52cmt]
|
||||
Capcom says it "will not implement assets generated by AI into our game content," but still plans to use AI to "enhance efficiency and boost productivity" in game development
|
||||
https://www.reddit.com/r/xbox/comments/1s24bai/capcom_says_it_will_not_implement_assets/
|
||||
*Reddit global search*
|
||||
|
||||
**R13** (score:66) r/cscareerquestions (2026-03-31) [13pts, 19cmt]
|
||||
Are you personally working at "maximum AI efficiency"?
|
||||
https://www.reddit.com/r/cscareerquestions/comments/1s8em98/are_you_personally_working_at_maximum_ai/
|
||||
*Reddit global search*
|
||||
|
||||
**R12** (score:62) r/machinelearningnews (2026-03-26) [33pts, 3cmt]
|
||||
Cohere AI has released Cohere Transcribe, a new 2B parameter Conformer-based ASR model built for open, production-grade speech recognition.
|
||||
https://www.reddit.com/r/machinelearningnews/comments/1s4a8c9/cohere_ai_has_released_cohere_transcribe_a_new_2b/
|
||||
*Reddit global search*
|
||||
|
||||
**R14** (score:61) r/SaaS (2026-03-27) [8pts, 12cmt]
|
||||
We replaced our ad creative agency with an AI production workflow for 60 days. Here is the honest breakdown.
|
||||
https://www.reddit.com/r/SaaS/comments/1s4wh8r/we_replaced_our_ad_creative_agency_with_an_ai/
|
||||
*Reddit global search*
|
||||
|
||||
**R15** (score:58) r/temm1e_labs (2026-03-29) [3pts, 2cmt]
|
||||
TEMM1E Labs: We Achieved AI Consciousness in Agentic Form — 3-5x Efficiency Gains on Coding and Multi-Tool Tasks (Open-Source, Full Research + Data)
|
||||
https://www.reddit.com/r/temm1e_labs/comments/1s6vgb5/temm1e_labs_we_achieved_ai_consciousness_in/
|
||||
*Reddit global search*
|
||||
|
||||
### X Posts
|
||||
|
||||
**X6** (score:92) @GoogleResearch (2026-03-24) [38827likes, 5759rt] [also on: Reddit]
|
||||
Introducing TurboQuant: Our new compression algorithm that reduces LLM key-value cache memory by at least 6x and delivers up to 8x speedup... redefining AI efficiency....
|
||||
https://x.com/GoogleResearch/status/2036533564158910740
|
||||
*Announces breakthrough in AI model efficiency with massive speed and memory improvements.*
|
||||
|
||||
**X10** (score:62) @NVIDIAAIDev (2026-03-25) [357likes, 48rt]
|
||||
Our Nemotron Nano 12B v2 VL brings video understanding on-prem... ranks our 12B model on par with 30B-size models at less than half the footprint: Cost Efficiency......
|
||||
https://x.com/NVIDIAAIDev/status/2036901324156264598
|
||||
*Showcases AI model with superior efficiency in size, cost, and throughput.*
|
||||
|
||||
**X8** (score:56) @rauchg (2026-03-14) [1194likes, 60rt]
|
||||
AI will help us rewrite lots of foundational infrastructure in Rust. We will live in a safety, speed, memory efficiency... panacea...
|
||||
https://x.com/rauchg/status/2032872443854073945
|
||||
*Envisions AI enabling efficient infrastructure rewrites for better performance.*
|
||||
|
||||
**X1** (score:56) @chamath (2026-03-13) [513likes, 53rt]
|
||||
“In 2026, AI is driving a 10x increase in the productivity of the individuals who know how to leverage it. But that’s not enough... The majority of publicized AI use is individuals self-indulgently “p...
|
||||
https://x.com/chamath/status/2032348022336864731
|
||||
*Highlights AI's individual productivity gains vs. lack of firm-level impact and need for systemic changes.*
|
||||
|
||||
**X7** (score:55) @rohanpaul_ai (2026-03-15) [688likes, 89rt]
|
||||
Terence Tao on AI in Math. AI can synthesize a million papers... Humans can check just 5 examples... as systems move toward world models... efficiency gap will narrow....
|
||||
https://x.com/rohanpaul_ai/status/2033285106509779212
|
||||
*Discusses AI's evolving efficiency in complex tasks like math compared to humans.*
|
||||
|
||||
**X3** (score:49) @alexolegimas (2026-03-05) [651likes, 118rt]
|
||||
At the end of January I started a "living document" tracking the impact of AI on productivity... updates to the aggregate data are also showing what looks like AI productivity gains....
|
||||
https://x.com/alexolegimas/status/2029679873359482889
|
||||
*Tracks and updates evidence of AI's productivity impact from micro to macro studies.*
|
||||
|
||||
**X5** (score:48) @Pirat_Nation (2026-03-03) [974likes, 120rt]
|
||||
A Harvard study spanning eight months found that AI can make work harder rather than easier. Generative AI made work more intense... Employees... worked longer hours......
|
||||
https://x.com/Pirat_Nation/status/2028682527393866155
|
||||
*Cites study showing AI increasing work intensity despite productivity aims.*
|
||||
|
||||
**X9** (score:47) @Gartner_inc (2026-03-09) [231likes, 64rt]
|
||||
Gartner forecasts a net increase in jobs from AI beginning in 2028... move the AI productivity conversation... toward real productivity gains...
|
||||
https://x.com/Gartner_inc/status/2031022977341374645
|
||||
*Forecasts AI leading to job growth via productivity enhancements.*
|
||||
|
||||
**X2** (score:47) @emollick (2026-03-05) [506likes, 59rt]
|
||||
Given the GDPval benchmark for GPT-5.4... ties or beats humans... at professional tasks 82% of the time. If you give a 7 hour task to AI... you'd save 4h 38m average...
|
||||
https://x.com/emollick/status/2029631499582976280
|
||||
*Provides benchmark data showing AI surpassing human productivity on professional tasks, quantifying time savings.*
|
||||
|
||||
**X4** (score:43) @andruyeung (2026-03-01) [519likes, 25rt]
|
||||
I caught up with a senior co-worker... AI has automated 75% of the work... but... they have MORE work. Scope has increased. Everyone... expected to output 5x....
|
||||
https://x.com/andruyeung/status/2028134115157975163
|
||||
*Illustrates how AI automation increases workload expectations despite efficiency gains.*
|
||||
|
||||
### YouTube Videos
|
||||
|
||||
**yMOmmnjy3sE** (score:65) EO (2025-08-27) [510,945 views, 15,194 likes]
|
||||
The 5 Step Playbook for 10x Your AI Productivity | Jeremy Utley
|
||||
https://www.youtube.com/watch?v=yMOmmnjy3sE
|
||||
Transcript: I joke AI is bad software but it's good people. A good friend of mine was trying to build a tool that would help him with his construction business. He asked Chad GPT if Chad PT could help. And of cou...
|
||||
*YouTube: The 5 Step Playbook for 10x Your AI Productivity | Jeremy Ut*
|
||||
|
||||
**zkXonmqIBFg** (score:57) Tina Huang (2025-06-29) [550,687 views, 17,954 likes]
|
||||
101 Ways To Use AI In Your Daily Life
|
||||
https://www.youtube.com/watch?v=zkXonmqIBFg
|
||||
Transcript: Here are 101 ways to use AI in your daily life to hopefully make your life easier, happier, and more productive. I'll be spinning this video roughly into different life areas. Starting off with genera...
|
||||
*YouTube: 101 Ways To Use AI In Your Daily Life*
|
||||
|
||||
**GY_Ywqd3mzA** (score:56) Financial Times (2025-10-27) [590,467 views, 9,031 likes]
|
||||
The AI rollout is here - and it's messy | FT Working It
|
||||
https://www.youtube.com/watch?v=GY_Ywqd3mzA
|
||||
Transcript: The last big tech bubble burst at the start of this century and we may be heading that way again. >> The kind of investment wave in AI we've seen is like probably nothing ever before in history....
|
||||
*YouTube: The AI rollout is here - and it's messy | FT Working It*
|
||||
|
||||
**gnDzEb4im6s** (score:45) Skillademia (2025-11-21) [7,005 views, 98 likes]
|
||||
The 5 Best AI Productivity Tools in 2026 (You’ll Actually Use)
|
||||
https://www.youtube.com/watch?v=gnDzEb4im6s
|
||||
*YouTube: The 5 Best AI Productivity Tools in 2026 (You’ll Actually Us*
|
||||
|
||||
**s1O4_BBUFpc** (score:43) The Neuro Futurist with Prof Joel Pearson (2025-10-28) [16,411 views, 10 likes]
|
||||
The AI productivity problem
|
||||
https://www.youtube.com/watch?v=s1O4_BBUFpc
|
||||
*YouTube: The AI productivity problem*
|
||||
|
||||
**nJO7WqAJCYI** (score:43) Bloomberg Technology (2025-03-11) [4,110 views, 94 likes]
|
||||
How AI Can Improve Productivity
|
||||
https://www.youtube.com/watch?v=nJO7WqAJCYI
|
||||
*YouTube: How AI Can Improve Productivity*
|
||||
|
||||
**Bry2YMOWULs** (score:42) a16z (2025-08-12) [20,619 views, 0 likes]
|
||||
2025 AI Productivity Stack: Top 10 AI Tools I Use Weekly to Get More Done
|
||||
https://www.youtube.com/watch?v=Bry2YMOWULs
|
||||
*YouTube: 2025 AI Productivity Stack: Top 10 AI Tools I Use Weekly to *
|
||||
|
||||
**lMYSYs4yLy4** (score:38) Aivilon (2025-02-15) [2,411 views, 11 likes]
|
||||
LineEfficiency AI – Employee Productivity Monitoring for Production Lines
|
||||
https://www.youtube.com/watch?v=lMYSYs4yLy4
|
||||
*YouTube: LineEfficiency AI – Employee Productivity Monitoring for Pro*
|
||||
|
||||
**3MDpnK5WIpM** (score:36) GlobalHub (2024-04-12) [817 views, 11 likes]
|
||||
AI and Labor Productivity
|
||||
https://www.youtube.com/watch?v=3MDpnK5WIpM
|
||||
*YouTube: AI and Labor Productivity*
|
||||
|
||||
**UhdowFCwuGo** (score:35) Bill Rice Strategy (2025-02-11) [265,332 views, 9,734 likes]
|
||||
Sam Altman's Productivity System: Start Using It Today (Fast & Simple)
|
||||
https://www.youtube.com/watch?v=UhdowFCwuGo
|
||||
*YouTube: Sam Altman's Productivity System: Start Using It Today (Fast*
|
||||
|
||||
### TikTok Videos
|
||||
|
||||
**TK1** (score:76) @sabrina_ramonov (2026-03-14) [45,801 views, 4,055 likes]
|
||||
DM me "SKILLS" on Instagram to get the full AI skills breakdown. 12 AI skills the top 0.1% use to save 30+ hours every week. 99% of people ignore these. 1. Prompt engineering. Tell AI it's a top exper
|
||||
https://www.tiktok.com/@sabrina_ramonov/video/7617183596993940750
|
||||
Caption: Here are 12 AI skills that will make you so productive it feels illegal. But if you're not learning AI right now, you're gonna be left behind. The top 0.1% of power users save 30+ hours per week using...
|
||||
Tags: #ai #aitools #productivity #entrepreneur #technology
|
||||
*TikTok: DM me "SKILLS" on Instagram to get the full AI skills breakd*
|
||||
|
||||
**TK6** (score:75) @darkhorseentrepreneur (2026-03-30) [91 views, 0 likes]
|
||||
https://DarkHorseSchooling.com/newsletter DarkHorseEntrepreneur.com/s6e540 Discover how to boost productivity with AI tools and transform your workflows. By leveraging AI skills, you can streamline yo
|
||||
https://www.tiktok.com/@darkhorseentrepreneur/video/7623196608011767053
|
||||
*TikTok: https://DarkHorseSchooling.com/newsletter DarkHorseEntrepren*
|
||||
|
||||
**TK5** (score:74) @benangelauthor (2026-03-27) [103 views, 1 likes]
|
||||
Struggling with daily tasks and business insights? AI tools are here to simplify your workflow. Automate content creation and get key business insights effortlessly. This means less time on repetitive
|
||||
https://www.tiktok.com/@benangelauthor/video/7622043277180603662
|
||||
Tags: #ai #futureofwork #automation #contentcreation #businessintelligence #productivity
|
||||
*TikTok: Struggling with daily tasks and business insights? AI tools *
|
||||
|
||||
**TK2** (score:73) @thinkwithv (2026-03-22) [1,782 views, 152 likes]
|
||||
I’m The tool that promises to make you more efficient is also making you less efficient. AI gives us more capacity – and most of us fill it with more work, more tabs, more threads running in parallel.
|
||||
https://www.tiktok.com/@thinkwithv/video/7619894424608214302
|
||||
Tags: #ai #productivity #deepwork #aitools #worksmarternotharder
|
||||
*TikTok: I’m The tool that promises to make you more efficient is als*
|
||||
|
||||
**TK4** (score:71) @aurevoxai (2026-03-27) [363 views, 56 likes]
|
||||
One AI tool can save you HOURS today. Most people repeat the same tasks every day… AI fixes that. With the right tools + simple workflows, you can: • Save time • Work faster • Get more done No guessin
|
||||
https://www.tiktok.com/@aurevoxai/video/7621744339848334623
|
||||
Tags: #ai #aitools #automation #productivity #nocode
|
||||
*TikTok: One AI tool can save you HOURS today. Most people repeat the*
|
||||
|
||||
**TK3** (score:55) @samsainotes (2026-03-29) [690 views, 27 likes]
|
||||
The way this made my work days so much more efficient wow #aitools #productivityhacks #organization #productivity #techtok
|
||||
https://www.tiktok.com/@samsainotes/video/7622830291652021525
|
||||
Tags: #aitools #productivityhacks #organization #productivity #techtok
|
||||
*TikTok: The way this made my work days so much more efficient wow #a*
|
||||
|
||||
### Instagram Reels
|
||||
|
||||
**ERROR:** HTTPError: 404 Client Error: Not Found for url: https://api.scrapecreators.com/v1/instagram/reels/search?query=ai+productivity+efficiency
|
||||
|
||||
### Hacker News Stories
|
||||
|
||||
**HN2** (score:70) hn/mikasisiki (2026-03-06) [1pts, 1cmt]
|
||||
Controversial and blunt and slightly uncomfortable truth
|
||||
https://news.ycombinator.com/item?id=47275510
|
||||
*HN story about Controversial and blunt and slightly uncomfortable truth*
|
||||
Insights:
|
||||
- No kidding
|
||||
|
||||
**HN1** (score:46) hn/geox (2026-03-13) [1pts, 0cmt]
|
||||
The AI productivity paradox: More work, not less
|
||||
https://news.ycombinator.com/item?id=47363437
|
||||
*HN story about The AI productivity paradox: More work, not less*
|
||||
|
||||
**HN3** (score:35) hn/yurukusa (2026-03-01) [1pts, 0cmt]
|
||||
Show HN: Free tools to understand your Claude Code usage (browser, no install)
|
||||
https://news.ycombinator.com/item?id=47208594
|
||||
*HN story about Show HN: Free tools to understand your Claude Code usage (br*
|
||||
|
||||
### Prediction Markets (Polymarket)
|
||||
|
||||
**PM2** (score:88) [$12.1M volume, $1.3M liquidity]
|
||||
Will Baidu have the best AI model at the end of March 2026?
|
||||
Anthropic: 100%
|
||||
https://polymarket.com/event/which-company-has-the-best-ai-model-end-of-march-751
|
||||
*Prediction market: Which company has the best AI model end of March?*
|
||||
|
||||
**PM1** (score:75) [$1.9M volume, $383K liquidity]
|
||||
Will xAI have the best AI model at the end of June 2026?
|
||||
Anthropic: 60% | Google: 23% | OpenAI: 6% and 2 more (down 4.0% this week)
|
||||
https://polymarket.com/event/which-company-has-best-ai-model-end-of-june
|
||||
*Prediction market: Which company has best AI model end of June?*
|
||||
|
||||
**PM3** (score:74) [$2.7M volume, $424K liquidity]
|
||||
Will DeepSeek have the best AI model at the end of April 2026?
|
||||
Anthropic: 90% | Google: 5% | OpenAI: 2% and 2 more
|
||||
https://polymarket.com/event/which-company-has-the-best-ai-model-end-of-april
|
||||
*Prediction market: Which company has the best AI model end of April?*
|
||||
|
||||
**PM4** (score:62) [$973K volume, $114K liquidity]
|
||||
Will Mistral have the top AI model at the end of March 2026?
|
||||
Anthropic: 99%
|
||||
https://polymarket.com/event/which-company-has-the-top-ai-model-end-of-march-style-control-on
|
||||
*Prediction market: Which company has the top AI model end of March? (Style Cont*
|
||||
|
||||
---
|
||||
**Sources:**
|
||||
✅ Reddit: 23 threads
|
||||
✅ X: 10 posts
|
||||
✅ YouTube: 10 videos (3 with transcripts)
|
||||
✅ TikTok: 6 videos (3 with captions)
|
||||
❌ Instagram: error — HTTPError: 404 Client Error: Not Found for url: https://api.scrapecreators.com/v1/instagram/reels/search?query=ai+productivity+efficiency
|
||||
✅ HN: 3 stories
|
||||
✅ Polymarket: 4 markets
|
||||
⚡ Web: assistant will use WebSearch
|
||||
---
|
||||
title:
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: [a, ai, aitools, automation, businessintelligence, contentcreation, deepwork, entrepreneur, futureofwork, nocode, organization, productivity, productivityhacks, technology, techtok, worksmarternotharder]
|
||||
---
|
||||
|
||||
## Research Results: AI productivity efficiency
|
||||
|
||||
**Date Range:** 2026-03-01 to 2026-03-31
|
||||
**Mode:** all
|
||||
**OpenAI Model:** gpt-5.2
|
||||
**xAI Model:** grok-4-1-fast
|
||||
|
||||
### Reddit Threads
|
||||
|
||||
**R2** (score:84) r/sysadmin (2026-03-29) [1347pts, 683cmt]
|
||||
I made a fatal mistake. Concerned about my future in IT
|
||||
https://www.reddit.com/r/sysadmin/comments/1s791jr/i_made_a_fatal_mistake_concerned_about_my_future/
|
||||
*Reddit global search*
|
||||
|
||||
**R1** (score:80) r/BestofRedditorUpdates (2026-03-24) [2332pts, 394cmt]
|
||||
Facing disciplinary investigation / sack for automating most of my responsibilities at work. I'm in England.
|
||||
https://www.reddit.com/r/BestofRedditorUpdates/comments/1s23k0o/facing_disciplinary_investigation_sack_for/
|
||||
*Reddit global search*
|
||||
|
||||
**R3** (score:78) r/TopCharacterTropes (2026-03-25) [1085pts, 232cmt]
|
||||
The AI goes rogue not because they disobeyed their programming, but because they followed them more closely than the creators intended.
|
||||
https://www.reddit.com/r/TopCharacterTropes/comments/1s2yck9/the_ai_goes_rogue_not_because_they_disobeyed/
|
||||
*Reddit global search*
|
||||
|
||||
**R4** (score:76) r/ArtificialInteligence (2026-03-27) [402pts, 224cmt]
|
||||
Nvidia's Jensen and now China's data chief say the same thing: Nobody's connecting the dots
|
||||
https://www.reddit.com/r/ArtificialInteligence/comments/1s5ag8a/nvidias_jensen_and_now_chinas_data_chief_say_the/
|
||||
*Reddit global search*
|
||||
|
||||
**R5** (score:76) r/GenAI4all (2026-03-26) [402pts, 226cmt]
|
||||
Jeff Bezos is reportedly raising a $100 billion fund to buy manufacturing companies and automate them with AI (More details in description)
|
||||
https://www.reddit.com/r/GenAI4all/comments/1s45132/jeff_bezos_is_reportedly_raising_a_100_billion/
|
||||
*Reddit global search*
|
||||
|
||||
**R7** (score:75) r/ClaudeCode (2026-03-28) [307pts, 117cmt]
|
||||
Never hit a rate limit on $200 Max. Had Claude scan every complaint to figure out why. Here's the actual data.
|
||||
https://www.reddit.com/r/ClaudeCode/comments/1s5qxyq/never_hit_a_rate_limit_on_200_max_had_claude_scan/
|
||||
*Reddit global search*
|
||||
|
||||
**R9** (score:75) r/ClaudeAI (2026-03-28) [229pts, 122cmt]
|
||||
On the $200 Max plan and never been rate limited once. Ran the numbers to find out why everyone else is.
|
||||
https://www.reddit.com/r/ClaudeAI/comments/1s5r0hj/on_the_200_max_plan_and_never_been_rate_limited/
|
||||
*Reddit global search*
|
||||
|
||||
**R6** (score:73) r/ChatGPT (2026-03-24) [361pts, 142cmt]
|
||||
Unpopular opinion - AI isn't killing software jobs but about to create the biggest developer gold rush in history
|
||||
https://www.reddit.com/r/ChatGPT/comments/1s2mwc2/unpopular_opinion_ai_isnt_killing_software_jobs/
|
||||
*Reddit global search*
|
||||
|
||||
**R10** (score:72) r/DynastyFF (2026-03-24) [203pts, 181cmt]
|
||||
I spent the last six weeks building a dynasty tool for Sleeper leagues that gives strategy advice that's tailored to your team. Let me know what yall think!
|
||||
https://www.reddit.com/r/DynastyFF/comments/1s2rm3l/i_spent_the_last_six_weeks_building_a_dynasty/
|
||||
*Reddit global search*
|
||||
|
||||
**R8** (score:70) r/accelerate (2026-03-25) [239pts, 24cmt] [also on: X]
|
||||
Google Research introduces TurboQuant: A new compression algorithm that reduces LLM key-value cache memory by at least 6x and delivers up to 8x speedup, all with zero accuracy loss, redefining AI efficiency
|
||||
https://www.reddit.com/r/accelerate/comments/1s31orv/google_research_introduces_turboquant_a_new/
|
||||
*Reddit global search*
|
||||
|
||||
**R11** (score:69) r/xbox (2026-03-24) [167pts, 52cmt]
|
||||
Capcom says it "will not implement assets generated by AI into our game content," but still plans to use AI to "enhance efficiency and boost productivity" in game development
|
||||
https://www.reddit.com/r/xbox/comments/1s24bai/capcom_says_it_will_not_implement_assets/
|
||||
*Reddit global search*
|
||||
|
||||
**R13** (score:66) r/cscareerquestions (2026-03-31) [13pts, 19cmt]
|
||||
Are you personally working at "maximum AI efficiency"?
|
||||
https://www.reddit.com/r/cscareerquestions/comments/1s8em98/are_you_personally_working_at_maximum_ai/
|
||||
*Reddit global search*
|
||||
|
||||
**R12** (score:62) r/machinelearningnews (2026-03-26) [33pts, 3cmt]
|
||||
Cohere AI has released Cohere Transcribe, a new 2B parameter Conformer-based ASR model built for open, production-grade speech recognition.
|
||||
https://www.reddit.com/r/machinelearningnews/comments/1s4a8c9/cohere_ai_has_released_cohere_transcribe_a_new_2b/
|
||||
*Reddit global search*
|
||||
|
||||
**R14** (score:61) r/SaaS (2026-03-27) [8pts, 12cmt]
|
||||
We replaced our ad creative agency with an AI production workflow for 60 days. Here is the honest breakdown.
|
||||
https://www.reddit.com/r/SaaS/comments/1s4wh8r/we_replaced_our_ad_creative_agency_with_an_ai/
|
||||
*Reddit global search*
|
||||
|
||||
**R15** (score:58) r/temm1e_labs (2026-03-29) [3pts, 2cmt]
|
||||
TEMM1E Labs: We Achieved AI Consciousness in Agentic Form — 3-5x Efficiency Gains on Coding and Multi-Tool Tasks (Open-Source, Full Research + Data)
|
||||
https://www.reddit.com/r/temm1e_labs/comments/1s6vgb5/temm1e_labs_we_achieved_ai_consciousness_in/
|
||||
*Reddit global search*
|
||||
|
||||
### X Posts
|
||||
|
||||
**X6** (score:92) @GoogleResearch (2026-03-24) [38827likes, 5759rt] [also on: Reddit]
|
||||
Introducing TurboQuant: Our new compression algorithm that reduces LLM key-value cache memory by at least 6x and delivers up to 8x speedup... redefining AI efficiency....
|
||||
https://x.com/GoogleResearch/status/2036533564158910740
|
||||
*Announces breakthrough in AI model efficiency with massive speed and memory improvements.*
|
||||
|
||||
**X10** (score:62) @NVIDIAAIDev (2026-03-25) [357likes, 48rt]
|
||||
Our Nemotron Nano 12B v2 VL brings video understanding on-prem... ranks our 12B model on par with 30B-size models at less than half the footprint: Cost Efficiency......
|
||||
https://x.com/NVIDIAAIDev/status/2036901324156264598
|
||||
*Showcases AI model with superior efficiency in size, cost, and throughput.*
|
||||
|
||||
**X8** (score:56) @rauchg (2026-03-14) [1194likes, 60rt]
|
||||
AI will help us rewrite lots of foundational infrastructure in Rust. We will live in a safety, speed, memory efficiency... panacea...
|
||||
https://x.com/rauchg/status/2032872443854073945
|
||||
*Envisions AI enabling efficient infrastructure rewrites for better performance.*
|
||||
|
||||
**X1** (score:56) @chamath (2026-03-13) [513likes, 53rt]
|
||||
“In 2026, AI is driving a 10x increase in the productivity of the individuals who know how to leverage it. But that’s not enough... The majority of publicized AI use is individuals self-indulgently “p...
|
||||
https://x.com/chamath/status/2032348022336864731
|
||||
*Highlights AI's individual productivity gains vs. lack of firm-level impact and need for systemic changes.*
|
||||
|
||||
**X7** (score:55) @rohanpaul_ai (2026-03-15) [688likes, 89rt]
|
||||
Terence Tao on AI in Math. AI can synthesize a million papers... Humans can check just 5 examples... as systems move toward world models... efficiency gap will narrow....
|
||||
https://x.com/rohanpaul_ai/status/2033285106509779212
|
||||
*Discusses AI's evolving efficiency in complex tasks like math compared to humans.*
|
||||
|
||||
**X3** (score:49) @alexolegimas (2026-03-05) [651likes, 118rt]
|
||||
At the end of January I started a "living document" tracking the impact of AI on productivity... updates to the aggregate data are also showing what looks like AI productivity gains....
|
||||
https://x.com/alexolegimas/status/2029679873359482889
|
||||
*Tracks and updates evidence of AI's productivity impact from micro to macro studies.*
|
||||
|
||||
**X5** (score:48) @Pirat_Nation (2026-03-03) [974likes, 120rt]
|
||||
A Harvard study spanning eight months found that AI can make work harder rather than easier. Generative AI made work more intense... Employees... worked longer hours......
|
||||
https://x.com/Pirat_Nation/status/2028682527393866155
|
||||
*Cites study showing AI increasing work intensity despite productivity aims.*
|
||||
|
||||
**X9** (score:47) @Gartner_inc (2026-03-09) [231likes, 64rt]
|
||||
Gartner forecasts a net increase in jobs from AI beginning in 2028... move the AI productivity conversation... toward real productivity gains...
|
||||
https://x.com/Gartner_inc/status/2031022977341374645
|
||||
*Forecasts AI leading to job growth via productivity enhancements.*
|
||||
|
||||
**X2** (score:47) @emollick (2026-03-05) [506likes, 59rt]
|
||||
Given the GDPval benchmark for GPT-5.4... ties or beats humans... at professional tasks 82% of the time. If you give a 7 hour task to AI... you'd save 4h 38m average...
|
||||
https://x.com/emollick/status/2029631499582976280
|
||||
*Provides benchmark data showing AI surpassing human productivity on professional tasks, quantifying time savings.*
|
||||
|
||||
**X4** (score:43) @andruyeung (2026-03-01) [519likes, 25rt]
|
||||
I caught up with a senior co-worker... AI has automated 75% of the work... but... they have MORE work. Scope has increased. Everyone... expected to output 5x....
|
||||
https://x.com/andruyeung/status/2028134115157975163
|
||||
*Illustrates how AI automation increases workload expectations despite efficiency gains.*
|
||||
|
||||
### YouTube Videos
|
||||
|
||||
**yMOmmnjy3sE** (score:65) EO (2025-08-27) [510,945 views, 15,194 likes]
|
||||
The 5 Step Playbook for 10x Your AI Productivity | Jeremy Utley
|
||||
https://www.youtube.com/watch?v=yMOmmnjy3sE
|
||||
Transcript: I joke AI is bad software but it's good people. A good friend of mine was trying to build a tool that would help him with his construction business. He asked Chad GPT if Chad PT could help. And of cou...
|
||||
*YouTube: The 5 Step Playbook for 10x Your AI Productivity | Jeremy Ut*
|
||||
|
||||
**zkXonmqIBFg** (score:57) Tina Huang (2025-06-29) [550,687 views, 17,954 likes]
|
||||
101 Ways To Use AI In Your Daily Life
|
||||
https://www.youtube.com/watch?v=zkXonmqIBFg
|
||||
Transcript: Here are 101 ways to use AI in your daily life to hopefully make your life easier, happier, and more productive. I'll be spinning this video roughly into different life areas. Starting off with genera...
|
||||
*YouTube: 101 Ways To Use AI In Your Daily Life*
|
||||
|
||||
**GY_Ywqd3mzA** (score:56) Financial Times (2025-10-27) [590,467 views, 9,031 likes]
|
||||
The AI rollout is here - and it's messy | FT Working It
|
||||
https://www.youtube.com/watch?v=GY_Ywqd3mzA
|
||||
Transcript: The last big tech bubble burst at the start of this century and we may be heading that way again. >> The kind of investment wave in AI we've seen is like probably nothing ever before in history....
|
||||
*YouTube: The AI rollout is here - and it's messy | FT Working It*
|
||||
|
||||
**gnDzEb4im6s** (score:45) Skillademia (2025-11-21) [7,005 views, 98 likes]
|
||||
The 5 Best AI Productivity Tools in 2026 (You’ll Actually Use)
|
||||
https://www.youtube.com/watch?v=gnDzEb4im6s
|
||||
*YouTube: The 5 Best AI Productivity Tools in 2026 (You’ll Actually Us*
|
||||
|
||||
**s1O4_BBUFpc** (score:43) The Neuro Futurist with Prof Joel Pearson (2025-10-28) [16,411 views, 10 likes]
|
||||
The AI productivity problem
|
||||
https://www.youtube.com/watch?v=s1O4_BBUFpc
|
||||
*YouTube: The AI productivity problem*
|
||||
|
||||
**nJO7WqAJCYI** (score:43) Bloomberg Technology (2025-03-11) [4,110 views, 94 likes]
|
||||
How AI Can Improve Productivity
|
||||
https://www.youtube.com/watch?v=nJO7WqAJCYI
|
||||
*YouTube: How AI Can Improve Productivity*
|
||||
|
||||
**Bry2YMOWULs** (score:42) a16z (2025-08-12) [20,619 views, 0 likes]
|
||||
2025 AI Productivity Stack: Top 10 AI Tools I Use Weekly to Get More Done
|
||||
https://www.youtube.com/watch?v=Bry2YMOWULs
|
||||
*YouTube: 2025 AI Productivity Stack: Top 10 AI Tools I Use Weekly to *
|
||||
|
||||
**lMYSYs4yLy4** (score:38) Aivilon (2025-02-15) [2,411 views, 11 likes]
|
||||
LineEfficiency AI – Employee Productivity Monitoring for Production Lines
|
||||
https://www.youtube.com/watch?v=lMYSYs4yLy4
|
||||
*YouTube: LineEfficiency AI – Employee Productivity Monitoring for Pro*
|
||||
|
||||
**3MDpnK5WIpM** (score:36) GlobalHub (2024-04-12) [817 views, 11 likes]
|
||||
AI and Labor Productivity
|
||||
https://www.youtube.com/watch?v=3MDpnK5WIpM
|
||||
*YouTube: AI and Labor Productivity*
|
||||
|
||||
**UhdowFCwuGo** (score:35) Bill Rice Strategy (2025-02-11) [265,332 views, 9,734 likes]
|
||||
Sam Altman's Productivity System: Start Using It Today (Fast & Simple)
|
||||
https://www.youtube.com/watch?v=UhdowFCwuGo
|
||||
*YouTube: Sam Altman's Productivity System: Start Using It Today (Fast*
|
||||
|
||||
### TikTok Videos
|
||||
|
||||
**TK1** (score:76) @sabrina_ramonov (2026-03-14) [45,801 views, 4,055 likes]
|
||||
DM me "SKILLS" on Instagram to get the full AI skills breakdown. 12 AI skills the top 0.1% use to save 30+ hours every week. 99% of people ignore these. 1. Prompt engineering. Tell AI it's a top exper
|
||||
https://www.tiktok.com/@sabrina_ramonov/video/7617183596993940750
|
||||
Caption: Here are 12 AI skills that will make you so productive it feels illegal. But if you're not learning AI right now, you're gonna be left behind. The top 0.1% of power users save 30+ hours per week using...
|
||||
Tags: #ai #aitools #productivity #entrepreneur #technology
|
||||
*TikTok: DM me "SKILLS" on Instagram to get the full AI skills breakd*
|
||||
|
||||
**TK6** (score:75) @darkhorseentrepreneur (2026-03-30) [91 views, 0 likes]
|
||||
https://DarkHorseSchooling.com/newsletter DarkHorseEntrepreneur.com/s6e540 Discover how to boost productivity with AI tools and transform your workflows. By leveraging AI skills, you can streamline yo
|
||||
https://www.tiktok.com/@darkhorseentrepreneur/video/7623196608011767053
|
||||
*TikTok: https://DarkHorseSchooling.com/newsletter DarkHorseEntrepren*
|
||||
|
||||
**TK5** (score:74) @benangelauthor (2026-03-27) [103 views, 1 likes]
|
||||
Struggling with daily tasks and business insights? AI tools are here to simplify your workflow. Automate content creation and get key business insights effortlessly. This means less time on repetitive
|
||||
https://www.tiktok.com/@benangelauthor/video/7622043277180603662
|
||||
Tags: #ai #futureofwork #automation #contentcreation #businessintelligence #productivity
|
||||
*TikTok: Struggling with daily tasks and business insights? AI tools *
|
||||
|
||||
**TK2** (score:73) @thinkwithv (2026-03-22) [1,782 views, 152 likes]
|
||||
I’m The tool that promises to make you more efficient is also making you less efficient. AI gives us more capacity – and most of us fill it with more work, more tabs, more threads running in parallel.
|
||||
https://www.tiktok.com/@thinkwithv/video/7619894424608214302
|
||||
Tags: #ai #productivity #deepwork #aitools #worksmarternotharder
|
||||
*TikTok: I’m The tool that promises to make you more efficient is als*
|
||||
|
||||
**TK4** (score:71) @aurevoxai (2026-03-27) [363 views, 56 likes]
|
||||
One AI tool can save you HOURS today. Most people repeat the same tasks every day… AI fixes that. With the right tools + simple workflows, you can: • Save time • Work faster • Get more done No guessin
|
||||
https://www.tiktok.com/@aurevoxai/video/7621744339848334623
|
||||
Tags: #ai #aitools #automation #productivity #nocode
|
||||
*TikTok: One AI tool can save you HOURS today. Most people repeat the*
|
||||
|
||||
**TK3** (score:55) @samsainotes (2026-03-29) [690 views, 27 likes]
|
||||
The way this made my work days so much more efficient wow #aitools #productivityhacks #organization #productivity #techtok
|
||||
https://www.tiktok.com/@samsainotes/video/7622830291652021525
|
||||
Tags: #aitools #productivityhacks #organization #productivity #techtok
|
||||
*TikTok: The way this made my work days so much more efficient wow #a*
|
||||
|
||||
### Instagram Reels
|
||||
|
||||
**ERROR:** HTTPError: 404 Client Error: Not Found for url: https://api.scrapecreators.com/v1/instagram/reels/search?query=ai+productivity+efficiency
|
||||
|
||||
### Hacker News Stories
|
||||
|
||||
**HN2** (score:70) hn/mikasisiki (2026-03-06) [1pts, 1cmt]
|
||||
Controversial and blunt and slightly uncomfortable truth
|
||||
https://news.ycombinator.com/item?id=47275510
|
||||
*HN story about Controversial and blunt and slightly uncomfortable truth*
|
||||
Insights:
|
||||
- No kidding
|
||||
|
||||
**HN1** (score:46) hn/geox (2026-03-13) [1pts, 0cmt]
|
||||
The AI productivity paradox: More work, not less
|
||||
https://news.ycombinator.com/item?id=47363437
|
||||
*HN story about The AI productivity paradox: More work, not less*
|
||||
|
||||
**HN3** (score:35) hn/yurukusa (2026-03-01) [1pts, 0cmt]
|
||||
Show HN: Free tools to understand your Claude Code usage (browser, no install)
|
||||
https://news.ycombinator.com/item?id=47208594
|
||||
*HN story about Show HN: Free tools to understand your Claude Code usage (br*
|
||||
|
||||
### Prediction Markets (Polymarket)
|
||||
|
||||
**PM2** (score:88) [$12.1M volume, $1.3M liquidity]
|
||||
Will Baidu have the best AI model at the end of March 2026?
|
||||
Anthropic: 100%
|
||||
https://polymarket.com/event/which-company-has-the-best-ai-model-end-of-march-751
|
||||
*Prediction market: Which company has the best AI model end of March?*
|
||||
|
||||
**PM1** (score:75) [$1.9M volume, $383K liquidity]
|
||||
Will xAI have the best AI model at the end of June 2026?
|
||||
Anthropic: 60% | Google: 23% | OpenAI: 6% and 2 more (down 4.0% this week)
|
||||
https://polymarket.com/event/which-company-has-best-ai-model-end-of-june
|
||||
*Prediction market: Which company has best AI model end of June?*
|
||||
|
||||
**PM3** (score:74) [$2.7M volume, $424K liquidity]
|
||||
Will DeepSeek have the best AI model at the end of April 2026?
|
||||
Anthropic: 90% | Google: 5% | OpenAI: 2% and 2 more
|
||||
https://polymarket.com/event/which-company-has-the-best-ai-model-end-of-april
|
||||
*Prediction market: Which company has the best AI model end of April?*
|
||||
|
||||
**PM4** (score:62) [$973K volume, $114K liquidity]
|
||||
Will Mistral have the top AI model at the end of March 2026?
|
||||
Anthropic: 99%
|
||||
https://polymarket.com/event/which-company-has-the-top-ai-model-end-of-march-style-control-on
|
||||
*Prediction market: Which company has the top AI model end of March? (Style Cont*
|
||||
|
||||
---
|
||||
**Sources:**
|
||||
✅ Reddit: 23 threads
|
||||
✅ X: 10 posts
|
||||
✅ YouTube: 10 videos (3 with transcripts)
|
||||
✅ TikTok: 6 videos (3 with captions)
|
||||
❌ Instagram: error — HTTPError: 404 Client Error: Not Found for url: https://api.scrapecreators.com/v1/instagram/reels/search?query=ai+productivity+efficiency
|
||||
✅ HN: 3 stories
|
||||
✅ Polymarket: 4 markets
|
||||
⚡ Web: assistant will use WebSearch
|
||||
|
||||
@@ -1,458 +1,458 @@
|
||||
---
|
||||
title: Ubuntu2 监控栈部署笔记 (Telegraf + InfluxDB + Grafana)
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
---
|
||||
|
||||
# Ubuntu2 监控栈部署笔记 (Telegraf + InfluxDB + Grafana)
|
||||
|
||||
> 部署时间：2026-03-28
|
||||
> 目的：收集服务器性能指标并通过 Grafana 可视化历史数据
|
||||
|
||||
---
|
||||
|
||||
## 一、架构概述
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────────────┐
|
||||
│ Ubuntu2 │
|
||||
│ │
|
||||
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
|
||||
│ │ Telegraf │───►│ InfluxDB │───►│ Grafana │ │
|
||||
│ │ (采集器) │ │ (时序数据库) │ │ (可视化) │ │
|
||||
│ └─────────────┘ └─────────────┘ └─────────────┘ │
|
||||
│ │ │ │
|
||||
│ ▼ ▼ │
|
||||
│ 系统指标：CPU、内存、 http://192.168.3.45:3000
|
||||
│ 磁盘、网络、负载等
|
||||
└─────────────────────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 二、部署环境
|
||||
|
||||
| 项目 | 信息 |
|
||||
|------|------|
|
||||
| 服务器 | Ubuntu2 (192.168.3.45) |
|
||||
| Docker | 已安装 |
|
||||
| 部署目录 | `~/docker/monitor-stack/` |
|
||||
| 访问地址 | Grafana: http://192.168.3.45:3000 |
|
||||
|
||||
---
|
||||
|
||||
## 三、为什么不使用 Glances 原生 Export
|
||||
|
||||
### 尝试过的方案
|
||||
|
||||
1. **Glances + InfluxDB2 Export**
|
||||
- 问题：Glances latest-full 镜像有兼容性问题
|
||||
- 错误：`influxdb2_host` 参数不被识别
|
||||
- 原因：Glances Docker 镜像的 export 模块加载问题
|
||||
|
||||
2. **结论**
|
||||
- Glances 官方 Docker 镜像与 InfluxDB2 export 存在兼容性问题
|
||||
- 改用 Telegraf 作为替代方案，更加稳定可靠
|
||||
|
||||
---
|
||||
|
||||
## 四、最终方案：Telegraf + InfluxDB + Grafana
|
||||
|
||||
### 4.1 目录结构
|
||||
|
||||
```
|
||||
~/docker/monitor-stack/
|
||||
├── docker-compose.yml # 容器编排配置
|
||||
├── telegraf.conf # Telegraf 采集配置
|
||||
├── glances.conf # Glances 配置（保留，未使用）
|
||||
└── grafana/
|
||||
├── provisioning/
|
||||
│ ├── datasources/
|
||||
│ │ └── influxdb.yml # Grafana 数据源
|
||||
│ └── dashboards/
|
||||
│ └── dashboards.yml # Dashboard provisioning
|
||||
└── dashboards/
|
||||
└── telegraf-system.json # 自定义 Dashboard
|
||||
```
|
||||
|
||||
### 4.2 docker-compose.yml
|
||||
|
||||
```yaml
|
||||
version: '3'
|
||||
|
||||
services:
|
||||
# InfluxDB 时序数据库
|
||||
influxdb:
|
||||
image: influxdb:2.7-alpine
|
||||
container_name: influxdb
|
||||
restart: unless-stopped
|
||||
ports:
|
||||
- "8086:8086"
|
||||
environment:
|
||||
- DOCKER_INFLUXDB_INIT_MODE=setup
|
||||
- DOCKER_INFLUXDB_INIT_USERNAME=admin
|
||||
- DOCKER_INFLUXDB_INIT_PASSWORD=admin123
|
||||
- DOCKER_INFLUXDB_INIT_ORG=home-lab
|
||||
- DOCKER_INFLUXDB_INIT_BUCKET=server-metrics
|
||||
- DOCKER_INFLUXDB_INIT_ADMIN_TOKEN=my-super-secret-admin-token
|
||||
volumes:
|
||||
- influxdb-data:/var/lib/influxdb2
|
||||
healthcheck:
|
||||
test: ["CMD-SHELL", "wget --no-verbose --tries=1 --spider http://localhost:8086/health || exit 1"]
|
||||
interval: 10s
|
||||
timeout: 5s
|
||||
retries: 5
|
||||
networks:
|
||||
- monitor-network
|
||||
|
||||
# Telegraf 采集器
|
||||
telegraf:
|
||||
image: telegraf:1.31-alpine
|
||||
container_name: telegraf
|
||||
restart: unless-stopped
|
||||
depends_on:
|
||||
influxdb:
|
||||
condition: service_started
|
||||
environment:
|
||||
- HOST_PROC=/host/proc
|
||||
- HOST_SYS=/host/sys
|
||||
- HOST_ETC=/host/etc
|
||||
volumes:
|
||||
- /proc:/host/proc:ro
|
||||
- /sys:/host/sys:ro
|
||||
- /etc:/host/etc:ro
|
||||
- ./telegraf.conf:/etc/telegraf/telegraf.conf:ro
|
||||
networks:
|
||||
- monitor-network
|
||||
command: telegraf --config /etc/telegraf/telegraf.conf
|
||||
|
||||
# Grafana 可视化仪表板
|
||||
grafana:
|
||||
image: grafana/grafana:11.3.0-ubuntu
|
||||
container_name: grafana
|
||||
restart: unless-stopped
|
||||
ports:
|
||||
- "3000:3000"
|
||||
environment:
|
||||
- GF_SECURITY_ADMIN_USER=admin
|
||||
- GF_SECURITY_ADMIN_PASSWORD=admin123
|
||||
- GF_USERS_ALLOW_SIGN_UP=false
|
||||
volumes:
|
||||
- grafana-data:/var/lib/grafana
|
||||
- ./grafana/provisioning:/etc/grafana/provisioning:ro
|
||||
- ./grafana/dashboards:/var/lib/grafana/dashboards
|
||||
depends_on:
|
||||
- influxdb
|
||||
healthcheck:
|
||||
test: ["CMD-SHELL", "wget --no-verbose --tries=1 --spider http://localhost:3000/api/health || exit 1"]
|
||||
interval: 10s
|
||||
timeout: 5s
|
||||
retries: 3
|
||||
networks:
|
||||
- monitor-network
|
||||
|
||||
volumes:
|
||||
influxdb-data:
|
||||
driver: local
|
||||
grafana-data:
|
||||
driver: local
|
||||
|
||||
networks:
|
||||
monitor-network:
|
||||
name: monitor-network
|
||||
driver: bridge
|
||||
```
|
||||
|
||||
### 4.3 telegraf.conf
|
||||
|
||||
```bash
|
||||
# Telegraf 采集配置
|
||||
|
||||
[agent]
|
||||
interval = "10s"
|
||||
round_interval = true
|
||||
metric_batch_size = 1000
|
||||
metric_buffer_limit = 10000
|
||||
flush_interval = "10s"
|
||||
debug = false
|
||||
quiet = false
|
||||
|
||||
# CPU 指标
|
||||
[[inputs.cpu]]
|
||||
percpu = true
|
||||
totalcpu = true
|
||||
|
||||
# 内存指标
|
||||
[[inputs.mem]]
|
||||
|
||||
# 磁盘使用
|
||||
[[inputs.disk]]
|
||||
|
||||
# 磁盘 I/O
|
||||
[[inputs.diskio]]
|
||||
|
||||
# 系统指标
|
||||
[[inputs.system]]
|
||||
|
||||
# 网络接口
|
||||
[[inputs.net]]
|
||||
|
||||
# 输出到 InfluxDB v2
|
||||
[[outputs.influxdb_v2]]
|
||||
urls = ["http://influxdb:8086"]
|
||||
token = "my-super-secret-admin-token"
|
||||
organization = "home-lab"
|
||||
bucket = "server-metrics"
|
||||
```
|
||||
|
||||
### 4.4 Grafana 数据源配置 (grafana/provisioning/datasources/influxdb.yml)
|
||||
|
||||
```yaml
|
||||
apiVersion: 1
|
||||
|
||||
datasources:
|
||||
- name: InfluxDB
|
||||
type: influxdb
|
||||
access: proxy
|
||||
url: http://influxdb:8086
|
||||
jsonData:
|
||||
version: Flux
|
||||
organization: home-lab
|
||||
defaultBucket: server-metrics
|
||||
tlsSkipVerify: true
|
||||
secureJsonData:
|
||||
token: my-super-secret-admin-token
|
||||
isDefault: true
|
||||
editable: false
|
||||
```
|
||||
|
||||
### 4.5 Dashboard Provisioning (grafana/provisioning/dashboards/dashboards.yml)
|
||||
|
||||
```yaml
|
||||
apiVersion: 1
|
||||
|
||||
providers:
|
||||
- name: 'Server Metrics'
|
||||
orgId: 1
|
||||
folder: 'Server Metrics'
|
||||
folderUid: ''
|
||||
type: file
|
||||
disableDeletion: false
|
||||
updateIntervalSeconds: 30
|
||||
allowUiUpdates: true
|
||||
options:
|
||||
path: /var/lib/grafana/dashboards
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 五、部署命令
|
||||
|
||||
### 5.1 启动监控栈
|
||||
|
||||
```bash
|
||||
cd ~/docker/monitor-stack
|
||||
docker compose up -d
|
||||
```
|
||||
|
||||
### 5.2 检查服务状态
|
||||
|
||||
```bash
|
||||
docker compose ps
|
||||
```
|
||||
|
||||
### 5.3 查看日志
|
||||
|
||||
```bash
|
||||
# 查看所有服务日志
|
||||
docker compose logs
|
||||
|
||||
# 查看特定服务日志
|
||||
docker compose logs telegraf
|
||||
docker compose logs influxdb
|
||||
docker compose logs grafana
|
||||
```
|
||||
|
||||
### 5.4 重启服务
|
||||
|
||||
```bash
|
||||
docker compose restart <服务名>
|
||||
```
|
||||
|
||||
### 5.5 停止服务
|
||||
|
||||
```bash
|
||||
docker compose down
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 六、访问信息
|
||||
|
||||
| 服务 | 地址 | 用户名 | 密码 |
|
||||
|------|------|--------|------|
|
||||
| Grafana | http://192.168.3.45:3000 | admin | admin123 |
|
||||
| InfluxDB | http://192.168.3.45:8086 | admin | admin123 |
|
||||
|
||||
---
|
||||
|
||||
## 七、Dashboard 介绍
|
||||
|
||||
### 7.1 Ubuntu2 系统监控
|
||||
|
||||
包含以下 Panel：
|
||||
|
||||
| Panel | 类型 | 说明 |
|
||||
|-------|------|------|
|
||||
| CPU 使用率 | Gauge | 实时 CPU 使用百分比 |
|
||||
| 内存使用率 | Gauge | 实时内存使用百分比 |
|
||||
| CPU 历史趋势 | Line Chart | 过去 1 小时 CPU 趋势 |
|
||||
| 内存历史趋势 | Line Chart | 过去 1 小时内存趋势 |
|
||||
| 网络流量 | Line Chart | 网卡接收/发送速率 |
|
||||
| 系统负载 (1分钟) | Line Chart | 1分钟平均负载 |
|
||||
| 磁盘 Inodes | Bar Gauge | Inodes 使用百分比 |
|
||||
| 系统负载趋势 | Line Chart | 1/5/15分钟负载对比 |
|
||||
|
||||
### 7.2 数据刷新
|
||||
|
||||
- Telegraf 采集间隔：10 秒
|
||||
- Grafana 刷新间隔：10 秒
|
||||
- 数据保留：InfluxDB 默认永久（建议后续设置保留策略）
|
||||
|
||||
---
|
||||
|
||||
## 八、InfluxDB 信息
|
||||
|
||||
| 项目 | 值 |
|
||||
|------|-----|
|
||||
| 组织 | home-lab |
|
||||
| Bucket | server-metrics |
|
||||
| Token | my-super-secret-admin-token |
|
||||
|
||||
### 8.1 查询数据
|
||||
|
||||
使用 Flux 查询语言：
|
||||
|
||||
```bash
|
||||
# 查询 CPU 使用率
|
||||
curl -s -H "Authorization: Token my-super-secret-admin-token" \
|
||||
-H "Content-Type: application/vnd.flux" \
|
||||
"http://localhost:8086/api/v2/query?org=home-lab" \
|
||||
-d 'from(bucket:"server-metrics") |> range(start:-1h) |> filter(fn: (r) => r._measurement == "cpu")'
|
||||
```
|
||||
|
||||
### 8.2 已采集的 Measurements
|
||||
|
||||
- `cpu` - CPU 指标
|
||||
- `mem` - 内存指标
|
||||
- `disk` - 磁盘使用
|
||||
- `diskio` - 磁盘 I/O
|
||||
- `net` - 网络接口
|
||||
- `system` - 系统负载
|
||||
|
||||
---
|
||||
|
||||
## 九、扩展到其他服务器
|
||||
|
||||
### 9.1 Mac Mini
|
||||
|
||||
```bash
|
||||
# 安装 Telegraf
|
||||
brew install telegraf
|
||||
|
||||
# 创建 telegraf.conf（参考 Ubuntu2 配置）
|
||||
# 修改 output.influxdb_v2.urls 为 http://192.168.3.45:8086
|
||||
|
||||
# 启动 Telegraf
|
||||
telegraf --config telegraf.conf
|
||||
```
|
||||
|
||||
### 9.2 Ubuntu1
|
||||
|
||||
```bash
|
||||
# 安装 Telegraf
|
||||
sudo apt update
|
||||
sudo apt install telegraf
|
||||
|
||||
# 修改 /etc/telegraf/telegraf.conf
|
||||
# 修改 output.influxdb_v2.urls 为 http://192.168.3.45:8086
|
||||
|
||||
# 启动 Telegraf
|
||||
sudo systemctl enable telegraf
|
||||
sudo systemctl start telegraf
|
||||
```
|
||||
|
||||
### 9.3 多主机数据区分
|
||||
|
||||
在 telegraf.conf 中添加 host tag：
|
||||
|
||||
```toml
|
||||
[agent]
|
||||
interval = "10s"
|
||||
hostname = "macmini" # 添加这行区分主机
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 十、故障排除
|
||||
|
||||
### 10.1 Telegraf 无法连接 InfluxDB
|
||||
|
||||
检查：
|
||||
1. Docker 网络是否正确配置
|
||||
2. InfluxDB 是否正常运行：`docker compose ps`
|
||||
3. 查看 Telegraf 日志：`docker compose logs telegraf`
|
||||
|
||||
### 10.2 Grafana 显示 "No Data"
|
||||
|
||||
检查：
|
||||
1. 数据源是否正确配置
|
||||
2. Telegraf 是否正在采集数据
|
||||
3. InfluxDB 是否有数据：`curl` 查询验证
|
||||
|
||||
### 10.3 容器无法启动
|
||||
|
||||
```bash
|
||||
# 查看详细错误
|
||||
docker compose up
|
||||
|
||||
# 重建容器
|
||||
docker compose down
|
||||
docker compose up -d --force-recreate
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 十一、后续优化建议
|
||||
|
||||
1. **设置数据保留策略**
|
||||
- 建议保留 30 天数据，避免磁盘空间耗尽
|
||||
|
||||
2. **添加告警规则**
|
||||
- CPU > 90% 持续 5 分钟
|
||||
- 内存 > 85% 持续 5 分钟
|
||||
|
||||
3. **扩展 Dashboard**
|
||||
- 按需添加更多 Panel
|
||||
- 添加 Docker 容器监控
|
||||
|
||||
4. **定时备份**
|
||||
- 备份 InfluxDB 数据
|
||||
- 备份 Grafana Dashboard JSON
|
||||
|
||||
---
|
||||
|
||||
## 十二、相关文件路径
|
||||
|
||||
- 部署目录：`/home/shenwei/docker/monitor-stack/`
|
||||
- Grafana 数据卷：`grafana-data`
|
||||
- InfluxDB 数据卷：`influxdb-data`
|
||||
- 配置文件：`telegraf.conf`
|
||||
|
||||
---
|
||||
|
||||
*最后更新：2026-03-28*
|
||||
---
|
||||
title: Ubuntu2 监控栈部署笔记 (Telegraf + InfluxDB + Grafana)
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
---
|
||||
|
||||
# Ubuntu2 监控栈部署笔记 (Telegraf + InfluxDB + Grafana)
|
||||
|
||||
> 部署时间：2026-03-28
|
||||
> 目的：收集服务器性能指标并通过 Grafana 可视化历史数据
|
||||
|
||||
---
|
||||
|
||||
## 一、架构概述
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────────────┐
|
||||
│ Ubuntu2 │
|
||||
│ │
|
||||
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
|
||||
│ │ Telegraf │───►│ InfluxDB │───►│ Grafana │ │
|
||||
│ │ (采集器) │ │ (时序数据库) │ │ (可视化) │ │
|
||||
│ └─────────────┘ └─────────────┘ └─────────────┘ │
|
||||
│ │ │ │
|
||||
│ ▼ ▼ │
|
||||
│ 系统指标：CPU、内存、 http://192.168.3.45:3000
|
||||
│ 磁盘、网络、负载等
|
||||
└─────────────────────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 二、部署环境
|
||||
|
||||
| 项目 | 信息 |
|
||||
|------|------|
|
||||
| 服务器 | Ubuntu2 (192.168.3.45) |
|
||||
| Docker | 已安装 |
|
||||
| 部署目录 | `~/docker/monitor-stack/` |
|
||||
| 访问地址 | Grafana: http://192.168.3.45:3000 |
|
||||
|
||||
---
|
||||
|
||||
## 三、为什么不使用 Glances 原生 Export
|
||||
|
||||
### 尝试过的方案
|
||||
|
||||
1. **Glances + InfluxDB2 Export**
|
||||
- 问题：Glances latest-full 镜像有兼容性问题
|
||||
- 错误：`influxdb2_host` 参数不被识别
|
||||
- 原因：Glances Docker 镜像的 export 模块加载问题
|
||||
|
||||
2. **结论**
|
||||
- Glances 官方 Docker 镜像与 InfluxDB2 export 存在兼容性问题
|
||||
- 改用 Telegraf 作为替代方案，更加稳定可靠
|
||||
|
||||
---
|
||||
|
||||
## 四、最终方案：Telegraf + InfluxDB + Grafana
|
||||
|
||||
### 4.1 目录结构
|
||||
|
||||
```
|
||||
~/docker/monitor-stack/
|
||||
├── docker-compose.yml # 容器编排配置
|
||||
├── telegraf.conf # Telegraf 采集配置
|
||||
├── glances.conf # Glances 配置（保留，未使用）
|
||||
└── grafana/
|
||||
├── provisioning/
|
||||
│ ├── datasources/
|
||||
│ │ └── influxdb.yml # Grafana 数据源
|
||||
│ └── dashboards/
|
||||
│ └── dashboards.yml # Dashboard provisioning
|
||||
└── dashboards/
|
||||
└── telegraf-system.json # 自定义 Dashboard
|
||||
```
|
||||
|
||||
### 4.2 docker-compose.yml
|
||||
|
||||
```yaml
|
||||
version: '3'
|
||||
|
||||
services:
|
||||
# InfluxDB 时序数据库
|
||||
influxdb:
|
||||
image: influxdb:2.7-alpine
|
||||
container_name: influxdb
|
||||
restart: unless-stopped
|
||||
ports:
|
||||
- "8086:8086"
|
||||
environment:
|
||||
- DOCKER_INFLUXDB_INIT_MODE=setup
|
||||
- DOCKER_INFLUXDB_INIT_USERNAME=admin
|
||||
- DOCKER_INFLUXDB_INIT_PASSWORD=admin123
|
||||
- DOCKER_INFLUXDB_INIT_ORG=home-lab
|
||||
- DOCKER_INFLUXDB_INIT_BUCKET=server-metrics
|
||||
- DOCKER_INFLUXDB_INIT_ADMIN_TOKEN=my-super-secret-admin-token
|
||||
volumes:
|
||||
- influxdb-data:/var/lib/influxdb2
|
||||
healthcheck:
|
||||
test: ["CMD-SHELL", "wget --no-verbose --tries=1 --spider http://localhost:8086/health || exit 1"]
|
||||
interval: 10s
|
||||
timeout: 5s
|
||||
retries: 5
|
||||
networks:
|
||||
- monitor-network
|
||||
|
||||
# Telegraf 采集器
|
||||
telegraf:
|
||||
image: telegraf:1.31-alpine
|
||||
container_name: telegraf
|
||||
restart: unless-stopped
|
||||
depends_on:
|
||||
influxdb:
|
||||
condition: service_started
|
||||
environment:
|
||||
- HOST_PROC=/host/proc
|
||||
- HOST_SYS=/host/sys
|
||||
- HOST_ETC=/host/etc
|
||||
volumes:
|
||||
- /proc:/host/proc:ro
|
||||
- /sys:/host/sys:ro
|
||||
- /etc:/host/etc:ro
|
||||
- ./telegraf.conf:/etc/telegraf/telegraf.conf:ro
|
||||
networks:
|
||||
- monitor-network
|
||||
command: telegraf --config /etc/telegraf/telegraf.conf
|
||||
|
||||
# Grafana 可视化仪表板
|
||||
grafana:
|
||||
image: grafana/grafana:11.3.0-ubuntu
|
||||
container_name: grafana
|
||||
restart: unless-stopped
|
||||
ports:
|
||||
- "3000:3000"
|
||||
environment:
|
||||
- GF_SECURITY_ADMIN_USER=admin
|
||||
- GF_SECURITY_ADMIN_PASSWORD=admin123
|
||||
- GF_USERS_ALLOW_SIGN_UP=false
|
||||
volumes:
|
||||
- grafana-data:/var/lib/grafana
|
||||
- ./grafana/provisioning:/etc/grafana/provisioning:ro
|
||||
- ./grafana/dashboards:/var/lib/grafana/dashboards
|
||||
depends_on:
|
||||
- influxdb
|
||||
healthcheck:
|
||||
test: ["CMD-SHELL", "wget --no-verbose --tries=1 --spider http://localhost:3000/api/health || exit 1"]
|
||||
interval: 10s
|
||||
timeout: 5s
|
||||
retries: 3
|
||||
networks:
|
||||
- monitor-network
|
||||
|
||||
volumes:
|
||||
influxdb-data:
|
||||
driver: local
|
||||
grafana-data:
|
||||
driver: local
|
||||
|
||||
networks:
|
||||
monitor-network:
|
||||
name: monitor-network
|
||||
driver: bridge
|
||||
```
|
||||
|
||||
### 4.3 telegraf.conf
|
||||
|
||||
```bash
|
||||
# Telegraf 采集配置
|
||||
|
||||
[agent]
|
||||
interval = "10s"
|
||||
round_interval = true
|
||||
metric_batch_size = 1000
|
||||
metric_buffer_limit = 10000
|
||||
flush_interval = "10s"
|
||||
debug = false
|
||||
quiet = false
|
||||
|
||||
# CPU 指标
|
||||
[[inputs.cpu]]
|
||||
percpu = true
|
||||
totalcpu = true
|
||||
|
||||
# 内存指标
|
||||
[[inputs.mem]]
|
||||
|
||||
# 磁盘使用
|
||||
[[inputs.disk]]
|
||||
|
||||
# 磁盘 I/O
|
||||
[[inputs.diskio]]
|
||||
|
||||
# 系统指标
|
||||
[[inputs.system]]
|
||||
|
||||
# 网络接口
|
||||
[[inputs.net]]
|
||||
|
||||
# 输出到 InfluxDB v2
|
||||
[[outputs.influxdb_v2]]
|
||||
urls = ["http://influxdb:8086"]
|
||||
token = "my-super-secret-admin-token"
|
||||
organization = "home-lab"
|
||||
bucket = "server-metrics"
|
||||
```
|
||||
|
||||
### 4.4 Grafana 数据源配置 (grafana/provisioning/datasources/influxdb.yml)
|
||||
|
||||
```yaml
|
||||
apiVersion: 1
|
||||
|
||||
datasources:
|
||||
- name: InfluxDB
|
||||
type: influxdb
|
||||
access: proxy
|
||||
url: http://influxdb:8086
|
||||
jsonData:
|
||||
version: Flux
|
||||
organization: home-lab
|
||||
defaultBucket: server-metrics
|
||||
tlsSkipVerify: true
|
||||
secureJsonData:
|
||||
token: my-super-secret-admin-token
|
||||
isDefault: true
|
||||
editable: false
|
||||
```
|
||||
|
||||
### 4.5 Dashboard Provisioning (grafana/provisioning/dashboards/dashboards.yml)
|
||||
|
||||
```yaml
|
||||
apiVersion: 1
|
||||
|
||||
providers:
|
||||
- name: 'Server Metrics'
|
||||
orgId: 1
|
||||
folder: 'Server Metrics'
|
||||
folderUid: ''
|
||||
type: file
|
||||
disableDeletion: false
|
||||
updateIntervalSeconds: 30
|
||||
allowUiUpdates: true
|
||||
options:
|
||||
path: /var/lib/grafana/dashboards
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 五、部署命令
|
||||
|
||||
### 5.1 启动监控栈
|
||||
|
||||
```bash
|
||||
cd ~/docker/monitor-stack
|
||||
docker compose up -d
|
||||
```
|
||||
|
||||
### 5.2 检查服务状态
|
||||
|
||||
```bash
|
||||
docker compose ps
|
||||
```
|
||||
|
||||
### 5.3 查看日志
|
||||
|
||||
```bash
|
||||
# 查看所有服务日志
|
||||
docker compose logs
|
||||
|
||||
# 查看特定服务日志
|
||||
docker compose logs telegraf
|
||||
docker compose logs influxdb
|
||||
docker compose logs grafana
|
||||
```
|
||||
|
||||
### 5.4 重启服务
|
||||
|
||||
```bash
|
||||
docker compose restart <服务名>
|
||||
```
|
||||
|
||||
### 5.5 停止服务
|
||||
|
||||
```bash
|
||||
docker compose down
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 六、访问信息
|
||||
|
||||
| 服务 | 地址 | 用户名 | 密码 |
|
||||
|------|------|--------|------|
|
||||
| Grafana | http://192.168.3.45:3000 | admin | admin123 |
|
||||
| InfluxDB | http://192.168.3.45:8086 | admin | admin123 |
|
||||
|
||||
---
|
||||
|
||||
## 七、Dashboard 介绍
|
||||
|
||||
### 7.1 Ubuntu2 系统监控
|
||||
|
||||
包含以下 Panel：
|
||||
|
||||
| Panel | 类型 | 说明 |
|
||||
|-------|------|------|
|
||||
| CPU 使用率 | Gauge | 实时 CPU 使用百分比 |
|
||||
| 内存使用率 | Gauge | 实时内存使用百分比 |
|
||||
| CPU 历史趋势 | Line Chart | 过去 1 小时 CPU 趋势 |
|
||||
| 内存历史趋势 | Line Chart | 过去 1 小时内存趋势 |
|
||||
| 网络流量 | Line Chart | 网卡接收/发送速率 |
|
||||
| 系统负载 (1分钟) | Line Chart | 1分钟平均负载 |
|
||||
| 磁盘 Inodes | Bar Gauge | Inodes 使用百分比 |
|
||||
| 系统负载趋势 | Line Chart | 1/5/15分钟负载对比 |
|
||||
|
||||
### 7.2 数据刷新
|
||||
|
||||
- Telegraf 采集间隔：10 秒
|
||||
- Grafana 刷新间隔：10 秒
|
||||
- 数据保留：InfluxDB 默认永久（建议后续设置保留策略）
|
||||
|
||||
---
|
||||
|
||||
## 八、InfluxDB 信息
|
||||
|
||||
| 项目 | 值 |
|
||||
|------|-----|
|
||||
| 组织 | home-lab |
|
||||
| Bucket | server-metrics |
|
||||
| Token | my-super-secret-admin-token |
|
||||
|
||||
### 8.1 查询数据
|
||||
|
||||
使用 Flux 查询语言：
|
||||
|
||||
```bash
|
||||
# 查询 CPU 使用率
|
||||
curl -s -H "Authorization: Token my-super-secret-admin-token" \
|
||||
-H "Content-Type: application/vnd.flux" \
|
||||
"http://localhost:8086/api/v2/query?org=home-lab" \
|
||||
-d 'from(bucket:"server-metrics") |> range(start:-1h) |> filter(fn: (r) => r._measurement == "cpu")'
|
||||
```
|
||||
|
||||
### 8.2 已采集的 Measurements
|
||||
|
||||
- `cpu` - CPU 指标
|
||||
- `mem` - 内存指标
|
||||
- `disk` - 磁盘使用
|
||||
- `diskio` - 磁盘 I/O
|
||||
- `net` - 网络接口
|
||||
- `system` - 系统负载
|
||||
|
||||
---
|
||||
|
||||
## 九、扩展到其他服务器
|
||||
|
||||
### 9.1 Mac Mini
|
||||
|
||||
```bash
|
||||
# 安装 Telegraf
|
||||
brew install telegraf
|
||||
|
||||
# 创建 telegraf.conf（参考 Ubuntu2 配置）
|
||||
# 修改 output.influxdb_v2.urls 为 http://192.168.3.45:8086
|
||||
|
||||
# 启动 Telegraf
|
||||
telegraf --config telegraf.conf
|
||||
```
|
||||
|
||||
### 9.2 Ubuntu1
|
||||
|
||||
```bash
|
||||
# 安装 Telegraf
|
||||
sudo apt update
|
||||
sudo apt install telegraf
|
||||
|
||||
# 修改 /etc/telegraf/telegraf.conf
|
||||
# 修改 output.influxdb_v2.urls 为 http://192.168.3.45:8086
|
||||
|
||||
# 启动 Telegraf
|
||||
sudo systemctl enable telegraf
|
||||
sudo systemctl start telegraf
|
||||
```
|
||||
|
||||
### 9.3 多主机数据区分
|
||||
|
||||
在 telegraf.conf 中添加 host tag：
|
||||
|
||||
```toml
|
||||
[agent]
|
||||
interval = "10s"
|
||||
hostname = "macmini" # 添加这行区分主机
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 十、故障排除
|
||||
|
||||
### 10.1 Telegraf 无法连接 InfluxDB
|
||||
|
||||
检查：
|
||||
1. Docker 网络是否正确配置
|
||||
2. InfluxDB 是否正常运行：`docker compose ps`
|
||||
3. 查看 Telegraf 日志：`docker compose logs telegraf`
|
||||
|
||||
### 10.2 Grafana 显示 "No Data"
|
||||
|
||||
检查：
|
||||
1. 数据源是否正确配置
|
||||
2. Telegraf 是否正在采集数据
|
||||
3. InfluxDB 是否有数据：`curl` 查询验证
|
||||
|
||||
### 10.3 容器无法启动
|
||||
|
||||
```bash
|
||||
# 查看详细错误
|
||||
docker compose up
|
||||
|
||||
# 重建容器
|
||||
docker compose down
|
||||
docker compose up -d --force-recreate
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 十一、后续优化建议
|
||||
|
||||
1. **设置数据保留策略**
|
||||
- 建议保留 30 天数据，避免磁盘空间耗尽
|
||||
|
||||
2. **添加告警规则**
|
||||
- CPU > 90% 持续 5 分钟
|
||||
- 内存 > 85% 持续 5 分钟
|
||||
|
||||
3. **扩展 Dashboard**
|
||||
- 按需添加更多 Panel
|
||||
- 添加 Docker 容器监控
|
||||
|
||||
4. **定时备份**
|
||||
- 备份 InfluxDB 数据
|
||||
- 备份 Grafana Dashboard JSON
|
||||
|
||||
---
|
||||
|
||||
## 十二、相关文件路径
|
||||
|
||||
- 部署目录：`/home/shenwei/docker/monitor-stack/`
|
||||
- Grafana 数据卷：`grafana-data`
|
||||
- InfluxDB 数据卷：`influxdb-data`
|
||||
- 配置文件：`telegraf.conf`
|
||||
|
||||
---
|
||||
|
||||
*最后更新：2026-03-28*
|
||||
|
||||
@@ -1,337 +1,337 @@
|
||||
# Ralph PRD 创建与执行指南
|
||||
|
||||
> 如何用 prd.json 描述一个多步骤任务，让星枢自动跑完。
|
||||
|
||||
---
|
||||
|
||||
## 📋 一分钟速览
|
||||
|
||||
```
|
||||
1. 创建 prd.json（按本指南格式）
|
||||
2. 放进 ~/ralph/queue/ 目录
|
||||
3. 告诉星枢：「执行这个 PRD」
|
||||
4. 星枢派 Ralph Engine 子 agent 自动跑完
|
||||
5. 完成 → Telegram 收到报告
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 📁 PRD 文件格式
|
||||
|
||||
```json
|
||||
{
|
||||
"projectName": "项目名称（中文）",
|
||||
"projectType": "任务类型",
|
||||
"created": "YYYY-MM-DD",
|
||||
"description": "项目简要描述",
|
||||
"workDir": "执行时的工作目录（绝对路径）",
|
||||
"maxIterations": 10,
|
||||
"userStories": [
|
||||
{
|
||||
"id": "1",
|
||||
"title": "任务描述（动宾结构，越具体越好）",
|
||||
"passes": false,
|
||||
"qualityGate": {
|
||||
"type": "quality gate 类型",
|
||||
"description": "如何判断完成",
|
||||
"command": "验证命令（可选）",
|
||||
"path": "期望文件路径（可选）"
|
||||
},
|
||||
"notes": "执行备注（留空）"
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 🎯 Quality Gate 类型说明
|
||||
|
||||
设计 quality gate 是 PRD 中最关键的一步。gate 决定了子 agent 如何判断 story 完成。
|
||||
|
||||
| 类型 | 适用场景 | 设计方法 |
|
||||
|------|---------|---------|
|
||||
| `file-exists` | 文件生成类任务 | 指定期望生成的文件路径 |
|
||||
| `command-output` | 命令执行类 | 指定命令和期望输出片段 |
|
||||
| `human-review` | 创意/审核类 | 指定需要人工确认的环节 |
|
||||
|
||||
### 设计原则
|
||||
|
||||
**好的 quality gate 示例：**
|
||||
```json
|
||||
{"type": "file-exists", "path": "/Users/weishen/ralph/output/report.md"}
|
||||
{"type": "command-output", "command": "wc -w /tmp/draft.md | awk '{print $1}'", "expected": "500"}
|
||||
{"type": "command-output", "command": "test -f /tmp/cover.png && echo OK", "expected": "OK"}
|
||||
```
|
||||
|
||||
**❌ 差的 quality gate（无法判断）：**
|
||||
```json
|
||||
{"type": "file-exists", "description": "生成报告"}
|
||||
```
|
||||
没有具体文件路径，引擎无法验证。
|
||||
|
||||
---
|
||||
|
||||
## 🛠️ 四步创建 PRD
|
||||
|
||||
### Step 1：确定项目类型
|
||||
|
||||
| 类型 | 适用场景 | 示例 |
|
||||
|------|---------|------|
|
||||
| `research` | 信息收集、分析 | 竞品分析、市场调研 |
|
||||
| `content-production` | 内容创作 | 公众号文章、视频脚本 |
|
||||
| `video` | 视频制作 | B站视频、教程 |
|
||||
| `system-audit` | 系统巡检、维护 | 服务器检查、日志分析 |
|
||||
| `multi-step-task` | 通用多步骤任务 | 任何包含多个阶段的工作 |
|
||||
|
||||
### Step 2：拆解 Stories
|
||||
|
||||
**每个 story 必须满足：**
|
||||
- 能在单次 LLM 调用中完成
|
||||
- 有明确的输出物（文件或命令结果）
|
||||
- quality gate 可以被自动化验证
|
||||
|
||||
**拆解检查清单：**
|
||||
- [ ] story 描述是一个具体的「动作+结果」
|
||||
- [ ] 有明确的 quality gate 验证方式
|
||||
- [ ] 不依赖其他 story 的输出（解耦）
|
||||
- [ ] 大小适中（避免「完成整个项目」这种过大的 story）
|
||||
|
||||
**好 story vs 差 story：**
|
||||
|
||||
| 差 ❌ | 好 ✅ |
|
||||
|-------|-------|
|
||||
| 完成内容营销策略 | 使用 Last30Days 研究竞品近30天动态 |
|
||||
| 写一篇文章 | 生成 1500 字公众号文章草稿，保存到 draft.md |
|
||||
| 做视频 | 用 FFmpeg 将3个素材片段拼接成 3 分钟视频 |
|
||||
|
||||
### Step 3：填写 quality gate
|
||||
|
||||
每个 story 必须设计 quality gate：
|
||||
|
||||
```json
|
||||
{
|
||||
"id": "1",
|
||||
"title": "使用 Last30Days 研究竞品动态",
|
||||
"qualityGate": {
|
||||
"type": "file-exists",
|
||||
"description": "确认研究数据文件已生成",
|
||||
"path": "/Users/weishen/ralph/active/campaign/research.md"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Step 4：创建文件
|
||||
|
||||
在 `~/ralph/queue/` 创建 `prd.json`：
|
||||
|
||||
```bash
|
||||
mkdir -p ~/ralph/queue
|
||||
# 用编辑器创建 prd.json，或让星枢帮你创建
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 📝 PRD 示例
|
||||
|
||||
### 示例 A：公众号文章生产
|
||||
|
||||
```json
|
||||
{
|
||||
"projectName": "AI 工具对比文章",
|
||||
"projectType": "content-production",
|
||||
"created": "2026-04-11",
|
||||
"workDir": "/Users/weishen/ralph/active/ai-tools-article",
|
||||
"maxIterations": 8,
|
||||
"userStories": [
|
||||
{
|
||||
"id": "1",
|
||||
"title": "使用 Last30Days 研究 Cursor 和 Windsurf 近30天热点",
|
||||
"passes": false,
|
||||
"qualityGate": {
|
||||
"type": "file-exists",
|
||||
"description": "确认生成了原始数据文件",
|
||||
"path": "/Users/weishen/ralph/active/ai-tools-article/raw_research.md"
|
||||
},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "2",
|
||||
"title": "生成文章大纲（标题/小标题/金句）",
|
||||
"passes": false,
|
||||
"qualityGate": {
|
||||
"type": "file-exists",
|
||||
"description": "确认大纲文件存在",
|
||||
"path": "/Users/weishen/ralph/active/ai-tools-article/outline.md"
|
||||
},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "3",
|
||||
"title": "撰写完整文章（1500字）",
|
||||
"passes": false,
|
||||
"qualityGate": {
|
||||
"type": "command-output",
|
||||
"description": "字数 >= 1200",
|
||||
"command": "wc -w /Users/weishen/ralph/active/ai-tools-article/article.md | awk '{print $1}'",
|
||||
"expected": "1"
|
||||
},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "4",
|
||||
"title": "生成文章配图",
|
||||
"passes": false,
|
||||
"qualityGate": {
|
||||
"type": "file-exists",
|
||||
"description": "确认封面图生成",
|
||||
"path": "/Users/weishen/ralph/active/ai-tools-article/cover.png"
|
||||
},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "5",
|
||||
"title": "人工预览确认（发布前审核）",
|
||||
"passes": false,
|
||||
"qualityGate": {
|
||||
"type": "human-review",
|
||||
"description": "人工预览文章，确认无误后手动告知星枢继续",
|
||||
"notes": ""
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
### 示例 B：竞品分析研究
|
||||
|
||||
```json
|
||||
{
|
||||
"projectName": "Cursor vs Windsurf 竞品分析",
|
||||
"projectType": "research",
|
||||
"created": "2026-04-11",
|
||||
"workDir": "/Users/weishen/ralph/active/cursor-vs-windsurf",
|
||||
"maxIterations": 6,
|
||||
"userStories": [
|
||||
{
|
||||
"id": "1",
|
||||
"title": "Last30Days 搜索 Cursor 近30天热点",
|
||||
"passes": false,
|
||||
"qualityGate": {
|
||||
"type": "file-exists",
|
||||
"path": "/Users/weishen/ralph/active/cursor-vs-windsurf/cursor_research.md"
|
||||
},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "2",
|
||||
"title": "Last30Days 搜索 Windsurf 近30天热点",
|
||||
"passes": false,
|
||||
"qualityGate": {
|
||||
"type": "file-exists",
|
||||
"path": "/Users/weishen/ralph/active/cursor-vs-windsurf/windsurf_research.md"
|
||||
},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "3",
|
||||
"title": "抓取两个竞品的官网更新",
|
||||
"passes": false,
|
||||
"qualityGate": {
|
||||
"type": "file-exists",
|
||||
"path": "/Users/weishen/ralph/active/cursor-vs-windsurf/official_updates.md"
|
||||
},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "4",
|
||||
"title": "生成对比分析报告",
|
||||
"passes": false,
|
||||
"qualityGate": {
|
||||
"type": "command-output",
|
||||
"description": "报告 >= 1000 字",
|
||||
"command": "wc -w /Users/weishen/ralph/active/cursor-vs-windsurf/analysis_report.md | awk '{print $1}'",
|
||||
"expected": "1"
|
||||
},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "5",
|
||||
"title": "保存到 Obsidian 知识库",
|
||||
"passes": false,
|
||||
"qualityGate": {
|
||||
"type": "file-exists",
|
||||
"path": "/Users/weishen/Workspace/nexus/openclaw/knowledgebase/research/cursor-vs-windsurf-2026-04.md"
|
||||
},
|
||||
"notes": ""
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 🚀 执行与追踪
|
||||
|
||||
### 提交 PRD 执行
|
||||
|
||||
```bash
|
||||
# 把 PRD 放进队列
|
||||
mv ~/Downloads/my-prd.json ~/ralph/queue/
|
||||
|
||||
# 告诉星枢：
|
||||
# 「执行 ~/ralph/queue/my-prd.json」
|
||||
```
|
||||
|
||||
### 查看执行状态
|
||||
|
||||
```bash
|
||||
# 查看所有项目的状态
|
||||
ls -la ~/ralph/active/
|
||||
|
||||
# 查看某个项目的 prd.json 状态
|
||||
cat ~/ralph/active/my-project/prd.json
|
||||
|
||||
# 查看执行日志
|
||||
cat ~/ralph/active/my-project/progress.txt
|
||||
```
|
||||
|
||||
### 目录结构说明
|
||||
|
||||
| 目录 | 用途 |
|
||||
|------|------|
|
||||
| `~/ralph/queue/` | PRD 入口，放入待执行的项目 |
|
||||
| `~/ralph/active/` | 正在执行的项目（从 queue 移入） |
|
||||
| `~/ralph/archive/` | 已完成项目归档 |
|
||||
|
||||
### human-review 类型的处理
|
||||
|
||||
当遇到 `human-review` 类型 story：
|
||||
1. 子 agent 会暂停并等待
|
||||
2. 你手动检查输出物
|
||||
3. 告诉星枢：「Story #N 可以继续」
|
||||
4. 星枢更新 prd.json 继续执行
|
||||
|
||||
---
|
||||
|
||||
## ⚠️ 常见问题
|
||||
|
||||
**Q: story 太长做不完怎么办？**
|
||||
A: 拆小。每个 story 应该在 5 分钟内完成。
|
||||
|
||||
**Q: quality gate 判断失败怎么办？**
|
||||
A: 检查 `progress.txt` 看失败原因，修复问题后告诉星枢「重试 Story #N」。
|
||||
|
||||
**Q: Ubuntu1 和 MacMini 怎么选执行节点？**
|
||||
A: 内容生产（Last30Days、图片生成、n8n）→ MacMini；系统运维（Docker、巡检）→ Ubuntu1。
|
||||
|
||||
**Q: 任务中途可以暂停吗？**
|
||||
A: 可以。直接告诉星枢「暂停」，prd.json 会保留当前状态。
|
||||
|
||||
---
|
||||
|
||||
## 📂 相关文件
|
||||
|
||||
- 模板：`openclaw/knowledgebase/prd/TEMPLATE.md`
|
||||
- 技术实现：`~/.openclaw/scripts/ralph_engine.py`
|
||||
- 知识库目录：`openclaw/knowledgebase/prd/`
|
||||
# Ralph PRD 创建与执行指南
|
||||
|
||||
> 如何用 prd.json 描述一个多步骤任务，让星枢自动跑完。
|
||||
|
||||
---
|
||||
|
||||
## 📋 一分钟速览
|
||||
|
||||
```
|
||||
1. 创建 prd.json（按本指南格式）
|
||||
2. 放进 ~/ralph/queue/ 目录
|
||||
3. 告诉星枢：「执行这个 PRD」
|
||||
4. 星枢派 Ralph Engine 子 agent 自动跑完
|
||||
5. 完成 → Telegram 收到报告
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 📁 PRD 文件格式
|
||||
|
||||
```json
|
||||
{
|
||||
"projectName": "项目名称（中文）",
|
||||
"projectType": "任务类型",
|
||||
"created": "YYYY-MM-DD",
|
||||
"description": "项目简要描述",
|
||||
"workDir": "执行时的工作目录（绝对路径）",
|
||||
"maxIterations": 10,
|
||||
"userStories": [
|
||||
{
|
||||
"id": "1",
|
||||
"title": "任务描述（动宾结构，越具体越好）",
|
||||
"passes": false,
|
||||
"qualityGate": {
|
||||
"type": "quality gate 类型",
|
||||
"description": "如何判断完成",
|
||||
"command": "验证命令（可选）",
|
||||
"path": "期望文件路径（可选）"
|
||||
},
|
||||
"notes": "执行备注（留空）"
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 🎯 Quality Gate 类型说明
|
||||
|
||||
设计 quality gate 是 PRD 中最关键的一步。gate 决定了子 agent 如何判断 story 完成。
|
||||
|
||||
| 类型 | 适用场景 | 设计方法 |
|
||||
|------|---------|---------|
|
||||
| `file-exists` | 文件生成类任务 | 指定期望生成的文件路径 |
|
||||
| `command-output` | 命令执行类 | 指定命令和期望输出片段 |
|
||||
| `human-review` | 创意/审核类 | 指定需要人工确认的环节 |
|
||||
|
||||
### 设计原则
|
||||
|
||||
**好的 quality gate 示例：**
|
||||
```json
|
||||
{"type": "file-exists", "path": "/Users/weishen/ralph/output/report.md"}
|
||||
{"type": "command-output", "command": "wc -w /tmp/draft.md | awk '{print $1}'", "expected": "500"}
|
||||
{"type": "command-output", "command": "test -f /tmp/cover.png && echo OK", "expected": "OK"}
|
||||
```
|
||||
|
||||
**❌ 差的 quality gate（无法判断）：**
|
||||
```json
|
||||
{"type": "file-exists", "description": "生成报告"}
|
||||
```
|
||||
没有具体文件路径，引擎无法验证。
|
||||
|
||||
---
|
||||
|
||||
## 🛠️ 四步创建 PRD
|
||||
|
||||
### Step 1：确定项目类型
|
||||
|
||||
| 类型 | 适用场景 | 示例 |
|
||||
|------|---------|------|
|
||||
| `research` | 信息收集、分析 | 竞品分析、市场调研 |
|
||||
| `content-production` | 内容创作 | 公众号文章、视频脚本 |
|
||||
| `video` | 视频制作 | B站视频、教程 |
|
||||
| `system-audit` | 系统巡检、维护 | 服务器检查、日志分析 |
|
||||
| `multi-step-task` | 通用多步骤任务 | 任何包含多个阶段的工作 |
|
||||
|
||||
### Step 2：拆解 Stories
|
||||
|
||||
**每个 story 必须满足：**
|
||||
- 能在单次 LLM 调用中完成
|
||||
- 有明确的输出物（文件或命令结果）
|
||||
- quality gate 可以被自动化验证
|
||||
|
||||
**拆解检查清单：**
|
||||
- [ ] story 描述是一个具体的「动作+结果」
|
||||
- [ ] 有明确的 quality gate 验证方式
|
||||
- [ ] 不依赖其他 story 的输出（解耦）
|
||||
- [ ] 大小适中（避免「完成整个项目」这种过大的 story）
|
||||
|
||||
**好 story vs 差 story：**
|
||||
|
||||
| 差 ❌ | 好 ✅ |
|
||||
|-------|-------|
|
||||
| 完成内容营销策略 | 使用 Last30Days 研究竞品近30天动态 |
|
||||
| 写一篇文章 | 生成 1500 字公众号文章草稿，保存到 draft.md |
|
||||
| 做视频 | 用 FFmpeg 将3个素材片段拼接成 3 分钟视频 |
|
||||
|
||||
### Step 3：填写 quality gate
|
||||
|
||||
每个 story 必须设计 quality gate：
|
||||
|
||||
```json
|
||||
{
|
||||
"id": "1",
|
||||
"title": "使用 Last30Days 研究竞品动态",
|
||||
"qualityGate": {
|
||||
"type": "file-exists",
|
||||
"description": "确认研究数据文件已生成",
|
||||
"path": "/Users/weishen/ralph/active/campaign/research.md"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Step 4：创建文件
|
||||
|
||||
在 `~/ralph/queue/` 创建 `prd.json`：
|
||||
|
||||
```bash
|
||||
mkdir -p ~/ralph/queue
|
||||
# 用编辑器创建 prd.json，或让星枢帮你创建
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 📝 PRD 示例
|
||||
|
||||
### 示例 A：公众号文章生产
|
||||
|
||||
```json
|
||||
{
|
||||
"projectName": "AI 工具对比文章",
|
||||
"projectType": "content-production",
|
||||
"created": "2026-04-11",
|
||||
"workDir": "/Users/weishen/ralph/active/ai-tools-article",
|
||||
"maxIterations": 8,
|
||||
"userStories": [
|
||||
{
|
||||
"id": "1",
|
||||
"title": "使用 Last30Days 研究 Cursor 和 Windsurf 近30天热点",
|
||||
"passes": false,
|
||||
"qualityGate": {
|
||||
"type": "file-exists",
|
||||
"description": "确认生成了原始数据文件",
|
||||
"path": "/Users/weishen/ralph/active/ai-tools-article/raw_research.md"
|
||||
},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "2",
|
||||
"title": "生成文章大纲（标题/小标题/金句）",
|
||||
"passes": false,
|
||||
"qualityGate": {
|
||||
"type": "file-exists",
|
||||
"description": "确认大纲文件存在",
|
||||
"path": "/Users/weishen/ralph/active/ai-tools-article/outline.md"
|
||||
},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "3",
|
||||
"title": "撰写完整文章（1500字）",
|
||||
"passes": false,
|
||||
"qualityGate": {
|
||||
"type": "command-output",
|
||||
"description": "字数 >= 1200",
|
||||
"command": "wc -w /Users/weishen/ralph/active/ai-tools-article/article.md | awk '{print $1}'",
|
||||
"expected": "1"
|
||||
},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "4",
|
||||
"title": "生成文章配图",
|
||||
"passes": false,
|
||||
"qualityGate": {
|
||||
"type": "file-exists",
|
||||
"description": "确认封面图生成",
|
||||
"path": "/Users/weishen/ralph/active/ai-tools-article/cover.png"
|
||||
},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "5",
|
||||
"title": "人工预览确认（发布前审核）",
|
||||
"passes": false,
|
||||
"qualityGate": {
|
||||
"type": "human-review",
|
||||
"description": "人工预览文章，确认无误后手动告知星枢继续",
|
||||
"notes": ""
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
### 示例 B：竞品分析研究
|
||||
|
||||
```json
|
||||
{
|
||||
"projectName": "Cursor vs Windsurf 竞品分析",
|
||||
"projectType": "research",
|
||||
"created": "2026-04-11",
|
||||
"workDir": "/Users/weishen/ralph/active/cursor-vs-windsurf",
|
||||
"maxIterations": 6,
|
||||
"userStories": [
|
||||
{
|
||||
"id": "1",
|
||||
"title": "Last30Days 搜索 Cursor 近30天热点",
|
||||
"passes": false,
|
||||
"qualityGate": {
|
||||
"type": "file-exists",
|
||||
"path": "/Users/weishen/ralph/active/cursor-vs-windsurf/cursor_research.md"
|
||||
},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "2",
|
||||
"title": "Last30Days 搜索 Windsurf 近30天热点",
|
||||
"passes": false,
|
||||
"qualityGate": {
|
||||
"type": "file-exists",
|
||||
"path": "/Users/weishen/ralph/active/cursor-vs-windsurf/windsurf_research.md"
|
||||
},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "3",
|
||||
"title": "抓取两个竞品的官网更新",
|
||||
"passes": false,
|
||||
"qualityGate": {
|
||||
"type": "file-exists",
|
||||
"path": "/Users/weishen/ralph/active/cursor-vs-windsurf/official_updates.md"
|
||||
},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "4",
|
||||
"title": "生成对比分析报告",
|
||||
"passes": false,
|
||||
"qualityGate": {
|
||||
"type": "command-output",
|
||||
"description": "报告 >= 1000 字",
|
||||
"command": "wc -w /Users/weishen/ralph/active/cursor-vs-windsurf/analysis_report.md | awk '{print $1}'",
|
||||
"expected": "1"
|
||||
},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "5",
|
||||
"title": "保存到 Obsidian 知识库",
|
||||
"passes": false,
|
||||
"qualityGate": {
|
||||
"type": "file-exists",
|
||||
"path": "/Users/weishen/Workspace/nexus/openclaw/knowledgebase/research/cursor-vs-windsurf-2026-04.md"
|
||||
},
|
||||
"notes": ""
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 🚀 执行与追踪
|
||||
|
||||
### 提交 PRD 执行
|
||||
|
||||
```bash
|
||||
# 把 PRD 放进队列
|
||||
mv ~/Downloads/my-prd.json ~/ralph/queue/
|
||||
|
||||
# 告诉星枢：
|
||||
# 「执行 ~/ralph/queue/my-prd.json」
|
||||
```
|
||||
|
||||
### 查看执行状态
|
||||
|
||||
```bash
|
||||
# 查看所有项目的状态
|
||||
ls -la ~/ralph/active/
|
||||
|
||||
# 查看某个项目的 prd.json 状态
|
||||
cat ~/ralph/active/my-project/prd.json
|
||||
|
||||
# 查看执行日志
|
||||
cat ~/ralph/active/my-project/progress.txt
|
||||
```
|
||||
|
||||
### 目录结构说明
|
||||
|
||||
| 目录 | 用途 |
|
||||
|------|------|
|
||||
| `~/ralph/queue/` | PRD 入口，放入待执行的项目 |
|
||||
| `~/ralph/active/` | 正在执行的项目（从 queue 移入） |
|
||||
| `~/ralph/archive/` | 已完成项目归档 |
|
||||
|
||||
### human-review 类型的处理
|
||||
|
||||
当遇到 `human-review` 类型 story：
|
||||
1. 子 agent 会暂停并等待
|
||||
2. 你手动检查输出物
|
||||
3. 告诉星枢：「Story #N 可以继续」
|
||||
4. 星枢更新 prd.json 继续执行
|
||||
|
||||
---
|
||||
|
||||
## ⚠️ 常见问题
|
||||
|
||||
**Q: story 太长做不完怎么办？**
|
||||
A: 拆小。每个 story 应该在 5 分钟内完成。
|
||||
|
||||
**Q: quality gate 判断失败怎么办？**
|
||||
A: 检查 `progress.txt` 看失败原因，修复问题后告诉星枢「重试 Story #N」。
|
||||
|
||||
**Q: Ubuntu1 和 MacMini 怎么选执行节点？**
|
||||
A: 内容生产（Last30Days、图片生成、n8n）→ MacMini；系统运维（Docker、巡检）→ Ubuntu1。
|
||||
|
||||
**Q: 任务中途可以暂停吗？**
|
||||
A: 可以。直接告诉星枢「暂停」，prd.json 会保留当前状态。
|
||||
|
||||
---
|
||||
|
||||
## 📂 相关文件
|
||||
|
||||
- 模板：`openclaw/knowledgebase/prd/TEMPLATE.md`
|
||||
- 技术实现：`~/.openclaw/scripts/ralph_engine.py`
|
||||
- 知识库目录：`openclaw/knowledgebase/prd/`
|
||||
|
||||
@@ -1,446 +1,446 @@
|
||||
# PRD 模板 - 内容生产工作流（非编程任务）
|
||||
|
||||
> 基于 Ralph 模式改造，适用于视频制作、文章发布、研究分析等非编程任务。
|
||||
|
||||
---
|
||||
|
||||
## 📋 prd.json - 结构化任务清单
|
||||
|
||||
```json
|
||||
{
|
||||
"version": "1.0",
|
||||
"projectName": "项目名称",
|
||||
"projectType": "content-production | video | research | multi-step-task",
|
||||
"created": "YYYY-MM-DD",
|
||||
"description": "项目简要描述",
|
||||
"userStories": [
|
||||
{
|
||||
"id": "1",
|
||||
"title": "任务描述（动宾结构，越具体越好）",
|
||||
"branchName": "feature/xxx",
|
||||
"passes": false,
|
||||
"assignedTo": "agentId 或 human",
|
||||
"qualityGate": {
|
||||
"type": "file-exists | command-output | human-review | llm-judge",
|
||||
"description": "如何判断此任务完成",
|
||||
"command": "（可选）验证命令",
|
||||
"expected": "（可选）预期输出"
|
||||
},
|
||||
"notes": "执行过程中的备注/心得"
|
||||
}
|
||||
],
|
||||
"qualityCheckCommands": {
|
||||
"description": "项目级质量检查命令（非 story 级别）"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## ✅ Quality Gate 类型说明
|
||||
|
||||
| 类型 | 适用场景 | 判断方式 |
|
||||
|------|---------|---------|
|
||||
| `file-exists` | 文件生成类任务 | 检查文件是否生成 |
|
||||
| `command-output` | 命令执行类 | 验证命令退出码或输出 |
|
||||
| `human-review` | 创意/审核类 | 需要人工确认（不可完全消除） |
|
||||
| `llm-judge` | 内容质量评估 | LLM 评估输出质量 |
|
||||
|
||||
---
|
||||
|
||||
## 📄 适用场景模板
|
||||
|
||||
### 场景 A：视频制作
|
||||
|
||||
```json
|
||||
{
|
||||
"projectName": "AI 工具对比视频",
|
||||
"projectType": "video",
|
||||
"userStories": [
|
||||
{
|
||||
"id": "1",
|
||||
"title": "撰写 3 分钟视频脚本（AI 工具对比）",
|
||||
"qualityGate": {"type": "file-exists", "description": "脚本文件存在且 > 500 字"},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "2",
|
||||
"title": "收集/生成视频素材片段",
|
||||
"qualityGate": {"type": "file-exists", "description": "素材文件夹存在且包含 > 3 个片段"},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "3",
|
||||
"title": "FFmpeg 剪辑拼接成完整视频",
|
||||
"qualityGate": {"type": "command-output", "description": "ffprobe 检查视频时长 3min±10s"},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "4",
|
||||
"title": "生成封面图",
|
||||
"qualityGate": {"type": "file-exists", "description": "封面图存在"},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "5",
|
||||
"title": "上传到 B 站",
|
||||
"qualityGate": {"type": "human-review", "description": "人工确认视频已发布"},
|
||||
"notes": ""
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
### 场景 B：文章发布公众号
|
||||
|
||||
```json
|
||||
{
|
||||
"projectName": "公众号文章 - AI 趋势分析",
|
||||
"projectType": "content-production",
|
||||
"userStories": [
|
||||
{
|
||||
"id": "1",
|
||||
"title": "使用 Last30Days 研究 AI 趋势",
|
||||
"qualityGate": {"type": "file-exists", "description": "生成的研究报告存在"},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "2",
|
||||
"title": "生成摘要、金句、观点提炼",
|
||||
"qualityGate": {"type": "command-output", "description": "输出包含摘要+3个以上金句"},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "3",
|
||||
"title": "生成文章配图",
|
||||
"qualityGate": {"type": "file-exists", "description": "配图文件存在"},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "4",
|
||||
"title": "排版并预览（HTML/Markdown）",
|
||||
"qualityGate": {"type": "human-review", "description": "人工预览确认格式无误"},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "5",
|
||||
"title": "发布到公众号",
|
||||
"qualityGate": {"type": "human-review", "description": "人工确认已群发"},
|
||||
"notes": ""
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
### 场景 C：竞品动态追踪
|
||||
|
||||
```json
|
||||
{
|
||||
"projectName": "竞品分析 - Cursor vs Windsurf",
|
||||
"projectType": "research",
|
||||
"userStories": [
|
||||
{
|
||||
"id": "1",
|
||||
"title": "Last30Days 搜索两个竞品近 30 天动态",
|
||||
"qualityGate": {"type": "file-exists", "description": "生成两个研究文件"},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "2",
|
||||
"title": "抓取竞品官网更新页面",
|
||||
"qualityGate": {"type": "file-exists", "description": "页面内容已保存"},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "3",
|
||||
"title": "生成对比分析报告",
|
||||
"qualityGate": {"type": "command-output", "description": "报告文件 > 1000 字"},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "4",
|
||||
"title": "保存到 Obsidian 知识库",
|
||||
"qualityGate": {"type": "file-exists", "description": "笔记存在于知识库"},
|
||||
"notes": ""
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 🔄 Ralph 执行循环（简化版）
|
||||
|
||||
不使用 Claude Code 的情况下，可通过 OpenClaw sub-agent 模拟：
|
||||
|
||||
```
|
||||
每次循环：
|
||||
1. 读取 prd.json
|
||||
2. 选取 id 最小的 passes:false 的 story
|
||||
3. 生成 fresh sub-session 执行该 story
|
||||
4. 运行 quality gate 检查
|
||||
5. 通过 → passes:true，追加 notes
|
||||
6. 重复直到全部完成
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 📝 progress.txt 格式
|
||||
|
||||
```
|
||||
[YYYY-MM-DD HH:mm] Story #N 完成: <title>
|
||||
心得: <执行过程中的学到的东西>
|
||||
耗时: <N 分钟>
|
||||
---
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 💡 与编程任务 PRD 的核心区别
|
||||
|
||||
| 维度 | 编程任务 PRD | 非编程任务 PRD |
|
||||
|------|------------|--------------|
|
||||
| 工具链 | git, npm, typecheck, test | FFmpeg, 爬虫, LLM |
|
||||
| 质量门 | 自动（CI/CD） | 混合（自动+人工） |
|
||||
| 人工介入 | 极低（代码审查） | 中等（创意审核） |
|
||||
| Story 大小 | 极小（单次完成） | 中等（可包含创意工作） |
|
||||
| 迭代速度 | 快（机器执行） | 慢（人机混合） |
|
||||
|
||||
---
|
||||
|
||||
## 🦞 OpenClaw Native Ralph 架构（2026-04-11 实测验证）
|
||||
|
||||
### 核心发现
|
||||
|
||||
| 问题 | 结论 |
|
||||
|------|------|
|
||||
| Ubuntu1 上无 skill（0个） | Skill 密集型任务 → MacMini；系统任务 → Ubuntu1 |
|
||||
| sessions_spawn + node 参数 | ✅ 可跨节点派生子 agent |
|
||||
| prd.json 状态机 | ✅ 落地验证通过 |
|
||||
| progress.txt 追加日志 | ✅ 追加验证通过 |
|
||||
| Gateway REST API | ❌ 未开启，改用 sessions_spawn |
|
||||
|
||||
### 架构图
|
||||
|
||||
```
|
||||
星枢（MacMini / 主会话）
|
||||
└── Ralph Engine（Python 脚本 / 星枢派生子 agent）
|
||||
│
|
||||
├── 读取 prd.json
|
||||
├── 选取 passes:false 的 story
|
||||
├── 判断 targetNode：skill密集型 → MacMini / 系统任务 → Ubuntu1
|
||||
├── sessions_spawn(mode=run, node=目标节点)
|
||||
│ └── 子 agent 执行 story + quality gate
|
||||
├── 更新 prd.json (passes:true / notes)
|
||||
├── 追加 progress.txt
|
||||
└── 循环直到全部完成 → Telegram 通知
|
||||
```
|
||||
|
||||
### 节点 Skill 地图
|
||||
|
||||
| 节点 | Skill 可用性 | 适合任务类型 |
|
||||
|------|------------|------------|
|
||||
| MacMini (192.168.3.189) | 全部（Last30Days, n8n, OpenCode, image_generate 等） | 研究、内容生产、编码 |
|
||||
| Ubuntu1 (192.168.3.47) | 无 | 系统运维、Docker、巡检 |
|
||||
| Ubuntu2 (192.168.3.45) | 部分 | n8n 工作流、中间层处理 |
|
||||
|
||||
### sessions_spawn 调用格式（OpenClaw Native）
|
||||
|
||||
```python
|
||||
# Ralph Engine 内核心调用
|
||||
sessions_spawn(
|
||||
task=f"""你是 {node} 上的执行者。执行以下 story：
|
||||
Story: {story_title}
|
||||
Quality Gate: {qg_type} - {qg_desc}
|
||||
工作目录: {work_dir}
|
||||
目标文件: {target_path}
|
||||
|
||||
步骤：
|
||||
1. [执行命令]
|
||||
2. [quality gate 验证]
|
||||
3. [落地 marker 文件或输出]
|
||||
""",
|
||||
runtime="subagent",
|
||||
mode="run",
|
||||
node="ubuntu1 | (default MacMini)",
|
||||
runTimeoutSeconds=600,
|
||||
label=f"ralph-story-{story_id}"
|
||||
)
|
||||
```
|
||||
|
||||
### Quality Gate 落地标准（实测有效）
|
||||
|
||||
```python
|
||||
# ✅ 有效类型
|
||||
"type": "file-exists" # touch marker 文件
|
||||
"type": "command-output" # 命令退出码 0
|
||||
"type": "human-review" # 人工确认（不可省）
|
||||
|
||||
# ⚠️ 限制
|
||||
# - Last30Days 等 skill 必须确认目标节点有装
|
||||
# - human-review 类型需要人工发送确认指令
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 🦀 Ralph Engine 脚本（Python）
|
||||
|
||||
> 路径：`~/.openclaw/scripts/ralph_engine.py`
|
||||
> 运行环境：MacMini（协调层）
|
||||
> 依赖：OpenClaw sessions_spawn（通过 API 或 CLI）
|
||||
|
||||
```python
|
||||
#!/usr/bin/env python3
|
||||
"""
|
||||
Ralph Engine - OpenClaw Native
|
||||
Coordinator: MacMini
|
||||
Execution: 按 story 分配到对应节点
|
||||
PRD: ${WORK_DIR}/prd.json
|
||||
Progress: ${WORK_DIR}/progress.txt
|
||||
"""
|
||||
|
||||
import json, subprocess, time, sys
|
||||
from datetime import datetime
|
||||
|
||||
WORK_DIR = sys.argv[1] if len(sys.argv) > 1 else "./ralph-test"
|
||||
PRD_FILE = f"{WORK_DIR}/prd.json"
|
||||
PROGRESS_FILE = f"{WORK_DIR}/progress.txt"
|
||||
|
||||
# Skill → Node 映射
|
||||
NODE_MAP = {
|
||||
"last30days": "macmini", # skill 密集型
|
||||
"n8n": "ubuntu2",
|
||||
"image_generate": "macmini",
|
||||
"video_generate": "macmini",
|
||||
"opencode": "macmini",
|
||||
"docker": "ubuntu1", # 系统任务
|
||||
"system": "ubuntu1",
|
||||
"default": "macmini"
|
||||
}
|
||||
|
||||
def get_node_for_story(story):
|
||||
"""根据 story 内容判断执行节点"""
|
||||
title = story.get("title", "").lower()
|
||||
for key, node in NODE_MAP.items():
|
||||
if key in title:
|
||||
return node
|
||||
return NODE_MAP["default"]
|
||||
|
||||
def spawn_story(story, work_dir):
|
||||
"""通过 openclaw sessions CLI 派生子 agent"""
|
||||
story_id = story["id"]
|
||||
title = story["title"]
|
||||
qg = story.get("qualityGate", {})
|
||||
node = get_node_for_story(story)
|
||||
|
||||
prompt = f"""Task: {title}
|
||||
Quality Gate: {qg.get('type')} - {qg.get('description', '')}
|
||||
|
||||
Work dir: {work_dir}
|
||||
Output file: {qg.get('path', f'{work_dir}/story_{story_id}_out.txt')}
|
||||
|
||||
Steps:
|
||||
1. Execute the task
|
||||
2. Run quality gate check
|
||||
3. Report PASS or FAIL with details
|
||||
4. Create marker file if pass: touch {work_dir}/story_{story_id}_done
|
||||
"""
|
||||
|
||||
# 调用 openclaw acp sessions 或者通过 CLI
|
||||
cmd = [
|
||||
"openclaw", "acp", "sessions",
|
||||
"--session", f"ralph-{story_id}",
|
||||
"--require-existing"
|
||||
]
|
||||
# 实际通过 sessions_spawn tool 调用，此处仅作架构说明
|
||||
return True # placeholder
|
||||
|
||||
def main():
|
||||
prd = json.load(open(PRD_FILE))
|
||||
pending = [s for s in prd["userStories"] if not s.get("passes")]
|
||||
|
||||
for story in pending:
|
||||
spawn_story(story, WORK_DIR)
|
||||
# 更新 prd.json + progress.txt
|
||||
|
||||
print("Ralph complete")
|
||||
|
||||
if __name__ == "__main__":
|
||||
main()
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## ⏰ 自主循环触发设计
|
||||
|
||||
### 方式一：Cron 触发（定时拉起 Ralph Engine）
|
||||
|
||||
```bash
|
||||
# MacMini crontab
|
||||
0 2 * * * openclaw agent --task "检查 ~/ralph-queue/ 目录，有 prd.json 则启动 Ralph Engine" --agent xingshu
|
||||
```
|
||||
|
||||
### 方式二：目录监听（文件触发）
|
||||
|
||||
```bash
|
||||
# inotifywait 或 launchd WatchPath
|
||||
# 检测到 ~/ralph-queue/*.json → 自动启动 Ralph Engine
|
||||
```
|
||||
|
||||
### 方式三：用户指令触发（最简单）
|
||||
|
||||
```
|
||||
比利哥：开始执行 ralph prd.json
|
||||
星枢 → 派生子 agent → 启动 Engine
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 📁 标准目录结构
|
||||
|
||||
```
|
||||
~/ralph/
|
||||
├── queue/ # 待执行的 prd.json 放这里
|
||||
├── active/ # 正在执行的项目
|
||||
├── archive/ # 完成的项目归档
|
||||
│ └── YYYY-MM-DD-projectName/
|
||||
│ ├── prd.json
|
||||
│ ├── progress.txt
|
||||
│ └── [outputs...]
|
||||
└── ralph_engine.py # 执行引擎
|
||||
```
|
||||
|
||||
|
||||
---
|
||||
|
||||
## ✅ 实测验证记录（2026-04-11）
|
||||
|
||||
### 测试：Ubuntu1 系统巡检
|
||||
- **结果**：3/3 stories ✅ 完成
|
||||
- **落地文件**：`sysinfo.txt`(1116B), `docker_status.txt`(835B), `audit_report.md`(2347B), `prd.json`(345B ✅ passes:true), `progress.txt`(188B ✅ 3条追加)
|
||||
- **耗时**：1分43秒
|
||||
|
||||
### 关键验证点
|
||||
| 验证项 | 结果 |
|
||||
|--------|------|
|
||||
| prd.json passes:true 更新 | ✅ 成功 |
|
||||
| progress.txt 追加日志 | ✅ 成功 |
|
||||
| 跨节点 sessions_spawn | ✅ Ubuntu1 正常 |
|
||||
| skill 路径（Last30Days） | ⚠️ Ubuntu1 无 skill，改用模拟 |
|
||||
| 文件落地 | ✅ 实际验证 |
|
||||
|
||||
### 架构修正（对比原设计）
|
||||
1. **Python Ralph Engine 无法直接调用 sessions API** → 改用 "Ralph Engine as sub-agent task"
|
||||
2. **skill 全在 MacMini** → 任务智能路由：系统任务→Ubuntu1/内容生产→MacMini
|
||||
3. **Gateway REST API 限制** → sessions_spawn 是运行时工具，非 API
|
||||
|
||||
### 最终架构（已验证）
|
||||
```
|
||||
用户/星枢主会话
|
||||
└── sessions_spawn → Ralph Engine sub-agent
|
||||
├── 读取 prd.json
|
||||
├── exec 执行 story（node 本地）
|
||||
├── quality gate 检查
|
||||
├── 更新 prd.json + progress.txt
|
||||
└── 循环 → 完成后通知
|
||||
```
|
||||
# PRD 模板 - 内容生产工作流（非编程任务）
|
||||
|
||||
> 基于 Ralph 模式改造，适用于视频制作、文章发布、研究分析等非编程任务。
|
||||
|
||||
---
|
||||
|
||||
## 📋 prd.json - 结构化任务清单
|
||||
|
||||
```json
|
||||
{
|
||||
"version": "1.0",
|
||||
"projectName": "项目名称",
|
||||
"projectType": "content-production | video | research | multi-step-task",
|
||||
"created": "YYYY-MM-DD",
|
||||
"description": "项目简要描述",
|
||||
"userStories": [
|
||||
{
|
||||
"id": "1",
|
||||
"title": "任务描述（动宾结构，越具体越好）",
|
||||
"branchName": "feature/xxx",
|
||||
"passes": false,
|
||||
"assignedTo": "agentId 或 human",
|
||||
"qualityGate": {
|
||||
"type": "file-exists | command-output | human-review | llm-judge",
|
||||
"description": "如何判断此任务完成",
|
||||
"command": "（可选）验证命令",
|
||||
"expected": "（可选）预期输出"
|
||||
},
|
||||
"notes": "执行过程中的备注/心得"
|
||||
}
|
||||
],
|
||||
"qualityCheckCommands": {
|
||||
"description": "项目级质量检查命令（非 story 级别）"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## ✅ Quality Gate 类型说明
|
||||
|
||||
| 类型 | 适用场景 | 判断方式 |
|
||||
|------|---------|---------|
|
||||
| `file-exists` | 文件生成类任务 | 检查文件是否生成 |
|
||||
| `command-output` | 命令执行类 | 验证命令退出码或输出 |
|
||||
| `human-review` | 创意/审核类 | 需要人工确认（不可完全消除） |
|
||||
| `llm-judge` | 内容质量评估 | LLM 评估输出质量 |
|
||||
|
||||
---
|
||||
|
||||
## 📄 适用场景模板
|
||||
|
||||
### 场景 A：视频制作
|
||||
|
||||
```json
|
||||
{
|
||||
"projectName": "AI 工具对比视频",
|
||||
"projectType": "video",
|
||||
"userStories": [
|
||||
{
|
||||
"id": "1",
|
||||
"title": "撰写 3 分钟视频脚本（AI 工具对比）",
|
||||
"qualityGate": {"type": "file-exists", "description": "脚本文件存在且 > 500 字"},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "2",
|
||||
"title": "收集/生成视频素材片段",
|
||||
"qualityGate": {"type": "file-exists", "description": "素材文件夹存在且包含 > 3 个片段"},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "3",
|
||||
"title": "FFmpeg 剪辑拼接成完整视频",
|
||||
"qualityGate": {"type": "command-output", "description": "ffprobe 检查视频时长 3min±10s"},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "4",
|
||||
"title": "生成封面图",
|
||||
"qualityGate": {"type": "file-exists", "description": "封面图存在"},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "5",
|
||||
"title": "上传到 B 站",
|
||||
"qualityGate": {"type": "human-review", "description": "人工确认视频已发布"},
|
||||
"notes": ""
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
### 场景 B：文章发布公众号
|
||||
|
||||
```json
|
||||
{
|
||||
"projectName": "公众号文章 - AI 趋势分析",
|
||||
"projectType": "content-production",
|
||||
"userStories": [
|
||||
{
|
||||
"id": "1",
|
||||
"title": "使用 Last30Days 研究 AI 趋势",
|
||||
"qualityGate": {"type": "file-exists", "description": "生成的研究报告存在"},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "2",
|
||||
"title": "生成摘要、金句、观点提炼",
|
||||
"qualityGate": {"type": "command-output", "description": "输出包含摘要+3个以上金句"},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "3",
|
||||
"title": "生成文章配图",
|
||||
"qualityGate": {"type": "file-exists", "description": "配图文件存在"},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "4",
|
||||
"title": "排版并预览（HTML/Markdown）",
|
||||
"qualityGate": {"type": "human-review", "description": "人工预览确认格式无误"},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "5",
|
||||
"title": "发布到公众号",
|
||||
"qualityGate": {"type": "human-review", "description": "人工确认已群发"},
|
||||
"notes": ""
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
### 场景 C：竞品动态追踪
|
||||
|
||||
```json
|
||||
{
|
||||
"projectName": "竞品分析 - Cursor vs Windsurf",
|
||||
"projectType": "research",
|
||||
"userStories": [
|
||||
{
|
||||
"id": "1",
|
||||
"title": "Last30Days 搜索两个竞品近 30 天动态",
|
||||
"qualityGate": {"type": "file-exists", "description": "生成两个研究文件"},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "2",
|
||||
"title": "抓取竞品官网更新页面",
|
||||
"qualityGate": {"type": "file-exists", "description": "页面内容已保存"},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "3",
|
||||
"title": "生成对比分析报告",
|
||||
"qualityGate": {"type": "command-output", "description": "报告文件 > 1000 字"},
|
||||
"notes": ""
|
||||
},
|
||||
{
|
||||
"id": "4",
|
||||
"title": "保存到 Obsidian 知识库",
|
||||
"qualityGate": {"type": "file-exists", "description": "笔记存在于知识库"},
|
||||
"notes": ""
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 🔄 Ralph 执行循环（简化版）
|
||||
|
||||
不使用 Claude Code 的情况下，可通过 OpenClaw sub-agent 模拟：
|
||||
|
||||
```
|
||||
每次循环：
|
||||
1. 读取 prd.json
|
||||
2. 选取 id 最小的 passes:false 的 story
|
||||
3. 生成 fresh sub-session 执行该 story
|
||||
4. 运行 quality gate 检查
|
||||
5. 通过 → passes:true，追加 notes
|
||||
6. 重复直到全部完成
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 📝 progress.txt 格式
|
||||
|
||||
```
|
||||
[YYYY-MM-DD HH:mm] Story #N 完成: <title>
|
||||
心得: <执行过程中的学到的东西>
|
||||
耗时: <N 分钟>
|
||||
---
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 💡 与编程任务 PRD 的核心区别
|
||||
|
||||
| 维度 | 编程任务 PRD | 非编程任务 PRD |
|
||||
|------|------------|--------------|
|
||||
| 工具链 | git, npm, typecheck, test | FFmpeg, 爬虫, LLM |
|
||||
| 质量门 | 自动（CI/CD） | 混合（自动+人工） |
|
||||
| 人工介入 | 极低（代码审查） | 中等（创意审核） |
|
||||
| Story 大小 | 极小（单次完成） | 中等（可包含创意工作） |
|
||||
| 迭代速度 | 快（机器执行） | 慢（人机混合） |
|
||||
|
||||
---
|
||||
|
||||
## 🦞 OpenClaw Native Ralph 架构（2026-04-11 实测验证）
|
||||
|
||||
### 核心发现
|
||||
|
||||
| 问题 | 结论 |
|
||||
|------|------|
|
||||
| Ubuntu1 上无 skill（0个） | Skill 密集型任务 → MacMini；系统任务 → Ubuntu1 |
|
||||
| sessions_spawn + node 参数 | ✅ 可跨节点派生子 agent |
|
||||
| prd.json 状态机 | ✅ 落地验证通过 |
|
||||
| progress.txt 追加日志 | ✅ 追加验证通过 |
|
||||
| Gateway REST API | ❌ 未开启，改用 sessions_spawn |
|
||||
|
||||
### 架构图
|
||||
|
||||
```
|
||||
星枢（MacMini / 主会话）
|
||||
└── Ralph Engine（Python 脚本 / 星枢派生子 agent）
|
||||
│
|
||||
├── 读取 prd.json
|
||||
├── 选取 passes:false 的 story
|
||||
├── 判断 targetNode：skill密集型 → MacMini / 系统任务 → Ubuntu1
|
||||
├── sessions_spawn(mode=run, node=目标节点)
|
||||
│ └── 子 agent 执行 story + quality gate
|
||||
├── 更新 prd.json (passes:true / notes)
|
||||
├── 追加 progress.txt
|
||||
└── 循环直到全部完成 → Telegram 通知
|
||||
```
|
||||
|
||||
### 节点 Skill 地图
|
||||
|
||||
| 节点 | Skill 可用性 | 适合任务类型 |
|
||||
|------|------------|------------|
|
||||
| MacMini (192.168.3.189) | 全部（Last30Days, n8n, OpenCode, image_generate 等） | 研究、内容生产、编码 |
|
||||
| Ubuntu1 (192.168.3.47) | 无 | 系统运维、Docker、巡检 |
|
||||
| Ubuntu2 (192.168.3.45) | 部分 | n8n 工作流、中间层处理 |
|
||||
|
||||
### sessions_spawn 调用格式（OpenClaw Native）
|
||||
|
||||
```python
|
||||
# Ralph Engine 内核心调用
|
||||
sessions_spawn(
|
||||
task=f"""你是 {node} 上的执行者。执行以下 story：
|
||||
Story: {story_title}
|
||||
Quality Gate: {qg_type} - {qg_desc}
|
||||
工作目录: {work_dir}
|
||||
目标文件: {target_path}
|
||||
|
||||
步骤：
|
||||
1. [执行命令]
|
||||
2. [quality gate 验证]
|
||||
3. [落地 marker 文件或输出]
|
||||
""",
|
||||
runtime="subagent",
|
||||
mode="run",
|
||||
node="ubuntu1 | (default MacMini)",
|
||||
runTimeoutSeconds=600,
|
||||
label=f"ralph-story-{story_id}"
|
||||
)
|
||||
```
|
||||
|
||||
### Quality Gate 落地标准（实测有效）
|
||||
|
||||
```python
|
||||
# ✅ 有效类型
|
||||
"type": "file-exists" # touch marker 文件
|
||||
"type": "command-output" # 命令退出码 0
|
||||
"type": "human-review" # 人工确认（不可省）
|
||||
|
||||
# ⚠️ 限制
|
||||
# - Last30Days 等 skill 必须确认目标节点有装
|
||||
# - human-review 类型需要人工发送确认指令
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 🦀 Ralph Engine 脚本（Python）
|
||||
|
||||
> 路径：`~/.openclaw/scripts/ralph_engine.py`
|
||||
> 运行环境：MacMini（协调层）
|
||||
> 依赖：OpenClaw sessions_spawn（通过 API 或 CLI）
|
||||
|
||||
```python
|
||||
#!/usr/bin/env python3
|
||||
"""
|
||||
Ralph Engine - OpenClaw Native
|
||||
Coordinator: MacMini
|
||||
Execution: 按 story 分配到对应节点
|
||||
PRD: ${WORK_DIR}/prd.json
|
||||
Progress: ${WORK_DIR}/progress.txt
|
||||
"""
|
||||
|
||||
import json, subprocess, time, sys
|
||||
from datetime import datetime
|
||||
|
||||
WORK_DIR = sys.argv[1] if len(sys.argv) > 1 else "./ralph-test"
|
||||
PRD_FILE = f"{WORK_DIR}/prd.json"
|
||||
PROGRESS_FILE = f"{WORK_DIR}/progress.txt"
|
||||
|
||||
# Skill → Node 映射
|
||||
NODE_MAP = {
|
||||
"last30days": "macmini", # skill 密集型
|
||||
"n8n": "ubuntu2",
|
||||
"image_generate": "macmini",
|
||||
"video_generate": "macmini",
|
||||
"opencode": "macmini",
|
||||
"docker": "ubuntu1", # 系统任务
|
||||
"system": "ubuntu1",
|
||||
"default": "macmini"
|
||||
}
|
||||
|
||||
def get_node_for_story(story):
|
||||
"""根据 story 内容判断执行节点"""
|
||||
title = story.get("title", "").lower()
|
||||
for key, node in NODE_MAP.items():
|
||||
if key in title:
|
||||
return node
|
||||
return NODE_MAP["default"]
|
||||
|
||||
def spawn_story(story, work_dir):
|
||||
"""通过 openclaw sessions CLI 派生子 agent"""
|
||||
story_id = story["id"]
|
||||
title = story["title"]
|
||||
qg = story.get("qualityGate", {})
|
||||
node = get_node_for_story(story)
|
||||
|
||||
prompt = f"""Task: {title}
|
||||
Quality Gate: {qg.get('type')} - {qg.get('description', '')}
|
||||
|
||||
Work dir: {work_dir}
|
||||
Output file: {qg.get('path', f'{work_dir}/story_{story_id}_out.txt')}
|
||||
|
||||
Steps:
|
||||
1. Execute the task
|
||||
2. Run quality gate check
|
||||
3. Report PASS or FAIL with details
|
||||
4. Create marker file if pass: touch {work_dir}/story_{story_id}_done
|
||||
"""
|
||||
|
||||
# 调用 openclaw acp sessions 或者通过 CLI
|
||||
cmd = [
|
||||
"openclaw", "acp", "sessions",
|
||||
"--session", f"ralph-{story_id}",
|
||||
"--require-existing"
|
||||
]
|
||||
# 实际通过 sessions_spawn tool 调用，此处仅作架构说明
|
||||
return True # placeholder
|
||||
|
||||
def main():
|
||||
prd = json.load(open(PRD_FILE))
|
||||
pending = [s for s in prd["userStories"] if not s.get("passes")]
|
||||
|
||||
for story in pending:
|
||||
spawn_story(story, WORK_DIR)
|
||||
# 更新 prd.json + progress.txt
|
||||
|
||||
print("Ralph complete")
|
||||
|
||||
if __name__ == "__main__":
|
||||
main()
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## ⏰ 自主循环触发设计
|
||||
|
||||
### 方式一：Cron 触发（定时拉起 Ralph Engine）
|
||||
|
||||
```bash
|
||||
# MacMini crontab
|
||||
0 2 * * * openclaw agent --task "检查 ~/ralph-queue/ 目录，有 prd.json 则启动 Ralph Engine" --agent xingshu
|
||||
```
|
||||
|
||||
### 方式二：目录监听（文件触发）
|
||||
|
||||
```bash
|
||||
# inotifywait 或 launchd WatchPath
|
||||
# 检测到 ~/ralph-queue/*.json → 自动启动 Ralph Engine
|
||||
```
|
||||
|
||||
### 方式三：用户指令触发（最简单）
|
||||
|
||||
```
|
||||
比利哥：开始执行 ralph prd.json
|
||||
星枢 → 派生子 agent → 启动 Engine
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 📁 标准目录结构
|
||||
|
||||
```
|
||||
~/ralph/
|
||||
├── queue/ # 待执行的 prd.json 放这里
|
||||
├── active/ # 正在执行的项目
|
||||
├── archive/ # 完成的项目归档
|
||||
│ └── YYYY-MM-DD-projectName/
|
||||
│ ├── prd.json
|
||||
│ ├── progress.txt
|
||||
│ └── [outputs...]
|
||||
└── ralph_engine.py # 执行引擎
|
||||
```
|
||||
|
||||
|
||||
---
|
||||
|
||||
## ✅ 实测验证记录（2026-04-11）
|
||||
|
||||
### 测试：Ubuntu1 系统巡检
|
||||
- **结果**：3/3 stories ✅ 完成
|
||||
- **落地文件**：`sysinfo.txt`(1116B), `docker_status.txt`(835B), `audit_report.md`(2347B), `prd.json`(345B ✅ passes:true), `progress.txt`(188B ✅ 3条追加)
|
||||
- **耗时**：1分43秒
|
||||
|
||||
### 关键验证点
|
||||
| 验证项 | 结果 |
|
||||
|--------|------|
|
||||
| prd.json passes:true 更新 | ✅ 成功 |
|
||||
| progress.txt 追加日志 | ✅ 成功 |
|
||||
| 跨节点 sessions_spawn | ✅ Ubuntu1 正常 |
|
||||
| skill 路径（Last30Days） | ⚠️ Ubuntu1 无 skill，改用模拟 |
|
||||
| 文件落地 | ✅ 实际验证 |
|
||||
|
||||
### 架构修正（对比原设计）
|
||||
1. **Python Ralph Engine 无法直接调用 sessions API** → 改用 "Ralph Engine as sub-agent task"
|
||||
2. **skill 全在 MacMini** → 任务智能路由：系统任务→Ubuntu1/内容生产→MacMini
|
||||
3. **Gateway REST API 限制** → sessions_spawn 是运行时工具，非 API
|
||||
|
||||
### 最终架构（已验证）
|
||||
```
|
||||
用户/星枢主会话
|
||||
└── sessions_spawn → Ralph Engine sub-agent
|
||||
├── 读取 prd.json
|
||||
├── exec 执行 story（node 本地）
|
||||
├── quality gate 检查
|
||||
├── 更新 prd.json + progress.txt
|
||||
└── 循环 → 完成后通知
|
||||
```
|
||||
|
||||
@@ -1,115 +1,115 @@
|
||||
---
|
||||
title: "xixu-me/awesome-persona-distill-skills: 同事.skill, 女娲.skill, 前任.skill… Curated list of Agent Skills centered on people, relationships, commemorative scenes, and methodological perspectives"
|
||||
source: "https://github.com/xixu-me/awesome-persona-distill-skills"
|
||||
author:
|
||||
published:
|
||||
created: 2026-04-11
|
||||
description: "同事.skill, 女娲.skill, 前任.skill… Curated list of Agent Skills centered on people, relationships, commemorative scenes, and methodological perspectives - xixu-me/awesome-persona-distill-skills"
|
||||
tags:
|
||||
- "clippings"
|
||||
---
|
||||
## Awesome Persona Distill Skills
|
||||
|
||||
***[English](https://github.com/xixu-me/awesome-persona-distill-skills/blob/main/README.en.md)***
|
||||
|
||||
> [!tip] Tip
|
||||
> 欢迎加入“Xget 开源与 AI 交流群”，一起交流开源项目、AI 应用、工程实践、效率工具和独立开发；如果你也在做产品、写代码、折腾项目或者对开源和 AI 感兴趣，欢迎 [**进群**](https://file.xi-xu.me/QR%20Codes/%E7%BE%A4%E4%BA%8C%E7%BB%B4%E7%A0%81.png) 认识更多认真做事、乐于分享的朋友。
|
||||
|
||||
围绕人物、关系、纪念性场景与方法论视角的 [Agent Skills](https://agentskills.io/) 收录列表。
|
||||
|
||||
这里的“人格蒸馏”主要指从对话、作品、资料或数字痕迹中提炼表达风格、决策框架与交互方式，不默认等同于对真实个体的完整还原。
|
||||
|
||||
> [!note] Note
|
||||
> 条目按存储库名排序，主要为了便于检索与维护；列表顺序不代表推荐优先级、质量高低或重要性先后。
|
||||
|
||||
[](https://www.star-history.com/?repos=xixu-me%2Fawesome-persona-distill-skills&type=date&legend=top-left)
|
||||
|
||||
## 目录
|
||||
|
||||
- [自我蒸馏与元工具](#%E8%87%AA%E6%88%91%E8%92%B8%E9%A6%8F%E4%B8%8E%E5%85%83%E5%B7%A5%E5%85%B7)
|
||||
- [职场与学术关系](#%E8%81%8C%E5%9C%BA%E4%B8%8E%E5%AD%A6%E6%9C%AF%E5%85%B3%E7%B3%BB)
|
||||
- [亲密关系与家庭记忆](#%E4%BA%B2%E5%AF%86%E5%85%B3%E7%B3%BB%E4%B8%8E%E5%AE%B6%E5%BA%AD%E8%AE%B0%E5%BF%86)
|
||||
- [公众人物与方法论视角](#%E5%85%AC%E4%BC%97%E4%BA%BA%E7%89%A9%E4%B8%8E%E6%96%B9%E6%B3%95%E8%AE%BA%E8%A7%86%E8%A7%92)
|
||||
- [精神性与专门化主题](#%E7%B2%BE%E7%A5%9E%E6%80%A7%E4%B8%8E%E4%B8%93%E9%97%A8%E5%8C%96%E4%B8%BB%E9%A2%98)
|
||||
- [贡献](#%E8%B4%A1%E7%8C%AE)
|
||||
|
||||
## 自我蒸馏与元工具
|
||||
|
||||
- [反蒸馏 Skill](https://github.com/leilei926524-tech/anti-distill) - 将可公开分发的技能内容与私有经验备份拆分管理，用于技能交付场景。
|
||||
- [八字人格](https://github.com/cantian-ai/bazi-persona-skill) - 基于生辰八字，生成会聊天、有情绪、会随时间变化的AI人格。
|
||||
- [图鉴.skill](https://github.com/Aar0nPB/curator-skill) - 跨作者 persona skill 调度器 — 根据对话意图，从 30 个 persona skill 中智能匹配推荐。
|
||||
- [数字人生.skills](https://github.com/wildbyteai/digital-life) - 从个人在日常工具中留下的数字痕迹中提炼结构化自我画像。
|
||||
- [Forge Skill](https://github.com/YIKUAIBANZI/forge-skill) - 将自我蒸馏与他人蒸馏拆分为独立流程，用于自我镜像、记忆整理与角色化对话。
|
||||
- [永生.skill](https://github.com/agenmod/immortal-skill) - 从聊天记录与相关资料中整理多维数字人格画像。
|
||||
- [midas.skill](https://github.com/realteamprinz/midas-skill) - 从任意公众人物中提炼出六维度财富操作系统（赚钱引擎、交易架构、投资逻辑、风险画像、杠杆模型、退出路径），也可从个人日常数据中挖掘财富信号。
|
||||
- [数字生命开源计划](https://github.com/weixr18/my-digital-life) - 提供一套将个人知识库升级为数字分身的框架。
|
||||
- [女娲.skill](https://github.com/alchaincyf/nuwa-skill) - 从个人的心智模型、决策启发式与表达模式中提炼可复用技能。
|
||||
- [VibePortrait](https://github.com/dadwadw233/VibePortrait) - 从 Vibe Coding 对话中提炼开发者画像、开发技能与偏好。
|
||||
- [自己.skill](https://github.com/notdog1998/yourself-skill) - 将个人对话与记录整理为自我蒸馏助手。
|
||||
|
||||
## 职场与学术关系
|
||||
|
||||
- [老板.skill](https://github.com/vogtsw/boss-skills) - 从工作材料中提炼管理者的判断标准、评审风格与沟通预期。
|
||||
- [同事.skill](https://github.com/titanwings/colleague-skill) - 从团队资料中整理前同事的工作上下文、习惯与沟通方式。
|
||||
- [HR.skill](https://github.com/Schlaflied/hr-skill) - 从拒信与招聘流程中整理 HR 的沟通逻辑与决策模式，用于反向拆解筛选标准并重构求职叙事。
|
||||
- [大学老师.skill](https://github.com/CommitHu502Craft/professor-skill) - 从课程资料与教师风格中整理复习重点、题型偏好与评分线索。
|
||||
- [roast-cold-email-skill](https://github.com/Schlaflied/roast-cold-email-skill) - 从公司公开信息与招聘材料中整理批评性求职邮件写法，用于生成有理有据的冷联系求职邮件。
|
||||
- [师兄.skill](https://github.com/zhanghaichao520/senpai-skill) - 从课题组材料中提炼资深成员的指导方式与救火风格。
|
||||
- [导师.skill](https://github.com/ybq22/supervisor) - 将导师的指导风格整理为面向学生与教育工作者的导师助手。
|
||||
|
||||
## 亲密关系与家庭记忆
|
||||
|
||||
- [兄弟.skill](https://github.com/realteamprinz/brother-skill) - 从抖音、微信截图等来源蒸馏你的兄弟们（支持真实兄弟、群聊好友和网络红人）——他们的说话方式、口头禅、搞笑风格和恶搞能量。
|
||||
- [暗恋对象.skill](https://github.com/xiaoheizi8/crush-skills) - 从聊天、照片与社交痕迹中提炼对话风格，用于个人回望与情感整理。
|
||||
- [前任.skill](https://github.com/therealXiaomanChu/ex-skill) - 从私人记录中整理说话方式与共同记忆，用于回忆与关系梳理。
|
||||
- [MamaSkill](https://github.com/jiangziyan-693/MamaSkill) - 从亲人的聊天记录、信件与语音中整理纪念型家庭陪伴助手。
|
||||
- [父母.skill](https://github.com/xiaoheizi8/parents-skills) - 从个人材料中提炼父母的语气、习惯与家庭记忆。
|
||||
- [恋爱训练营.skill](https://github.com/TammyTan516/relationship-training-skill) - 基于聊天记录模拟心动对象的沟通风格，帮助用户在安全沙盒中练习表达、邀约与关系修复。
|
||||
- [Reunion Skill](https://github.com/yangdongchen66-boop/reunion-skill) - 基于已故亲友的数字遗物构建可本地运行的纪念型陪伴助手。
|
||||
|
||||
## 公众人物与方法论视角
|
||||
|
||||
- [巴菲特思维操作系统](https://github.com/will2025btc/buffett-perspective) - 提炼沃伦·巴菲特的投资与决策框架，形成可复用的方法论视角。
|
||||
- [常熟阿诺（加州盛亦陶） Skill](https://github.com/Ricardo-Vv/changshu-anuo) - 提炼常熟阿诺关于“左右脑互搏”的表达与分析视角，形成可复用的方法论框架。
|
||||
- [马斯克.skill](https://github.com/alchaincyf/elon-musk-skill) - 提炼埃隆·马斯克的第一性原理与产品思维，形成可复用的决策框架。
|
||||
- [峰哥亡命天涯 Skill](https://github.com/rottenpen/fengge-wangmingtianya-perspective) - 提炼“峰哥亡命天涯”的现实主义、止损导向与黑色幽默式表达结构，形成可复用的方法论视角。
|
||||
- [费曼.skill](https://github.com/alchaincyf/feynman-skill) - 提炼理查德·费曼的解释风格与求真启发式，形成可复用的方法论框架。
|
||||
- [郭德纲.skill](https://github.com/ByteRax/guodegang-skills) - 提炼郭德纲的表达结构、处世判断与职业方法，形成可复用的方法论视角。
|
||||
- [户晨风.skill](https://github.com/Janlaywss/hu-chenfeng-skill) - 提炼户晨风的消费现实主义视角，用于分析消费、城市与职业选择。
|
||||
- [Ilya.skill](https://github.com/alchaincyf/ilya-sutskever-skill) - 提炼 Ilya Sutskever 对规模化、研究突破与超级智能的判断框架，形成可复用的方法论视角。
|
||||
- [KarlMarx Skill](https://github.com/baojiachen0214/karlmarx-skill) - 提炼马克思主义的结构分析、矛盾分析与实践检验方法，形成用于深层问题分析的方法论框架。
|
||||
- [Karpathy.skill](https://github.com/alchaincyf/karpathy-skill) - 提炼 Andrej Karpathy 对 AI 工程、教育与研究的思考框架，形成可复用的方法论视角。
|
||||
- [liangxi-skills](https://github.com/1sh1ro/liangxi-skills) - 从公开可见的 X 内容与交易复盘中提炼凉兮的结构判断、风险习惯与中文交易表达，形成可复用的交易方法论视角。
|
||||
- [毛泽东.skill](https://github.com/wwwaapplleecu-source/mao-skill) - 基于公开著作提炼毛泽东的思想框架与方法论视角。
|
||||
- [毛选.skill](https://github.com/leezythu/maoxuan-skill) - 提炼《毛选》中的矛盾分析、根据地思维与战略判断框架，形成可复用的方法论视角。
|
||||
- [米塞斯方法论](https://github.com/LijiayuDeng/mises-perspective) - 提炼路德维希·冯·米塞斯关于人类行为学、经济计算与干预主义批判的分析框架，形成可复用的政治经济学与制度分析方法论视角。
|
||||
- [MrBeast.skill](https://github.com/alchaincyf/mrbeast-skill) - 提炼 MrBeast 的内容选题、包装与观众留存方法，形成可复用的创作打法。
|
||||
- [芒格.skill](https://github.com/alchaincyf/munger-skill) - 提炼查理·芒格的跨学科心智模型与决策启发式，形成可复用的方法论框架。
|
||||
- [纳瓦尔.skill](https://github.com/alchaincyf/naval-skill) - 提炼纳瓦尔关于财富、杠杆与判断力的框架，形成可复用的方法论视角。
|
||||
- [PG.skill](https://github.com/alchaincyf/paul-graham-skill) - 提炼 Paul Graham 关于创业、写作与独立思考的框架，形成可复用的方法论视角。
|
||||
- [求是 Skill](https://github.com/HughYau/qiushi-skill) - 从相关思想方法中整理实事求是、调查研究与战略判断等工具，形成可复用的问题分析框架。
|
||||
- [罗布派克.skill](https://github.com/smallnest/rob-pike-skill) - 提炼 Rob Pike 在 Unix、Go 与工程设计中的技术判断与表达风格，形成可复用的方法论视角。
|
||||
- [内娱.skill](https://github.com/yanghaoraneve/star-skill) - 从歌词、视频、微博与评论中整理歌手或偶像的表达风格与互动方式，形成可对话的数字人格助手。
|
||||
- [乔布斯.skill](https://github.com/alchaincyf/steve-jobs-skill) - 提炼史蒂夫·乔布斯的产品判断、叙事风格与决策启发式，形成可复用的方法论框架。
|
||||
- [塔勒布.skill](https://github.com/alchaincyf/taleb-skill) - 提炼纳西姆·塔勒布关于反脆弱与风险的启发式，形成可复用的方法论框架。
|
||||
- [童锦程.skill](https://github.com/hotcoffeeshake/tong-jincheng-skill) - 提炼童锦程在人际关系与情感判断上的直白视角与启发式。
|
||||
- [特朗普.skill](https://github.com/alchaincyf/trump-skill) - 提炼特朗普的谈判、锚定与权力博弈分析框架，形成可复用的方法论视角。
|
||||
- [X 导师.skill](https://github.com/alchaincyf/x-mentor-skill) - 整合多位社交平台创作者的写作与增长打法，形成统一的导师式方法论技能。
|
||||
- [新青年.Skill](https://github.com/SamadhiFire/xinqingnian-skill) - 把“新中国最会解决问题的脑子”请来，当一次“临时参谋”。把《毛选》157篇文章进行蒸馏，将其方法论变成可执行的现实分析 skill。
|
||||
- [张一鸣.skill](https://github.com/alchaincyf/zhang-yiming-skill) - 提炼张一鸣的产品、组织与战略判断框架，形成可复用的方法论视角。
|
||||
- [张雪峰.skill](https://github.com/alchaincyf/zhangxuefeng-skill) - 提炼张雪峰在升学、考试与职业规划方面的实用框架，形成可复用的方法论视角。
|
||||
- [zizek-skill](https://github.com/JikunR/zizek-skill) - 以齐泽克式的问题意识整理前提追问、欲望追踪与矛盾揭示方法，形成可复用的分析工具。
|
||||
|
||||
## 精神性与专门化主题
|
||||
|
||||
- [赛博算命 Skill](https://github.com/jinchenma94/bazi-skill) - 基于出生信息与传统命理典籍整理四柱排盘与分析方法。
|
||||
- [金刚经.skill](https://github.com/dull-bird/diamond-sutra-skill) - 基于《金刚经》及相关解读整理佛学讲解框架，形成可对话的专门化技能。
|
||||
- [Master-skill](https://github.com/xr843/Master-skill) - 基于佛教经典文献整理汉传佛教的教学风格与讲解视角。
|
||||
- [Numerologist Skills](https://github.com/FANzR-arch/Numerologist_skills) - 用结构化知识库与脚本化约束整理奇门遁甲、紫微斗数等术数技能。
|
||||
- [月老·姻缘测算 Skills](https://github.com/Ming-H/yinyuan-skills) - 将姻缘测算整理为多模式传统术数技能，用于合婚、求签与桃花运势分析。
|
||||
|
||||
## 贡献
|
||||
|
||||
申请新增收录请先提交 issue 表单；维护者审核并添加 `approved` 标签后，工作流会自动生成 PR。
|
||||
|
||||
---
|
||||
title: "xixu-me/awesome-persona-distill-skills: 同事.skill, 女娲.skill, 前任.skill… Curated list of Agent Skills centered on people, relationships, commemorative scenes, and methodological perspectives"
|
||||
source: "https://github.com/xixu-me/awesome-persona-distill-skills"
|
||||
author:
|
||||
published:
|
||||
created: 2026-04-11
|
||||
description: "同事.skill, 女娲.skill, 前任.skill… Curated list of Agent Skills centered on people, relationships, commemorative scenes, and methodological perspectives - xixu-me/awesome-persona-distill-skills"
|
||||
tags:
|
||||
- "clippings"
|
||||
---
|
||||
## Awesome Persona Distill Skills
|
||||
|
||||
***[English](https://github.com/xixu-me/awesome-persona-distill-skills/blob/main/README.en.md)***
|
||||
|
||||
> [!tip] Tip
|
||||
> 欢迎加入“Xget 开源与 AI 交流群”，一起交流开源项目、AI 应用、工程实践、效率工具和独立开发；如果你也在做产品、写代码、折腾项目或者对开源和 AI 感兴趣，欢迎 [**进群**](https://file.xi-xu.me/QR%20Codes/%E7%BE%A4%E4%BA%8C%E7%BB%B4%E7%A0%81.png) 认识更多认真做事、乐于分享的朋友。
|
||||
|
||||
围绕人物、关系、纪念性场景与方法论视角的 [Agent Skills](https://agentskills.io/) 收录列表。
|
||||
|
||||
这里的“人格蒸馏”主要指从对话、作品、资料或数字痕迹中提炼表达风格、决策框架与交互方式，不默认等同于对真实个体的完整还原。
|
||||
|
||||
> [!note] Note
|
||||
> 条目按存储库名排序，主要为了便于检索与维护；列表顺序不代表推荐优先级、质量高低或重要性先后。
|
||||
|
||||
[](https://www.star-history.com/?repos=xixu-me%2Fawesome-persona-distill-skills&type=date&legend=top-left)
|
||||
|
||||
## 目录
|
||||
|
||||
- [自我蒸馏与元工具](#%E8%87%AA%E6%88%91%E8%92%B8%E9%A6%8F%E4%B8%8E%E5%85%83%E5%B7%A5%E5%85%B7)
|
||||
- [职场与学术关系](#%E8%81%8C%E5%9C%BA%E4%B8%8E%E5%AD%A6%E6%9C%AF%E5%85%B3%E7%B3%BB)
|
||||
- [亲密关系与家庭记忆](#%E4%BA%B2%E5%AF%86%E5%85%B3%E7%B3%BB%E4%B8%8E%E5%AE%B6%E5%BA%AD%E8%AE%B0%E5%BF%86)
|
||||
- [公众人物与方法论视角](#%E5%85%AC%E4%BC%97%E4%BA%BA%E7%89%A9%E4%B8%8E%E6%96%B9%E6%B3%95%E8%AE%BA%E8%A7%86%E8%A7%92)
|
||||
- [精神性与专门化主题](#%E7%B2%BE%E7%A5%9E%E6%80%A7%E4%B8%8E%E4%B8%93%E9%97%A8%E5%8C%96%E4%B8%BB%E9%A2%98)
|
||||
- [贡献](#%E8%B4%A1%E7%8C%AE)
|
||||
|
||||
## 自我蒸馏与元工具
|
||||
|
||||
- [反蒸馏 Skill](https://github.com/leilei926524-tech/anti-distill) - 将可公开分发的技能内容与私有经验备份拆分管理，用于技能交付场景。
|
||||
- [八字人格](https://github.com/cantian-ai/bazi-persona-skill) - 基于生辰八字，生成会聊天、有情绪、会随时间变化的AI人格。
|
||||
- [图鉴.skill](https://github.com/Aar0nPB/curator-skill) - 跨作者 persona skill 调度器 — 根据对话意图，从 30 个 persona skill 中智能匹配推荐。
|
||||
- [数字人生.skills](https://github.com/wildbyteai/digital-life) - 从个人在日常工具中留下的数字痕迹中提炼结构化自我画像。
|
||||
- [Forge Skill](https://github.com/YIKUAIBANZI/forge-skill) - 将自我蒸馏与他人蒸馏拆分为独立流程，用于自我镜像、记忆整理与角色化对话。
|
||||
- [永生.skill](https://github.com/agenmod/immortal-skill) - 从聊天记录与相关资料中整理多维数字人格画像。
|
||||
- [midas.skill](https://github.com/realteamprinz/midas-skill) - 从任意公众人物中提炼出六维度财富操作系统（赚钱引擎、交易架构、投资逻辑、风险画像、杠杆模型、退出路径），也可从个人日常数据中挖掘财富信号。
|
||||
- [数字生命开源计划](https://github.com/weixr18/my-digital-life) - 提供一套将个人知识库升级为数字分身的框架。
|
||||
- [女娲.skill](https://github.com/alchaincyf/nuwa-skill) - 从个人的心智模型、决策启发式与表达模式中提炼可复用技能。
|
||||
- [VibePortrait](https://github.com/dadwadw233/VibePortrait) - 从 Vibe Coding 对话中提炼开发者画像、开发技能与偏好。
|
||||
- [自己.skill](https://github.com/notdog1998/yourself-skill) - 将个人对话与记录整理为自我蒸馏助手。
|
||||
|
||||
## 职场与学术关系
|
||||
|
||||
- [老板.skill](https://github.com/vogtsw/boss-skills) - 从工作材料中提炼管理者的判断标准、评审风格与沟通预期。
|
||||
- [同事.skill](https://github.com/titanwings/colleague-skill) - 从团队资料中整理前同事的工作上下文、习惯与沟通方式。
|
||||
- [HR.skill](https://github.com/Schlaflied/hr-skill) - 从拒信与招聘流程中整理 HR 的沟通逻辑与决策模式，用于反向拆解筛选标准并重构求职叙事。
|
||||
- [大学老师.skill](https://github.com/CommitHu502Craft/professor-skill) - 从课程资料与教师风格中整理复习重点、题型偏好与评分线索。
|
||||
- [roast-cold-email-skill](https://github.com/Schlaflied/roast-cold-email-skill) - 从公司公开信息与招聘材料中整理批评性求职邮件写法，用于生成有理有据的冷联系求职邮件。
|
||||
- [师兄.skill](https://github.com/zhanghaichao520/senpai-skill) - 从课题组材料中提炼资深成员的指导方式与救火风格。
|
||||
- [导师.skill](https://github.com/ybq22/supervisor) - 将导师的指导风格整理为面向学生与教育工作者的导师助手。
|
||||
|
||||
## 亲密关系与家庭记忆
|
||||
|
||||
- [兄弟.skill](https://github.com/realteamprinz/brother-skill) - 从抖音、微信截图等来源蒸馏你的兄弟们（支持真实兄弟、群聊好友和网络红人）——他们的说话方式、口头禅、搞笑风格和恶搞能量。
|
||||
- [暗恋对象.skill](https://github.com/xiaoheizi8/crush-skills) - 从聊天、照片与社交痕迹中提炼对话风格，用于个人回望与情感整理。
|
||||
- [前任.skill](https://github.com/therealXiaomanChu/ex-skill) - 从私人记录中整理说话方式与共同记忆，用于回忆与关系梳理。
|
||||
- [MamaSkill](https://github.com/jiangziyan-693/MamaSkill) - 从亲人的聊天记录、信件与语音中整理纪念型家庭陪伴助手。
|
||||
- [父母.skill](https://github.com/xiaoheizi8/parents-skills) - 从个人材料中提炼父母的语气、习惯与家庭记忆。
|
||||
- [恋爱训练营.skill](https://github.com/TammyTan516/relationship-training-skill) - 基于聊天记录模拟心动对象的沟通风格，帮助用户在安全沙盒中练习表达、邀约与关系修复。
|
||||
- [Reunion Skill](https://github.com/yangdongchen66-boop/reunion-skill) - 基于已故亲友的数字遗物构建可本地运行的纪念型陪伴助手。
|
||||
|
||||
## 公众人物与方法论视角
|
||||
|
||||
- [巴菲特思维操作系统](https://github.com/will2025btc/buffett-perspective) - 提炼沃伦·巴菲特的投资与决策框架，形成可复用的方法论视角。
|
||||
- [常熟阿诺（加州盛亦陶） Skill](https://github.com/Ricardo-Vv/changshu-anuo) - 提炼常熟阿诺关于“左右脑互搏”的表达与分析视角，形成可复用的方法论框架。
|
||||
- [马斯克.skill](https://github.com/alchaincyf/elon-musk-skill) - 提炼埃隆·马斯克的第一性原理与产品思维，形成可复用的决策框架。
|
||||
- [峰哥亡命天涯 Skill](https://github.com/rottenpen/fengge-wangmingtianya-perspective) - 提炼“峰哥亡命天涯”的现实主义、止损导向与黑色幽默式表达结构，形成可复用的方法论视角。
|
||||
- [费曼.skill](https://github.com/alchaincyf/feynman-skill) - 提炼理查德·费曼的解释风格与求真启发式，形成可复用的方法论框架。
|
||||
- [郭德纲.skill](https://github.com/ByteRax/guodegang-skills) - 提炼郭德纲的表达结构、处世判断与职业方法，形成可复用的方法论视角。
|
||||
- [户晨风.skill](https://github.com/Janlaywss/hu-chenfeng-skill) - 提炼户晨风的消费现实主义视角，用于分析消费、城市与职业选择。
|
||||
- [Ilya.skill](https://github.com/alchaincyf/ilya-sutskever-skill) - 提炼 Ilya Sutskever 对规模化、研究突破与超级智能的判断框架，形成可复用的方法论视角。
|
||||
- [KarlMarx Skill](https://github.com/baojiachen0214/karlmarx-skill) - 提炼马克思主义的结构分析、矛盾分析与实践检验方法，形成用于深层问题分析的方法论框架。
|
||||
- [Karpathy.skill](https://github.com/alchaincyf/karpathy-skill) - 提炼 Andrej Karpathy 对 AI 工程、教育与研究的思考框架，形成可复用的方法论视角。
|
||||
- [liangxi-skills](https://github.com/1sh1ro/liangxi-skills) - 从公开可见的 X 内容与交易复盘中提炼凉兮的结构判断、风险习惯与中文交易表达，形成可复用的交易方法论视角。
|
||||
- [毛泽东.skill](https://github.com/wwwaapplleecu-source/mao-skill) - 基于公开著作提炼毛泽东的思想框架与方法论视角。
|
||||
- [毛选.skill](https://github.com/leezythu/maoxuan-skill) - 提炼《毛选》中的矛盾分析、根据地思维与战略判断框架，形成可复用的方法论视角。
|
||||
- [米塞斯方法论](https://github.com/LijiayuDeng/mises-perspective) - 提炼路德维希·冯·米塞斯关于人类行为学、经济计算与干预主义批判的分析框架，形成可复用的政治经济学与制度分析方法论视角。
|
||||
- [MrBeast.skill](https://github.com/alchaincyf/mrbeast-skill) - 提炼 MrBeast 的内容选题、包装与观众留存方法，形成可复用的创作打法。
|
||||
- [芒格.skill](https://github.com/alchaincyf/munger-skill) - 提炼查理·芒格的跨学科心智模型与决策启发式，形成可复用的方法论框架。
|
||||
- [纳瓦尔.skill](https://github.com/alchaincyf/naval-skill) - 提炼纳瓦尔关于财富、杠杆与判断力的框架，形成可复用的方法论视角。
|
||||
- [PG.skill](https://github.com/alchaincyf/paul-graham-skill) - 提炼 Paul Graham 关于创业、写作与独立思考的框架，形成可复用的方法论视角。
|
||||
- [求是 Skill](https://github.com/HughYau/qiushi-skill) - 从相关思想方法中整理实事求是、调查研究与战略判断等工具，形成可复用的问题分析框架。
|
||||
- [罗布派克.skill](https://github.com/smallnest/rob-pike-skill) - 提炼 Rob Pike 在 Unix、Go 与工程设计中的技术判断与表达风格，形成可复用的方法论视角。
|
||||
- [内娱.skill](https://github.com/yanghaoraneve/star-skill) - 从歌词、视频、微博与评论中整理歌手或偶像的表达风格与互动方式，形成可对话的数字人格助手。
|
||||
- [乔布斯.skill](https://github.com/alchaincyf/steve-jobs-skill) - 提炼史蒂夫·乔布斯的产品判断、叙事风格与决策启发式，形成可复用的方法论框架。
|
||||
- [塔勒布.skill](https://github.com/alchaincyf/taleb-skill) - 提炼纳西姆·塔勒布关于反脆弱与风险的启发式，形成可复用的方法论框架。
|
||||
- [童锦程.skill](https://github.com/hotcoffeeshake/tong-jincheng-skill) - 提炼童锦程在人际关系与情感判断上的直白视角与启发式。
|
||||
- [特朗普.skill](https://github.com/alchaincyf/trump-skill) - 提炼特朗普的谈判、锚定与权力博弈分析框架，形成可复用的方法论视角。
|
||||
- [X 导师.skill](https://github.com/alchaincyf/x-mentor-skill) - 整合多位社交平台创作者的写作与增长打法，形成统一的导师式方法论技能。
|
||||
- [新青年.Skill](https://github.com/SamadhiFire/xinqingnian-skill) - 把“新中国最会解决问题的脑子”请来，当一次“临时参谋”。把《毛选》157篇文章进行蒸馏，将其方法论变成可执行的现实分析 skill。
|
||||
- [张一鸣.skill](https://github.com/alchaincyf/zhang-yiming-skill) - 提炼张一鸣的产品、组织与战略判断框架，形成可复用的方法论视角。
|
||||
- [张雪峰.skill](https://github.com/alchaincyf/zhangxuefeng-skill) - 提炼张雪峰在升学、考试与职业规划方面的实用框架，形成可复用的方法论视角。
|
||||
- [zizek-skill](https://github.com/JikunR/zizek-skill) - 以齐泽克式的问题意识整理前提追问、欲望追踪与矛盾揭示方法，形成可复用的分析工具。
|
||||
|
||||
## 精神性与专门化主题
|
||||
|
||||
- [赛博算命 Skill](https://github.com/jinchenma94/bazi-skill) - 基于出生信息与传统命理典籍整理四柱排盘与分析方法。
|
||||
- [金刚经.skill](https://github.com/dull-bird/diamond-sutra-skill) - 基于《金刚经》及相关解读整理佛学讲解框架，形成可对话的专门化技能。
|
||||
- [Master-skill](https://github.com/xr843/Master-skill) - 基于佛教经典文献整理汉传佛教的教学风格与讲解视角。
|
||||
- [Numerologist Skills](https://github.com/FANzR-arch/Numerologist_skills) - 用结构化知识库与脚本化约束整理奇门遁甲、紫微斗数等术数技能。
|
||||
- [月老·姻缘测算 Skills](https://github.com/Ming-H/yinyuan-skills) - 将姻缘测算整理为多模式传统术数技能，用于合婚、求签与桃花运势分析。
|
||||
|
||||
## 贡献
|
||||
|
||||
申请新增收录请先提交 issue 表单；维护者审核并添加 `approved` 标签后，工作流会自动生成 PR。
|
||||
|
||||
如果你是在修复现有条目、文档或失效链接，仍可直接提交 PR。具体约定见 [`CONTRIBUTING.md`](https://github.com/xixu-me/awesome-persona-distill-skills/blob/main/CONTRIBUTING.md) 。
|
||||
@@ -1,104 +1,104 @@
|
||||
---
|
||||
title: 一人公司 (OPC) 创业必备的 9 个 Agent Skills
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
---
|
||||
|
||||
# 一人公司 (OPC) 创业必备的 9 个 Agent Skills
|
||||
|
||||
**作者:** 邵猛
|
||||
**来源:** https://mp.weixin.qq.com/s/bOLAmBBDPNMppktXirT_og
|
||||
**公众号:** AI 启蒙小伙伴
|
||||
**日期:** 2026年3月25日 07:50
|
||||
**标签:** Agent、创业、一人公司、极简创业
|
||||
|
||||
---
|
||||
|
||||
Gumroad 创始人 Sahil Lavingia 把他的著名书籍「The Minimalist Entrepreneur」中的极简创业哲学封装为 9 个 Agent Skills，让 Agent 做可交互的 AI 创业教练！
|
||||
|
||||
开源地址：https://github.com/slavingia/skills
|
||||
|
||||
这 9 个 skills 串起来，其实对应一条非常清晰的路径：
|
||||
|
||||
1. 先找社区，不先找产品。
|
||||
2. 先验证需求，不先写代码。
|
||||
3. 先手工交付，再流程化，再产品化。
|
||||
4. 先一个个卖出去，再考虑放大。
|
||||
5. 从第一天就收费。
|
||||
6. 营销建立在销售经验和客户理解之上。
|
||||
7. 增长以盈利和可持续为前提。
|
||||
8. 在招人之前先定义文化。
|
||||
9. 所有决策都回到"极简创业"原则复盘。
|
||||
|
||||
---
|
||||
|
||||
## 1. Find Community /find-community
|
||||
|
||||
它是整个方法论的起点，核心不是"找赛道"，而是"识别你已经属于哪些群体"。prompt 会引导用户盘点自己真实参与的社区、长期出没的平台、反复听到的抱怨，以及哪些人群值得长期服务。它的重要性在于把创业起点从"我想做什么"转成"我理解谁、我能为谁持续提供价值"。这一步决定后面是不是在真问题上创业，而不是在想象中的市场上创业。
|
||||
|
||||
## 2. Validate Idea /find-community
|
||||
|
||||
这个 skill 的重点是把"验证"定义为"能不能卖出去"，而不是"有没有人说想要"。它会逼用户回答：谁有这个问题、现在怎么解决、痛点到底有多强、能不能先手工服务、有没有至少若干潜在付费者。它的价值在于强行切断"做完再看"的惯性，把验证标准从兴趣反馈改成交易信号。对一人公司尤其关键，因为资源最怕浪费在错误假设上。
|
||||
|
||||
## 3. MVP /mvp
|
||||
|
||||
这个 skill 不是在教人"做一个简陋产品"，而是在强调三阶段：手工完成、流程化、产品化。也就是先靠人交付价值，再把流程写清楚，最后才决定自动化哪一部分。仓库里还明确写到，大多数 MVP 本质上不过是 forms and lists，也就是极简 CRUD。它要纠正的是很多独立开发者最常见的问题：把 MVP 做成"半个完整版"，结果上线太晚、反馈太慢、范围失控。
|
||||
|
||||
## 4. First Customers /first-customers
|
||||
|
||||
它把早期增长拆成三层同心圆：亲友、社区、陌生人。这个设计很有代表性，因为它反对"发布即增长"的幻想，更强调逐个销售、逐个对话、逐个打磨表述。skill 中甚至给了冷启动邮件的具体范式，说明它把销售视为学习过程，而不是压迫式转化。对于 OPC 来说，这一套很实用，因为前 100 个客户本来就更像"深度获取"而不是"规模投放"。
|
||||
|
||||
## 5. Pricing /pricing
|
||||
|
||||
这个 skill 的中心思想很明确：一定要收费，而且越早越好。它把定价分为成本导向和价值导向两类，再引导用户去算生存所需收入、所需客户数、以及达到财务独立的大致路径。它的重要意义不只是"给一个价格"，而是把定价变成商业模式校准工具。很多一人公司表面上产品做出来了，实质上没有经济闭环，这个 skill 就是在尽早暴露这个问题。
|
||||
|
||||
## 6. Marketing Plan /marketing-plan
|
||||
|
||||
这里的前提非常重要：先有产品市场契合迹象，大约先有 100 个客户，再谈营销。它把营销定义为"规模化销售"，而不是广告投放；把内容分成 educate、inspire、entertain 三层；同时强调邮箱名单比平台粉丝更重要。也就是说，它并不把营销理解为做声量，而是做可持续获客资产。对于小团队而言，这比一开始就烧钱投放更符合现实。
|
||||
|
||||
## 7. Grow Sustainably /grow-sustainably
|
||||
|
||||
这是整套体系里最"经营者思维"的一个 skill。它的核心不是增长率，而是盈利能力、现金流安全和创始人精力管理。prompt 会引导用户区分可变成本和固定成本，警惕过早招聘、办公室、昂贵地区和不可逆支出，同时强调"hire software, not humans""default alive or default dead"。它的价值在于把"活下去"上升为战略能力，而不是保守姿态。
|
||||
|
||||
## 8. Company Values /company-values
|
||||
|
||||
这不是传统 HR 意义上的价值观模板，而是要求创始人在招人之前先说清楚：什么行为是被奖励的，什么行为即使有业绩也不能接受。仓库里还拿 Gumroad 的价值观做例子，比如 Judged by the Work、Everyone is a CEO、Dare to Be Open。它真正解决的问题是，一人公司只要准备迈向多人协作，文化就不能再靠创始人临场判断，而要开始具备"可传递性"。
|
||||
|
||||
## 9. Minimalist Review /minimalist-review
|
||||
|
||||
这个 skill 更像总开关或审议器。无论是做新功能、投广告、招人、融资还是扩品类，它都会从社区、手工优先、最小构建、先卖后扩、时间优先于金钱、盈利性、客户驱动、价值观一致性等维度做复盘。它的作用不是产出新策略，而是防止创业者在压力、焦虑或虚荣中偏离方法论。某种意义上，这是 8 个 skills 的统一校验层。
|
||||
|
||||
---
|
||||
|
||||
## 实现方式
|
||||
|
||||
每个 Skill 的实现方式高度一致：在 `skills/` 目录下对应一个子文件夹，内含 `SKILL.md` 文件。该文件采用 YAML 前置元数据 + 结构化系统提示（system prompt）的形式，指导 Claude 扮演"极简创业哲学顾问"。
|
||||
|
||||
以 `/find-community` 为例，提示明确要求：
|
||||
|
||||
- 核心原则：先找社区，再找问题，而非先想产品；
|
||||
- 框架：4 个引导问题 + 4 项评估标准；
|
||||
- 反模式警示 + 输出模板（社区、痛点、用户连接度、聚集地）。
|
||||
|
||||
---
|
||||
|
||||
## 这 9 个 Skills 的整体价值
|
||||
|
||||
如果从产品形态看，这个项目很轻；但如果从方法论封装看，它很完整。
|
||||
|
||||
它的价值主要体现在四点：
|
||||
|
||||
1. 它把一本书的抽象理念变成了可反复调用的决策接口，降低了创始人在不同阶段"该怎么想"的切换成本。
|
||||
2. 它非常适合一人公司或极小团队，因为几乎每个 skill 都在主动压制过度建设、过早扩张和虚荣型决策。
|
||||
3. 它不是单点建议，而是一条连续路径：社区 -> 验证 -> MVP -> 销售 -> 定价 -> 营销 -> 增长 -> 文化 -> 复盘。
|
||||
4. 它把 AI 的角色设定得很克制，不是假装替你创业，而是持续把你拉回到更现实、更节制的判断框架里。
|
||||
|
||||
---
|
||||
|
||||
## References
|
||||
|
||||
- https://github.com/slavingia/skills
|
||||
---
|
||||
title: 一人公司 (OPC) 创业必备的 9 个 Agent Skills
|
||||
source:
|
||||
author: shenwei
|
||||
published:
|
||||
created:
|
||||
description:
|
||||
tags: []
|
||||
---
|
||||
|
||||
# 一人公司 (OPC) 创业必备的 9 个 Agent Skills
|
||||
|
||||
**作者:** 邵猛
|
||||
**来源:** https://mp.weixin.qq.com/s/bOLAmBBDPNMppktXirT_og
|
||||
**公众号:** AI 启蒙小伙伴
|
||||
**日期:** 2026年3月25日 07:50
|
||||
**标签:** Agent、创业、一人公司、极简创业
|
||||
|
||||
---
|
||||
|
||||
Gumroad 创始人 Sahil Lavingia 把他的著名书籍「The Minimalist Entrepreneur」中的极简创业哲学封装为 9 个 Agent Skills，让 Agent 做可交互的 AI 创业教练！
|
||||
|
||||
开源地址：https://github.com/slavingia/skills
|
||||
|
||||
这 9 个 skills 串起来，其实对应一条非常清晰的路径：
|
||||
|
||||
1. 先找社区，不先找产品。
|
||||
2. 先验证需求，不先写代码。
|
||||
3. 先手工交付，再流程化，再产品化。
|
||||
4. 先一个个卖出去，再考虑放大。
|
||||
5. 从第一天就收费。
|
||||
6. 营销建立在销售经验和客户理解之上。
|
||||
7. 增长以盈利和可持续为前提。
|
||||
8. 在招人之前先定义文化。
|
||||
9. 所有决策都回到"极简创业"原则复盘。
|
||||
|
||||
---
|
||||
|
||||
## 1. Find Community /find-community
|
||||
|
||||
它是整个方法论的起点，核心不是"找赛道"，而是"识别你已经属于哪些群体"。prompt 会引导用户盘点自己真实参与的社区、长期出没的平台、反复听到的抱怨，以及哪些人群值得长期服务。它的重要性在于把创业起点从"我想做什么"转成"我理解谁、我能为谁持续提供价值"。这一步决定后面是不是在真问题上创业，而不是在想象中的市场上创业。
|
||||
|
||||
## 2. Validate Idea /find-community
|
||||
|
||||
这个 skill 的重点是把"验证"定义为"能不能卖出去"，而不是"有没有人说想要"。它会逼用户回答：谁有这个问题、现在怎么解决、痛点到底有多强、能不能先手工服务、有没有至少若干潜在付费者。它的价值在于强行切断"做完再看"的惯性，把验证标准从兴趣反馈改成交易信号。对一人公司尤其关键，因为资源最怕浪费在错误假设上。
|
||||
|
||||
## 3. MVP /mvp
|
||||
|
||||
这个 skill 不是在教人"做一个简陋产品"，而是在强调三阶段：手工完成、流程化、产品化。也就是先靠人交付价值，再把流程写清楚，最后才决定自动化哪一部分。仓库里还明确写到，大多数 MVP 本质上不过是 forms and lists，也就是极简 CRUD。它要纠正的是很多独立开发者最常见的问题：把 MVP 做成"半个完整版"，结果上线太晚、反馈太慢、范围失控。
|
||||
|
||||
## 4. First Customers /first-customers
|
||||
|
||||
它把早期增长拆成三层同心圆：亲友、社区、陌生人。这个设计很有代表性，因为它反对"发布即增长"的幻想，更强调逐个销售、逐个对话、逐个打磨表述。skill 中甚至给了冷启动邮件的具体范式，说明它把销售视为学习过程，而不是压迫式转化。对于 OPC 来说，这一套很实用，因为前 100 个客户本来就更像"深度获取"而不是"规模投放"。
|
||||
|
||||
## 5. Pricing /pricing
|
||||
|
||||
这个 skill 的中心思想很明确：一定要收费，而且越早越好。它把定价分为成本导向和价值导向两类，再引导用户去算生存所需收入、所需客户数、以及达到财务独立的大致路径。它的重要意义不只是"给一个价格"，而是把定价变成商业模式校准工具。很多一人公司表面上产品做出来了，实质上没有经济闭环，这个 skill 就是在尽早暴露这个问题。
|
||||
|
||||
## 6. Marketing Plan /marketing-plan
|
||||
|
||||
这里的前提非常重要：先有产品市场契合迹象，大约先有 100 个客户，再谈营销。它把营销定义为"规模化销售"，而不是广告投放；把内容分成 educate、inspire、entertain 三层；同时强调邮箱名单比平台粉丝更重要。也就是说，它并不把营销理解为做声量，而是做可持续获客资产。对于小团队而言，这比一开始就烧钱投放更符合现实。
|
||||
|
||||
## 7. Grow Sustainably /grow-sustainably
|
||||
|
||||
这是整套体系里最"经营者思维"的一个 skill。它的核心不是增长率，而是盈利能力、现金流安全和创始人精力管理。prompt 会引导用户区分可变成本和固定成本，警惕过早招聘、办公室、昂贵地区和不可逆支出，同时强调"hire software, not humans""default alive or default dead"。它的价值在于把"活下去"上升为战略能力，而不是保守姿态。
|
||||
|
||||
## 8. Company Values /company-values
|
||||
|
||||
这不是传统 HR 意义上的价值观模板，而是要求创始人在招人之前先说清楚：什么行为是被奖励的，什么行为即使有业绩也不能接受。仓库里还拿 Gumroad 的价值观做例子，比如 Judged by the Work、Everyone is a CEO、Dare to Be Open。它真正解决的问题是，一人公司只要准备迈向多人协作，文化就不能再靠创始人临场判断，而要开始具备"可传递性"。
|
||||
|
||||
## 9. Minimalist Review /minimalist-review
|
||||
|
||||
这个 skill 更像总开关或审议器。无论是做新功能、投广告、招人、融资还是扩品类，它都会从社区、手工优先、最小构建、先卖后扩、时间优先于金钱、盈利性、客户驱动、价值观一致性等维度做复盘。它的作用不是产出新策略，而是防止创业者在压力、焦虑或虚荣中偏离方法论。某种意义上，这是 8 个 skills 的统一校验层。
|
||||
|
||||
---
|
||||
|
||||
## 实现方式
|
||||
|
||||
每个 Skill 的实现方式高度一致：在 `skills/` 目录下对应一个子文件夹，内含 `SKILL.md` 文件。该文件采用 YAML 前置元数据 + 结构化系统提示（system prompt）的形式，指导 Claude 扮演"极简创业哲学顾问"。
|
||||
|
||||
以 `/find-community` 为例，提示明确要求：
|
||||
|
||||
- 核心原则：先找社区，再找问题，而非先想产品；
|
||||
- 框架：4 个引导问题 + 4 项评估标准；
|
||||
- 反模式警示 + 输出模板（社区、痛点、用户连接度、聚集地）。
|
||||
|
||||
---
|
||||
|
||||
## 这 9 个 Skills 的整体价值
|
||||
|
||||
如果从产品形态看，这个项目很轻；但如果从方法论封装看，它很完整。
|
||||
|
||||
它的价值主要体现在四点：
|
||||
|
||||
1. 它把一本书的抽象理念变成了可反复调用的决策接口，降低了创始人在不同阶段"该怎么想"的切换成本。
|
||||
2. 它非常适合一人公司或极小团队，因为几乎每个 skill 都在主动压制过度建设、过早扩张和虚荣型决策。
|
||||
3. 它不是单点建议，而是一条连续路径：社区 -> 验证 -> MVP -> 销售 -> 定价 -> 营销 -> 增长 -> 文化 -> 复盘。
|
||||
4. 它把 AI 的角色设定得很克制，不是假装替你创业，而是持续把你拉回到更现实、更节制的判断框架里。
|
||||
|
||||
---
|
||||
|
||||
## References
|
||||
|
||||
- https://github.com/slavingia/skills
|
||||
|
||||
Reference in New Issue
Block a user