菜单
Set up a reef server with example services. Use when bootstrapping a new reef instance or adding fleet coordination services to an existing one.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/hdresearch/reef --skill setup命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | setup |
| description | Set up a reef server with example services. Use when bootstrapping a new reef instance or adding fleet coordination services to an existing one. |
Reef ships with core infrastructure services in services/ (including vm-tree, signals, swarm, lieutenant, usage, probe, docs, installer, services, store, cron, ui). Optional example services live in examples/services/ and can be copied into services/ if you want them.
| Service | What it does |
|---|---|
| board | Task tracking with review workflow, notes, artifacts, priority bumps |
| feed | Activity event stream with SSE, auto-publishes from board events |
| log | Append-only work log with time-range queries |
| journal | Personal narrative log with mood/vibe tagging |
| commits | VM snapshot ledger for tracking golden images |
| reports | Markdown reports with title, author, tags |
| usage | Cost & token tracking with per-agent summaries (depends on feed) |
| updater | Auto-update reef from npm |
Some services depend on others. Install dependencies first:
To install everything:
cp -r examples/services/feed services/feed
cp -r examples/services/board services/board
cp -r examples/services/log services/log
cp -r examples/services/journal services/journal
cp -r examples/services/commits services/commits
cp -r examples/services/reports services/reports
cp -r examples/services/usage services/usage
cp -r examples/services/updater services/updater
Then restart or reload:
curl -X POST http://localhost:3000/services/reload -H "Authorization: Bearer $TOKEN"
Pick what you need. A minimal coordination setup:
# Task tracking + activity feed
cp -r examples/services/feed services/feed
cp -r examples/services/board services/board
# Work log
cp -r examples/services/log services/log
# Web dashboard is built-in at services/ui — no copy needed
Reload:
curl -X POST http://localhost:3000/services/reload -H "Authorization: Bearer $TOKEN"
The example services import types from ../src/core/types.js (relative to examples/services/). After copying to services/, the import path resolves to services/src/core/types.js which doesn't exist.
You must fix the imports in each copied service. Change:
// Before (in examples/services/)
import type { ServiceModule } from "../src/core/types.js";
// After (in services/)
import type { ServiceModule } from "../../src/core/types.js";
Run this to fix all imports at once after copying:
find services/ -name '*.ts' -exec sed -i '' 's|from "../src/core/|from "../../src/core/|g' {} +
find services/ -name '*.ts' -exec sed -i '' 's|from "\.\./src/core/|from "../../src/core/|g' {} +
On Linux (no -i ''):
find services/ -name '*.ts' -exec sed -i 's|from "../src/core/|from "../../src/core/|g' {} +
After copying and fixing imports:
# Check the server starts
bun run start
# Or check health
curl http://localhost:3000/health
The health endpoint lists all loaded services. Every service you copied should appear.
Instead of copying, you can use the installer to symlink from examples:
curl -X POST http://localhost:3000/installer/install \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{"source": "./examples/services/board"}'
This creates a symlink — changes to the example source are reflected immediately. Good for development, but the import path issue still applies if examples use relative paths to src/core/.
examples/services/ to services/../src/core/ → ../../src/core/)GET /healthGET /docs shows routes for each new service