manuscript-pipeline

Reconciles a manuscript tracker workbook against a papers repository and git history.

Updated Oct 7, 2022
One-click install
npx skills add https://github.com/tamagusko/linux-cfg --skill manuscript-pipeline-tamagusko
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manuscript-pipeline
Source: https://github.com/tamagusko/linux-cfg/tree/main/dotfiles/claude/skills/manuscript-pipeline
Command: npx skills add https://github.com/tamagusko/linux-cfg --skill manuscript-pipeline-tamagusko

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? A hand-maintained paper tracker drifts out of sync with the actual manuscripts on disk, making it hard to know which submissions are active, stale, or missing from the record. This Skill compares the tracker workbook against the papers repository and git history so the workbook becomes derived from ground truth rather than remembered. ## Core Features & Use Cases - Tracker-to-repo reconciliation: Reads a tracker in .xlsx or .csv format, matches each row to a manuscript directory, and reports status alongside the last git commit date. - Drift and staleness detection: Flags rows where repo activity postdates the tracker, reports tracker age, and suppresses per-row flags when the whole workbook is outdated. - Unmatched and orphan reporting: Lists tracker rows with no directory and in-progress directories with no tracker row, with an aliases.json escape hatch for ambiguous matches. - Use Case: Ask where your papers stand before a meeting, and get a ranked report of recent manuscript activity, stale tracker entries, and untracked work in progress. ## Quick Start Ask the assistant to run the manuscript pipeline status report to reconcile your paper tracker against the papers repository.

Frequently Asked Questions about manuscript-pipeline

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

FAQPage Schema
How do I check the status of my manuscripts in progress?

Run the pipeline_status.py script, which reads your tracker workbook and matches each row to a directory in the papers repository. It prints a table of tracker status beside each directory's last git commit, plus ranked recent activity.

How do I reconcile a spreadsheet tracker with a git repository?

Point the script at your tracker with --tracker and your repository with --papers. It matches rows to directories by project slug and token coverage, then reports rows where repo commits postdate the tracker's last update.

Can I use a Google Sheets export instead of an xlsx file?

Yes, the --tracker flag accepts .csv as readily as .xlsx, so a Google Sheets CSV export works with no code changes. Downloading the sheet as .xlsx into the repo also works and avoids exposing unpublished titles.

Why does a tracker row report as unmatched?

Rows are unmatched when no directory matches by slug containment or token coverage, or when a match is ambiguous, since a wrong match is treated as worse than none. Resolve these by adding an entry to aliases.json keyed on the row's title or project.

Does the script modify my tracker workbook?

No, the script is strictly read-only and only prints a report. The workbook is co-author-visible, so all edits remain yours to make manually.