viral-run

Runs viral-video-pipeline stages via uv-managed Python module commands.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/yunior123/origna_gta_firebase --skill viral-run-yunior123
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: viral-run
Source: https://github.com/yunior123/origna_gta_firebase/tree/main/.claude/skills/viral-run
Command: npx skills add https://github.com/yunior123/origna_gta_firebase --skill viral-run-yunior123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running a multi-stage video pipeline manually requires remembering exact module paths, runtime flags, and project directories, which leads to errors like using the wrong Python interpreter or running from the wrong folder. ## Core Features & Use Cases - Stage-Based Execution: Run the full pipeline or individual stages (ideation, generation, postprocess, upload) with the correct uv run python3 -m src.<stage> command. - Environment Discipline: Enforces uv run python3 over bare python3 so dependencies from pyproject.toml are always resolved, and always changes to the project directory first. - Failure Handling: Surfaces full stderr output, checks for missing .env values or API keys, and supports dry-run isolation of failing stages. - Use Case: You want to regenerate only the postprocess stage of your video pipeline without re-running ideation — invoke the skill with the postprocess stage and it executes the correct command from the right directory. ## Quick Start Run the viral video pipeline's generation stage using the viral-run skill.

Frequently Asked Questions about viral-run

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

FAQPage Schema
How do I run a single stage of a Python video pipeline?▼

Run a single stage by executing uv run python3 -m src.<stage> from the project directory, where stage is ideation, generation, postprocess, or upload. Omitting the stage argument runs the full pipeline end to end.

Why use uv run python3 instead of python3?▼

uv run python3 reads the project's pyproject.toml and resolves the correct dependencies and environment automatically. Bare python3 may use the wrong interpreter or miss required packages, causing import or runtime failures.

What should I check when a pipeline stage fails?▼

Check the full stderr output first, then verify that .env values and API keys are present and correct. If the cause is unclear, rerun with --dry-run where supported to isolate the failing stage.

Can I run the generation or upload stage without cost concerns?▼

Generation and upload stages may consume API quota or incur costs, so confirm rate limits and budget before running them. The skill requires user confirmation before executing these stages as part of a full run.

Does the pipeline need to run from a specific directory?▼

Yes, all commands must run from the project root directory so module paths and configuration files resolve correctly. Always cd to the project directory before invoking any stage.