Intelligent conversation analysis, summarization, and conclusion recording
Analysis Dimensions:
Execution:
Analysis Dimensions:
Execution:
Check Scope:
Execution:
ScenarioTrigger MethodAuto-triggerEvery 10 conversations (via HEARTBEAT.md counter)Scheduled triggerDaily at 12:00 and 24:00 (cron)Manual triggerUser inputs "analyze conversation", "summary", "check tasks"
text
Conversation counter +1
↓
Counter >= 10?
↓ YES
Reset counter
↓
Execute 3 analysis tasks
↓
Update memory files
text
Cron trigger
↓
Analyze all conversations from 00:00 to current time
↓
Execute 3 analysis tasks
↓
Update memory files
↓
Send Feishu notification for incomplete tasks
HEARTBEAT.md - Conversation counter, task trackingUSER.md - User profile recordsMEMORY.md - Long-term memory, conversation analysis historySESSION-STATE.md - Current session stateUSER.md - Updated user profileMEMORY.md - Appended conversation analysisHEARTBEAT.md - Reset conversation counterbash
# Manual trigger analysis
node skills/conversation-analyzer/scripts/analyze.js
# Check incomplete tasks only
node skills/conversation-analyzer/scripts/check-tasks.js
# Daily full analysis (0:00 to now)
node skills/conversation-analyzer/scripts/daily-analysis.js
bash
# Daily analysis at 12:00 and 24:00
0 12,0 * * * cd ~/.openclaw/workspace && node skills/conversation-analyzer/scripts/daily-analysis.js > /dev/null 2>&1
bash
openclaw cron add "0 12,0 * * *" "conversation-analyzer/daily-analysis"
The skill reads and updates HEARTBEAT.md:
markdown
## Conversation Counter
- Current count: 0
- Last analysis: 2026-03-24 21:00
- Threshold: 10 conversations
When counter reaches 10:
StatusMeaningQueueWaiting to startActiveIn progressWaitingBlocked/WaitingDoneCompletedAbortedCancelledNotNeededExplicitly marked as not required
Transform passive responses into proactive insights 🎯