title-pipeline

Orchestrate multi-stage title processing across collect, embed, comps, and format-fit stages.

Updated Jul 22, 2025
One-click install
npx skills add https://github.com/creepyblues/kstorybridge-integrated --skill title-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: title-pipeline
Source: https://github.com/creepyblues/kstorybridge-integrated/tree/main/.claude/skills/title-pipeline
Command: npx skills add https://github.com/creepyblues/kstorybridge-integrated --skill title-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The pipeline automates end-to-end title processing by coordinating data collection, embeddings, comps generation, and format-fit analysis to enrich catalog data and insights.

Core Features & Use Cases

  • End-to-end orchestration of four stages (collect, embed, comps, format-fit) to process new and recently added titles.
  • Batch processing capabilities allow overnight or bulk processing of large title sets with progress visibility.
  • Cost and time tracking with per-title estimates, error handling, and retry strategies for robust operations.

Quick Start

Trigger the pipeline for a specific title by providing its title_id to the Run pipeline function.

Frequently Asked Questions about title-pipeline

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

FAQPage Schema
How do I automate end-to-end title processing for catalog enrichment?

You can automate end-to-end title processing by orchestrating a multi-stage pipeline covering data collection, embeddings, comps generation, and format-fit analysis to enrich your catalog data.

Can I run batch processing for large sets of new titles overnight?

Yes, batch processing capabilities support overnight or bulk processing of large title sets, providing progress visibility and robust error handling with retry strategies for continuous operations.

How does title intelligence pipeline orchestration handle errors and costs?

Pipeline orchestration handles errors and costs by specifying per-title cost and duration estimates, stage sequencing requirements, and retry strategies to ensure robust batch operations.

Do I need Supabase edge functions to run the title processing workflow?

Yes, the title processing workflow specifies integration with Supabase edge functions for each pipeline stage to execute the functional requirements of the orchestration sequence.

What is the best way to trigger the pipeline for a specific title?

The best way to trigger the pipeline for a specific title is by providing its title_id to the Run pipeline function, which initiates the four-stage processing workflow.