bip.ms

Monitor EPICs and tracked repos to surface new manuscript results.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manuscript teams spend tedious time scanning EPICs and tracked repositories for new results. This skill automates surfacing relevant findings to streamline manuscript progress.

Core Features & Use Cases

  • Monitors tracked EPIC issues across repositories for new results, figures, and findings
  • Fetches curated results via per-repo fetch_cmds, integrates artifacts into the manuscript workflow
  • Maintains manuscript context by updating TeX sources, prep-figures, and HTML notebooks
  • Generates a consolidated status view and guides next writing steps

Quick Start

Configure .ms-config.json with your manuscript root and tracked repositories, then run the workflow to surface new results.

Frequently Asked Questions about bip.ms

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

FAQPage Schema
How do I automatically surface new manuscript results from tracked GitHub repos?

To surface manuscript results from EPICs, use a .ms-config.json file specifying tracked repos, local paths, and fetch commands. The workflow monitors EPICs and integrates new figures and notebooks into your TeX project.

What is the best way to track EPIC issues for new findings across multiple repositories?

Tracking EPIC issues across repositories involves defining repo paths and EPICs in a .ms-config.json file. The workflow monitors these issues and fetches curated results to generate a consolidated manuscript status view.

Can I integrate new figures and notebooks into a TeX manuscript project automatically?

Yes, integrating new figures into a TeX manuscript is supported. By specifying a prep_figures_dir and fetch_cmds in your configuration, the workflow automatically updates TeX sources and HTML notebooks with artifacts from tracked repos.

How do I configure a workflow to pull new results from specified EPICs into my manuscript?

To pull new results from EPICs, create a .ms-config.json file in your manuscript root. List the manuscript path, prep_figures_dir, and tracked repos with their local_path, epics, and fetch_cmds to start the workflow.

Does this manuscript monitoring workflow require specific directory structures for prep figures?

Yes, this manuscript monitoring workflow requires a specific directory structure. You must define a manuscript root containing the .ms-config.json file and specify a prep_figures_dir path where fetched artifacts are integrated into your TeX manuscript workflow.

Why do I need to specify fetch_cmds in my manuscript configuration file?

You need fetch_cmds in your manuscript configuration to define how curated results are retrieved from each tracked repository. These commands automate pulling new figures and findings from specified EPICs into your local manuscript workflow.