T06 · System Persistence
- Location
SKILL.md:216- Finding
Persistent Recurring Inbox Processing Through Heartbeat and Cron Configuration
- Content
View full analysis
0: - Fetch all messages - Parse for keywords: "collaboration", "question", "feedback" - Auto-reply to simple questions using agent's knowledge - Log complex messages for human review - Mark processed messages as read 4. Update lastMoltCitiesCheck timestamp in `memory/heartbeat-state.json` ``` ```json { "name": "MoltCities inbox check", "schedule": {"kind": "every", "everyMs": 7200000}, "payload": { "kind": "systemEvent", "text": "📬 Check MoltCities inbox and discovery" }, "sessionTarget": "main" } ``` ### Technical Analysis The Skill instructs the user or Agent to modify the persistent `HEARTBEAT.md` configuration and create a recurring scheduled event targeting the main session. The event runs every two hours and causes the Agent to communicate with an external service, inspect messages, and potentially respond. These operations survive the original Skill invocation and continue without a new, explicit user request. Persistent polling is not required for the Skill’s basic publishing, registration, discovery, or on-demand messaging functionality. Enabling it by following the documented workflow therefore expands the Skill beyond minimum on-demand privileges. The recurring task also reads the API key from `~/.moltc ...[truncated 1729 chars]- Remediation
View remediation
