pipeline-manifest

Map research scripts to inputs, outputs, and dependencies, then derive a topological run order.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/cameronbracken/waterology-research --skill pipeline-manifest-cameronbracken
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pipeline-manifest
Source: https://github.com/cameronbracken/waterology-research/tree/main/skills/pipeline-manifest
Command: npx skills add https://github.com/cameronbracken/waterology-research --skill pipeline-manifest-cameronbracken

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Research projects accumulate scripts in Python, R, and Fortran with undocumented data flows, making replication packages, handoffs, and pipeline audits painful. This Skill reads the code without running it and produces a pipeline.md manifest that documents exactly how every artifact is produced. ## Core Features & Use Cases - Static Dependency Extraction: Records each script's purpose, entry command, files read and written, invoked programs, compiler flags, and figures or tables fed to Quarto or LaTeX documents, including Fortran I/O patterns like open, read, write, and inquire. - Dependency Graph and Run Order: Matches inputs to producers, builds a directed graph, runs a topological sort, and reports cycles, missing inputs, orphan scripts, and duplicate producers. - Structured Manifest Output: Writes pipeline.md with a pipeline table, figure and table manifest, Mermaid or adjacency-list graph, parallel execution groups, diagnostics, and RO-Crate readiness notes. - Use Case: Before submitting a replication package, run this Skill on the project directory to generate pipeline.md documenting every script's role and a verified execution order, then copy the bundled run-all.sh template once the graph is acyclic. ## Quick Start Analyze the scripts in this project directory and generate a pipeline.md manifest with the dependency graph and execution order.

Frequently Asked Questions about pipeline-manifest

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

FAQPage Schema
How do I document a research pipeline without running the code?▼

Statically scan the analysis directories for Python, R, and Fortran scripts, extract each script's inputs, outputs, and invoked programs, then match inputs to producers to build a dependency graph. The result is written to pipeline.md with a topological run order.

How to find the correct order to run analysis scripts?▼

Build a directed graph by matching each script's inputs to the script that produces them, then run a topological sort. The output lists the executable order, steps that can run in parallel, and reports cycles as failures rather than guessing an order.

Does pipeline-manifest support Fortran codebases?▼

Yes, it recognizes Fortran source files (.f90, .F90, .f95, .F95, .f) and common Fortran I/O such as open, read, write, inquire, command line arguments, and fixed unit mappings. It also traces wrappers that compile or launch Fortran executables.

What problems does a pipeline audit detect?▼

The audit reports dependency cycles, missing inputs with no producer, orphan scripts whose outputs reach nothing, duplicate producers for one output, document artifacts with no producing script, and produced outputs that no consumer uses.

When should I not generate the run-all.sh script?▼

Do not copy the bundled run-all.sh template until the dependency graph is acyclic and every canonical entry command is known. The template's project_root resolution assumes it lives at scripts/run-all.sh, so other destinations require adjustment and testing.