bip.ms.poll

Poll EPIC updates and tracked repositories for new manuscript artifacts.

29|4|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/matsen/bipartite --skill bip-ms-poll
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bip.ms.poll
Source: https://github.com/matsen/bipartite/tree/main/skills/bip.ms.poll
Command: npx skills add https://github.com/matsen/bipartite --skill bip-ms-poll

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps a manuscript project up-to-date by automatically polling tracked EPICs and code repositories for changes since the last check, fetching new artifacts, and surfacing actionable results.

Core Features & Use Cases

  • Lightweight mid-session polling of EPIC updates and merged PRs across tracked repos.
  • Automatically fetches new artifacts (figures, notebooks, notes) and surfaces key findings for quick drafting.
  • Useful during live writing sessions, research team coordination, and iterative manuscript refinement.

Quick Start

Start a poll during your manuscript session by running bip.ms.poll to fetch updates and surface new results since the last check.

Frequently Asked Questions about bip.ms.poll

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate polling for manuscript updates across tracked GitHub repositories?

Automating manuscript polling across tracked GitHub repositories is done by running mid-session polls that detect changes since the last check, fetch new artifacts like figures and notes, and surface actionable findings for drafting.

What is the best way to surface new research artifacts during live writing sessions?

Surfacing new research artifacts during live writing sessions requires deterministic polling of tracked EPICs and repositories to fetch new figures, notebooks, and key findings since the last poll for quick drafting.

Can I poll multiple tracked EPICs and code repositories at the same time?

You can poll multiple tracked EPICs and code repositories simultaneously during a manuscript session to fetch merged PRs, detect new artifacts, and surface key findings across all tracked projects.

How do I integrate GitHub data sources to detect manuscript-relevant code changes?

Integrating GitHub data sources to detect manuscript-relevant code changes involves enforcing deterministic polling steps that fetch new artifacts and surface updates from merged PRs across tracked repositories.

Does automated research-workflow polling require manual checks to find new figures and notes?

Automated research-workflow polling eliminates manual checks by automatically fetching new figures, notebooks, and notes from tracked EPICs and repositories to surface key findings for iterative manuscript refinement.