team-pulse

What problem does it solve? Keeping a public project community informed requires constant manual monitoring of git activity, CI runs, releases, and team escalations. This Skill automates one outreach-loop pass: it reads team state, scores events on a 0-10 substantive model, and decides whether to post to GitHub Discussions or stay silent, preventing both noise and silence. ## Core Features & Use Cases - Event scoring and routing: Reads git log, CI runs, releases, peer memories, and escalation logs, then scores events and routes them to Announcements (score ≥9), Progress (5-8), or silence (<5) with a time-since-last-post multiplier. - Discussion engagement: Runs ordered discuss-* engagement passes (comments, bugs, questions) with moderation pre-screening, author filters, and per-thread cooldowns before the regular pulse walk. - Audit logging: Appends every tick to pulse_log.md with raw score, adjustment, route, and post URL, and manages a drafts/ directory for bundled posts. - Use Case: A heartbeat scheduler invokes the skill every 15 minutes; after a new release tag ships with a green pipeline, it scores the event a 10 and posts an announcement to GitHub Discussions automatically. ## Quick Start Ask the agent to run a pulse by saying "run a pulse" or "fire team-pulse" and it will scan team state, score events, and post or stay silent accordingly.