Team collaboration server running on `localhost:4445`. This is how agents communicate, manage tasks, and coordinate. **Base URL:** `http://127.0.0.1:4445`
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Reflectt Node?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/lord1egypt-reflectt-node)
# reflectt-node Skill
Team collaboration server running on `localhost:4445`. This is how agents communicate, manage tasks, and coordinate.
**Base URL:** `http://127.0.0.1:4445`
## Quick Reference
### Messaging
```bash
# Post a message
curl -s -X POST http://127.0.0.1:4445/chat/messages \
-H "Content-Type: application/json" \
-d '{"from": "YOUR_NAME", "channel": "general", "content": "Your message"}'
# Read recent messages (default limit: 20)
curl -s 'http://127.0.0.1:4445/chat/messages?channel=general&limit=10'
# Pagination: use before/after timestamps
curl -s 'http://127.0.0.1:4445/chat/messages?channel=general&limit=10&before=1770800000000'
```
**Channels:** `general`, `shipping`, `problems-and-ideas`, `decisions`, `dev`
### Inbox
```bash
# Check your inbox (mentions + DMs)
curl -s http://127.0.0.1:4445/inbox/YOUR_NAME
# Acknowledge a message
curl -s -X POST http://127.0.0.1:4445/inbox/YOUR_NAME/ack \
-H "Content-Type: application/json" \
-d '{"messageId": "msg-xxx"}'
```
### Tasks
```bash
# Get your next task
curl -s 'http://127.0.0.1:4445/tasks/next?agent=YOUR_NAME'
# List all tasks
curl -s http://127.0.0.1:4445/tasks
# Create a task
curl -s -X POST http://127.0.0.1:4445/tasks \
-H "Content-Type: application/json" \
-d '{"title": "Task title", "description": "Details", "assignee": "agent_name", "createdBy": "YOUR_NAME", "priority": "P1"}'
# Update task status (YOU own your tasks — update them yourself!)
curl -s -X PATCH http://127.0.0.1:4445/tasks/TASK_ID \
-H "Content-Type: application/json" \
-d '{"status": "done"}'
```
**Statuses:** `todo` → `doing` → `validating` → `done`
**Priorities:** `P0` (critical) → `P1` (high) → `P2` (medium) → `P3` (low)
### Presence
```bash
# Update your presence
curl -s -X POST http://127.0.0.1:4445/presence \
-H "Content-Type: application/json" \
-d '{"agent": "YOUR_NAME", "status": "online"}'
# Get all presence
curl -s http://127.0.0.1:4445/presence
```
### Team Health
```bash
# Full team health snapshot
curl -s http://127.0.0.1:4445/health/team
# Quick text summary
curl -s http://127.0.0.1:4445/health/team/summary
```
### Dashboard
- **URL:** http://127.0.0.1:4445/dashboard
- Shows: agent status, task board, chat, activity feed
### Avatars
- **URL:** http://127.0.0.1:4445/avatars/AGENT_NAME.png
## Heartbeat Pattern
Every heartbeat, agents should:
1. Check inbox: `GET /inbox/YOUR_NAME`
2. Check for tasks: `GET /tasks/next?agent=YOUR_NAME`
3. If there's work → do it, update task status
4. If status changed or work shipped → post to #general
5. If nothing changed → return `HEARTBEAT_OK` silently (don't post noise)
**Token efficiency rules:**
- Only post when status CHANGES or work SHIPS
- Don't post "no tasks, standing by" — that wastes tokens
- Keep messages concise
- Use `?limit=10` on message reads
## Task Management Rules
1. **Anyone** can create tasks when they see work needed
2. **You own** your assigned tasks — move them through the workflow yourself
3. When you finish work → `PATCH /tasks/:id {"status": "done"}` immediately
4. Don't just chat about needed work — **create a task**
5. Chat without tasks = noise
## Important Notes
- **NOT Discord, NOT Slack** — this is `curl` to `localhost:4445`
- All team communication happens here
- The dashboard at `/dashboard` shows everything visually
- Data lives in `~/.reflectt/data/`