navig-pipeline
The content assembly line: short vertical clips cut to the beat, narrated reels, captions and hooks, and download → transcribe → script → narrate → fan-out — its own navig-pipeline command, with your own keys; also
navig pipelineinside navig.
Works on its own — its own CLI, no navig required · v0.7.2 · PyPI
On its own (no navig needed)
pip install navig-pipeline
navig-pipeline --help # no navig needed
With navig
pip install navig-pipeline
navig content --help
Commands
| Command | What it does |
|---|---|
navig content |
Run navig content |
navig content captions |
✍️ Transcribe a track to an .srt — with word-level timings. |
navig content cast |
🎬 Capture a REAL command's output for the Reel Stage — once, replayable at any size. |
navig content clip |
🎵 Build a vertical clip cut to a track you already have — no narration. |
navig content episode build |
🎬 Build an episode end to end — and stop at the first stage that fails. |
navig content episode draft |
📝 Draft an episode from an article — hook, beats, narration, posting copy. |
navig content episode plan |
🧭 Reconstruct a narration plan (rebuild.json) from a legacy episode's voice + cuts. |
navig content episode stats record |
Store a snapshot of a posted episode's numbers (from TikTok's insights screen). |
navig content episode stats show |
Every episode side by side: what the cut is (hook, cuts, pace) and how it did. |
navig content hooks |
🎣 Rank the passages of a track worth cutting a short clip from. |
navig content localize |
🌍 The same picture in another language — captures untouched. |
navig content publish |
📦 A render → a ready-to-post pack: spec check, cover, caption, hashtags. |
navig content qa |
🔎 Catch a video's design bugs before (and after) rendering it. |
navig content recipe apply |
Unpack a recipe into an episode folder — hash-checked, never half-applied. |
navig content recipe export |
Pack an episode's irreplaceable sources — scenes, shotlists, narration plan, casts. |
navig content reel |
🎬 Build a vertical reel per language — capture, narrate, caption, score. |
navig content run |
Run the assembly line from a topic (or a source clip) to a fanned-out post. |
navig content schedule |
Autopilot — run + publish the assembly line on a recurring cadence. |
navig content stage |
📱 Compile a scene into a self-contained, phone-sized page a reel or clip can film. |
navig content status |
Show which assembly-line stages are wired (their plugin is installed). |
navig content telegram-import |
Import a Telegram channel's media into the local library, then optionally delete the |
The content assembly line: short vertical clips cut to the beat, narrated reels, captions
and hooks, and a download → transcribe → script → narrate → publish flow. It runs on its own
as navig-pipeline, and inside navig as navig pipeline.
acquire (navig-download) → transcribe (navig-audio) → script (navig-text)
→ narrate (navig-audio) → publish (navig-social)
On its own
pip install navig-pipeline # adds the `navig-pipeline` command
navig-pipeline status # which stages are wired here
navig-pipeline captions track.mp3 # word-timed .srt — no key needed (local Whisper)
navig-pipeline hooks track.mp3 # passages worth cutting, with timings
navig-pipeline clip shot.md --range 30-45 # a vertical clip cut to the beat (ffmpeg on PATH)
navig-pipeline reel episode.md # narrated reel from a scenario
pip install "navig-pipeline[all]" # + the script, acquire and publish stages of `run`
navig-pipeline run --topic "…" --dry-run
The media engine comes from navig-generate and the voice from navig-audio, both installed with
this. Captions use navig-audio's transcription: the OpenAI Whisper API when an OpenAI key is
set, faster-whisper on this machine otherwise. Keys come from the environment or the shared
vault (navig-vault).
Filming a live URL in a clip or reel drives your installed Chrome through navig-browser
(pip install "navig-pipeline[film]", also in [all]); generated shots and stills need no
browser. Two things are part of navig and say so when used without it: schedule (navig's
daemon runs it) and telegram-import (navig's Telegram client).
Inside navig
The same commands are navig pipeline …, plus the Telegram and scheduling features above.
Why it exists
Capabilities compose. The pipeline reaches across plugins through the same public seams a
user would (navig-audio's transcription and narration, navig-generate's media engine,
navig-social's fan-out), and every stage is optional: a plugin that isn't installed drops its
stage, reported rather than silently skipped. run is a dry run unless you pass --live.
1 maintainer
Metadata
1 maintainer
Release files for navig-pipeline 0.7.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| navig_pipeline-0.7.2.tar.gz | 321.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| navig_pipeline-0.7.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 608.1 kB
Security for navig-pipeline 0.7.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
