engagement-act

Read memory/MEMORY.md for context on active projects and open engagement follow-ups. Read the last 7 days of memory/logs/ — look for engagement opportunities flagged by other skills (e.g. project-pulse, refresh-x, reply-maker, channel-recap) or noted in MEMORY.md Known Follow-ups. Projects-of-interest list: if `memory/topics/projects-of-interest.md` exists, treat the project names listed there as the things to watch for mentions, cosigns, attributions, and fork moments. If the file is missing or empty, fall back to any project names that appear in recent logs or in MEMORY.md. ## Steps 1. **Collect unactioned engagement opportunities.** Read `memory/logs/` for the last 7 days. Look for: - Log entries flagging engagement opps (e.g. "Engagement opps: N flagged" with N > 0) — extract the named handles/accounts - Any person who cosigned, mentioned, or attributed one of the operator's projects-of-interest - GitHub attribution or fork moments not yet acknowledged - Entries in MEMORY.md "Known Follow-ups" explicitly flagging engagement opps - Cosigns or mentions surfaced in refresh-x, reply-maker, or channel-recap runs Build a list: `{ person/account, context, what_they_did, link_if_known, days_ago }` 2. **Filter and prioritize.** Apply these rules: - Drop any opp older than 14 days — window is likely closed - De-dupe: skip opps where recent logs already show "replied to @X" or "acknowledged" for that handle - Rank by: recency (fresher first) × leve...