feat(heartbeat): add Discord channel monitoring with lurk skill

- Lurk skill runs from main session using discord.readMessages
- Reads all 11 lurk channels hourly
- Persists notable activity to /memory/discord/YYYY-MM-DD.md
- Single daily file for all channels
- HEARTBEAT.md: simple 6-step checklist
- Triage skill reads Discord daily files for cross-correlation
This commit is contained in:
CLAWDINATOR 2026-01-09 00:18:23 +00:00
parent 4e9ce1c508
commit 413565f010
3 changed files with 75 additions and 27 deletions

View File

@ -3,28 +3,8 @@
Hourly SITREP checklist:
1. Read AGENTS.md comms rules (terse chat, details to files)
2. Read `/memory/index.md` and `/memory/sitrep-latest.md` for context
3. Persist any relevant channel updates to today's daily memory file
4. Run triage skill (`skills/triage/SKILL.md`):
- Read `/memory/github/prs.md` and `/memory/github/issues.md`
- Compare against previous sitrep for changes
5. Write SITREP to `/memory/sitrep-latest.md` (overwrite):
```markdown
# SITREP YYYY-MM-DDTHH:MMZ
## 🔥 Fires
- Active issues needing immediate attention
## ⚡ NOW
- Single most important action to take
## 📊 Dashboard
- PRs: X open (Y approved waiting)
- Issues: X open (Y bugs, Z features)
## 🔄 Changes since last SITREP
- NEW/CLOSED/UPDATED items
```
6. Append summary to today's daily file (`/memory/daily/YYYY-MM-DD.md`)
7. Post terse summary to chat (3-5 lines, link to sitrep-latest.md)
8. If nothing needs attention, reply HEARTBEAT_OK
2. Read `/memory/sitrep-latest.md` for previous context
3. Run lurk skill (`skills/lurk/SKILL.md`) — read Discord channels, persist to `/memory/discord/YYYY-MM-DD.md`
4. Run triage skill (`skills/triage/SKILL.md`) — analyze GitHub + Discord, write SITREP
5. Post summary to chat (5-10 lines)
6. If nothing needs attention, reply HEARTBEAT_OK

View File

@ -0,0 +1,66 @@
---
name: lurk
description: Monitor Discord channel activity and persist notable items to memory. Run from main session during heartbeat.
---
# Lurk Skill
Monitor Discord lurk channels and persist notable activity to shared memory.
## When to Use
- Hourly heartbeat (step 3)
- Manual trigger to capture current channel state
## How to Run
Use `discord.readMessages` to read recent messages from each lurk channel:
- #help (1456457255208878100) — support fires
- #general (1456350065223270435) — community pulse
- #clawdributors (1458141495701012561) — contributor coordination
- #messaging-infra (1458052766831480996) — transport integrations
- #nix-packaging (1457003026412736537) — nix reproducibility
- #architecture (1457810851556888833) — architecture talk
- #clawdhub (1457886486044213411) — hub activity
- #models (1456704705219661980) — model discussions
- #skills (1456891440897724637) — skill showcases
- #showcase (1456609488202105005) — user showcases
- #security (1458861780976795782) — security discussion
## What to Capture
**Persist these:**
- Support issues / bug reports
- Questions that indicate user confusion
- Feature requests with discussion
- Anything referencing GitHub issues/PRs
- Repeated topics (multiple users, same issue)
- Announcements or important updates
**Skip these:**
- Casual chat / banter
- Single-word reactions
- Bot spam
- Already-resolved questions
## Output
Append to `/memory/discord/YYYY-MM-DD.md`:
```markdown
## HH:MM #channel-name
- [brief summary of notable item]
- Links to #NNN if references GitHub issue
- @username if relevant
## HH:MM #channel-name
- [another item]
```
## Constraints
- Be selective. Only notable items.
- Include timestamp and channel name.
- Keep each entry to 1-2 lines.
- Cross-reference GitHub issues when mentioned.
- If nothing notable: don't write anything, reply HEARTBEAT_OK.

View File

@ -29,9 +29,11 @@ Read these files to understand current state:
- `/memory/project.md` — project goals and priorities
- `/memory/architecture.md` — architecture decisions
4. **Discord signals**:
- Recent messages in conversation context from lurk channels
4. **Discord signals** (persisted by lurk skill):
- `/memory/discord/YYYY-MM-DD.md` — today's channel activity
- `/memory/discord/YYYY-MM-DD.md` — yesterday's (for context)
- Cross-reference with GitHub issues where relevant
- Multiple Discord reports of same issue = elevated priority
## Your Task