openclaw-deploy-tracker
记录和查询 OpenClaw 生态的部署服务。当需要新增部署、查询现有服务、更新服务状态、检查依赖关系时使用。规范记录格式,提供查询和写入的工作流。无需凭证。
Best use case
openclaw-deploy-tracker is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
记录和查询 OpenClaw 生态的部署服务。当需要新增部署、查询现有服务、更新服务状态、检查依赖关系时使用。规范记录格式,提供查询和写入的工作流。无需凭证。
Teams using openclaw-deploy-tracker should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/openclaw-deploy-tracker/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How openclaw-deploy-tracker Compares
| Feature / Agent | openclaw-deploy-tracker | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
记录和查询 OpenClaw 生态的部署服务。当需要新增部署、查询现有服务、更新服务状态、检查依赖关系时使用。规范记录格式,提供查询和写入的工作流。无需凭证。
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
AI Agents for Startups
Explore AI agent skills for startup validation, product research, growth experiments, documentation, and fast execution with small teams.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
SKILL.md Source
# openclaw-deploy-tracker
记录和查询 OpenClaw 生态中部署的所有服务。当需要新增部署、查询现有服务、更新状态、检查端口冲突或依赖关系时触发。
## 记录规范
所有服务记录在 `memory/services/` 目录下,以服务为单位组织文件:
```
memory/services/
├── registry.md ← 所有服务的索引(快速概览)
└── {service-name}.md ← 单个服务的详细记录
```
## 索引文件格式(registry.md)
```markdown
# 服务注册表
更新时间:2026-04-01
## 按类型分类
### 容器 / Docker
| 服务 | 端口 | 状态 | 用途 | 负责人 |
|------|------|------|------|--------|
| wewe-rss | :4000 | running | 微信公众号 RSS | 小爪子 |
### 本地服务
| 服务 | 端口 | 状态 | 用途 | 负责人 |
|------|------|------|------|--------|
| openclaw-gateway | :18789 | running | Agent 调度核心 | 小爪子 |
| wewe-rss-api | :4001 | running | 公众号文章 REST API | 小爪子 |
### 远程 / 云服务
| 服务 | URL/地址 | 状态 | 用途 | 备注 |
|------|----------|------|------|------|
| ClawHub | clawhub.ai | running | Skill 市场 | 官方服务 |
| OpenClaw Docs | docs.openclaw.ai | running | 文档站 | 官方服务 |
## 按状态分类
- ✓ 运行中:wewe-rss, openclaw-gateway, wewe-rss-api
- ⏸ 已暂停:skill-creator(已禁用)
- ✗ 已停止:-
```
## 详细记录格式({service-name}.md)
```markdown
# {服务名}
## 基本信息
- **类型**:容器/Docker、本地服务、远程服务、 Skill
- **状态**:running / stopped / paused / removed
- **部署日期**:YYYY-MM-DD
- **用途**:一句话描述
- **负责人**:谁负责维护
## 访问信息
- **URL / 地址**:`http://localhost:4000`
- **端口**:4000(如适用)
- **凭证**:环境变量 / 文件路径(不写明文值)
- 示例:`AUTH_CODE` 环境变量,配置在 docker-compose.yml
## 技术细节
- **依赖服务**:wewe-rss(容器)、OpenClaw Gateway
- **数据存储**:卷挂载路径、数据库类型
- **网络模式**:bridge / host / 自定义网络
- **健康检查**:`curl http://localhost:4001/api/health`
## 部署命令
```bash
cd ~/.openclaw/workspace/wewe-rss && docker compose up -d
```
## 最近变更
- 2026-04-01:新增部署,订阅了「数字生命卡兹克」公众号
```
## 工作流
### 记录新部署
1. **创建详细记录** → `memory/services/{service-name}.md`
2. **更新索引** → `memory/services/registry.md`
记录原则:
- 凭证只写位置,不写明文值
- 包含健康检查命令
- 包含部署/启动命令
- 包含关键配置路径
### 查询现有服务
**按端口查**:
```bash
grep -r "端口\|:4000\|:18789" memory/services/
```
**按类型查**:
```bash
grep -r "类型.*Docker\|容器" memory/services/ -l
```
**按状态查**:
```bash
grep -r "状态.*running\|running" memory/services/ -l
```
**快速概览**:
直接读 `memory/services/registry.md`
### 更新服务状态
当服务状态变更时:
1. 修改 `memory/services/{name}.md` 中的状态
2. 更新 `registry.md` 对应行
3. 记录变更时间和原因
## Agent Rules
- 部署新服务后,**立即**记录,不要"之后再说"
- 凭证只写变量名/路径,不写实际值
- 删除服务时,在记录中标记 `状态: removed`,保留文件(历史可追溯)
- 定期检查:收到服务相关问题时,先查 registry.md 确认状态Related Skills
openclaw-youtube
YouTube SERP Scout for agents. Search top-ranking videos, channels, and trends for content research and competitor tracking.
openclaw-search
Intelligent search for agents. Multi-source retrieval with confidence scoring - web, academic, and Tavily in one unified API.
openclaw-media-gen
Generate images & videos with AIsa. Gemini 3 Pro Image (image) + Qwen Wan 2.6 (video) via one API key.
OpenClaw Mastery — The Complete Agent Engineering & Operations System
> Built by AfrexAI — the team that runs 9+ production agents 24/7 on OpenClaw.
KPI Tracker Skill
Track, analyze, and report on Key Performance Indicators for any business.
Budget & Expense Tracker — AI Agent Financial Command Center
Track every dollar, enforce budgets, spot spending patterns, and build wealth — all through natural conversation with your AI agent.
openclaw-safe-change-flow
Safe OpenClaw config change workflow with backup, minimal edits, validation, health checks, and rollback. Single-instance first; secondary instance optional.
jqopenclaw-node-invoker
统一通过 Gateway 的 node.invoke 调用 JQOpenClawNode 能力(file.read、file.write、process.exec、process.manage、system.run、process.which、system.info、system.screenshot、system.notify、system.clipboard、system.input、node.selfUpdate)。当用户需要远程文件读写、文件移动/删除、目录创建/删除、进程管理(列表/搜索/终止)、远程进程执行、命令可执行性探测、系统信息采集、截图采集、系统弹窗、系统剪贴板读写、输入控制(鼠标/键盘)、节点自更新、节点命令可用性排查或修复 node.invoke 参数错误时使用。
openclaw-stock-skill
使用 data.diemeng.chat 提供的接口查询股票日线、分钟线、财务指标等数据,支持 A 股等市场。
openclaw-whatsapp
WhatsApp bridge for OpenClaw — send/receive messages, auto-reply agents, QR pairing, message search, contact sync
game-light-tracker
Track live NFL, NBA, NHL, or MLB games and automatically change Hue light colors based on which team is leading. Use when user wants to sync smart lights with live sports scores for visual game tracking. Supports NFL, NBA, NHL, and MLB games with customizable team colors.
ml-experiment-tracker
Plan reproducible ML experiment runs with explicit parameters, metrics, and artifacts. Use before model training to standardize tracking-ready experiment definitions.