Github Initiative Pulse
- 90 installs
- 325 repo stars
- Updated August 2, 2026
- athola/claude-night-market
Turn ProjectTracker status JSON into repeatable GitHub comment scorecards, blocker radars, and weekly initiative digests for stakeholders.
About
GitHub Initiative Pulse is a template-oriented agent skill for solo builders and tiny teams who already use a ProjectTracker-style JSON report and want consistent, scannable GitHub posts instead of ad-hoc status comments. It packages ready-made markdown for initiative scorecards, high-risk issue radars, PR watchlists, and a discussion footer that cites refresh timestamps—aligned with tracker.py status output and optional GitHub Projects filters. The digest blueprint walks you from raw tracker data through initiatives under 80% completion, pairing two wins (merged PR links), two risks (open issues), and ETA lines derived from due dates, then tabulates metrics for week-over-week comparability. It does not run the tracker itself; it teaches how to structure narrative so blockers, owners, and next milestones stay visible between syncs. Best when you ship in public on GitHub and need Minister-style pulse posts without rebuilding the format each week.
- Markdown snippets for Initiative Scorecard tables (Done, Blockers, Next per initiative)
- Blocker Radar collapsible template with owner handles and mitigation ETAs
- PR Watchlist section for reviews awaiting sign-off
- Status Digest Blueprint: 4-step flow from tracker JSON to wins, risks, and milestone bullets
- GitHub search query hooks so readers can self-serve deeper issue context
Github Initiative Pulse by the numbers
- 90 all-time installs (skills.sh)
- Ranked #1,407 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/athola/claude-night-market --skill github-initiative-pulseAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 90 |
|---|---|
| repo stars | ★ 325 |
| Security audit | 2 / 3 scanners passed |
| Last updated | August 2, 2026 |
| Repository | athola/claude-night-market ↗ |
What it does
Turn ProjectTracker status JSON into repeatable GitHub comment scorecards, blocker radars, and weekly initiative digests for stakeholders.
Files
GitHub Initiative Pulse
Overview
Turns tracker data and GitHub board metadata into initiative-level summaries. Provides markdown helpers and CSV exports for pasting into issues, PRs, or Discussions.
Ritual
1. Capture work via tracker.py add or sync from GitHub Projects. 2. Review blockers/highlights using the Blocker Radar table. 3. Generate GitHub comment via tracker.py status --github-comment or module snippets. 4. Cross-link the weekly Status Template and share with stakeholders.
Key Metrics
| Metric | Description |
|---|---|
| Completion % | Done tasks / total tasks per initiative. |
| Avg Task % | Mean completion percent for all in-flight tasks. |
| Burn Rate | Hours burned per week (auto-calculated). |
| Risk Hotlist | Tasks flagged priority=High or due date in past. |
GitHub Integrations
- Links every task to an issue/PR URL.
- Supports auto-labeling by referencing
phasein the tracker record. - Encourages posting digests to coordination issues or PR timelines.
Exit Criteria
- All initiatives represented with updated metrics.
- Markdown digest pasted into relevant GitHub thread.
- Risk follow-ups filed as issues with owners and due dates.
Troubleshooting
Common Issues
If metrics appear outdated, ensure tracker.py has successfully synced with GitHub. If the Markdown digest renders incorrectly in GitHub, check for unescaped characters in task titles or missing newlines between table rows.
GitHub Comment Snippets
Use these markdown snippets with tracker.py status --github-comment output for richer posts.
Initiative Scorecard
| Initiative | Done | Blockers | Next |
|------------|---------|-------------|--------|
| <Name> | <count> | <issue links> | <key tasks> |Blocker Radar
<details>
<summary>High Risk Issues</summary>
- [ ] [issue-123](link) – Owner: @handle – Mitigation ETA 1/12
- [ ] [issue-456](link) – Owner: @handle – Needs design sign-off
</details>PR Watchlist
### PRs awaiting review
- #1234 Ready for Docs
- #5678 Needs Performance Sign-offDiscussion Template
> Posted via Minister Initiative Pulse
> Data refreshed: <timestamp>Status Digest Blueprint
Inputs
ProjectTracker.get_status_report()JSON payload.- Optional GitHub Projects filter (lane, owner).
- Risk label queries (e.g.,
label:risk-red state:open).
Steps
1. Pull tracker JSON. 2. Identify initiatives with completion < 80%. 3. For each initiative create:
- 2 key wins (link to merged PRs).
- 2 active risks (link to issues).
- Updated ETA derived from due dates.
4. Drop summary into template:
### <Initiative>
- Wins: <PR 1>, <PR 2>
- Risks: <Issue 1>, <Issue 2>
- Next Milestone: <Date>5. Include table of metrics using tracker values.
Tips
- Use GitHub search queries so stakeholders can self-serve deeper context.
- Keep bullet count consistent each week for comparability.
- Add emoji tags to draw attention inside GitHub comments.
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kFAQ
Is Github Initiative Pulse safe to install?
skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.