pipeline

Automate end-to-end source processing through seed, reduce, reflect, reweave, verify, and archive.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/lightningfastsls/London_Lab --skill pipeline-lightningfastsls
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pipeline
Source: https://github.com/lightningfastsls/London_Lab/tree/main/.claude/skills/pipeline
Command: npx skills add https://github.com/lightningfastsls/London_Lab --skill pipeline-lightningfastsls

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates a complete end-to-end processing pipeline from seed to archive for source data and claims.

Core Features & Use Cases

  • End-to-end orchestration: Seeds, reduces, processes through reflect/reweave/verify, and archives results in a single command.
  • Consistent workflows: Applies the full pipeline to individual files or batches with clear traceability and logging.
  • Use Case: When you need repeatable, auditable processing of a set of source files with automated verification and archival.

Quick Start

Invoke the full pipeline on a given source file or a set of files using the /pipeline command.

Frequently Asked Questions about pipeline

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

FAQPage Schema
How do I automate end-to-end source processing in a single command?

End-to-end source processing is automated by orchestrating seed, reduce, reflect, reweave, verify, and archive stages into a single command entry point. This ensures reliable sequencing, error handling, and logging for your data workflows without manual intervention.

What is the best way to run an auditable workflow pipeline for multiple source files?

An auditable workflow pipeline requires automated verification and archival of processing results. Applying the full pipeline to individual files or batches provides clear traceability and logging, ensuring repeatable processing for reliable audits.

Can I use pipeline orchestration for both individual files and batch data workflows?

Pipeline orchestration applies to both individual source files and batch processing. It consistently executes the full seed-to-archive sequence across varying data volumes while maintaining clear traceability and logging for every processed item.

Do I need external dependencies to run claims processing and source archival workflows?

No external dependencies are required to run claims processing and source archival workflows. The pipeline operates independently to handle sequencing, error handling, logging, and archival requirements within its own execution environment.

How does error handling work during automated source processing and archival?

Error handling during automated source processing is managed internally throughout the pipeline stages. It ensures reliable sequencing and logging from the initial seed phase through to final archival, preventing silent failures and maintaining auditable traceability.