Short Publish
Overview
This skill automates the complete "video → subtitles → PostFlow" pipeline: run Whisper-based transcription, burn subtitles with the bundled Python script, turn the transcript into a multi-platform copy block, and schedule social posts through the PostFlow CLI.
Inputs & Prerequisites
- Arguments:
PATH– absolute path to the source video (MOV/MP4/etc.).DATETIME– publication date/time (accepts natural language like "tomorrow 09:00"). Usedateto confirm the current timestamp if needed.
- Tooling: use the
postflowCLI (postflow media upload,postflow posts create) and refer topostflow-clifor command details. - Script dependency:
scripts/transcribe_burn.pywraps Whisper, ffmpeg, and auto-gain. Requires Python 3.8+, ffmpeg, andopenai-whisperinstalled for the user; no extra configuration is needed inside this skill. - Timezone: default to Europe/Madrid. In winter assume UTC+01:00 (CET) when presenting final schedules if the
datecommand does not provide the offset.
Workflow
-
Collect inputs
- Confirm the provided
PATHexists; stop with a descriptive error if not. - Resolve
DATETIMEto an ISO timestamp. Usedate -j -for another deterministic macOS command when the input is natural language so PostFlow receives an unambiguous value.
- Confirm the provided
-
Transcribe and burn subtitles
- Run the bundled helper:
python3 scripts/transcribe_burn.py "$PATH". - Outputs (all written next to the original video):
<stem>.srt,<stem>.ass,<stem>.txt,<stem>_caption.txt,<stem>_subtitled.mp4.
- The
_subtitled.mp4is the media you will upload; everything else is transient reference material. Remove the generated artifacts (srt/ass/txt/caption/mp4_subtitled/normalized wav) once they have been read and the upload succeeds—never delete the original video.
- Run the bundled helper:
-
Generate the social copy
-
Read
<stem>.txtfor the full transcript. -
Apply the exact copywriting prompt below to the transcript; do not improvise structure or tone beyond the template.
Act as an expert LinkedIn copywriter building authority content. Transform the TRANSCRIPT into a case-study or practical-lesson post with this structure: 1. Hook headline with a leading emoji. 2. 2-3 sentence context introducing the situation. 3. Structured core (use 1️⃣/2️⃣/3️⃣ or ✅ and bold keywords per line). 4. Closing takeaway line. 5. Optional P.S. only when the transcript mentions an offer/event. Style rules: short paragraphs (1-2 lines), intentional emoji usage, no invented facts, stay faithful to the transcript. -
Reuse the single output block verbatim for LinkedIn, X, and Instagram, and as the YouTube description (light line breaks allowed). Craft a YouTube title ≤100 characters from the same content.
-
-
Upload the subtitled video
- Upload the
_subtitled.mp4and capturemedia_id:postflow --json media upload --file "<stem>_subtitled.mp4" --kind video - Use the returned
idasmedia_idfor all posts.
- Upload the
-
Schedule posts via
postflow posts create- Accounts come from
~/.config/skills/config.jsonunderpostflow.groups.short_publishandpostflow.accounts. - For X aliases, use
postflow.defaults.x(defaultx-es) unless the user explicitly requests another account. - For each account, create a scheduled post with the same copy block and the uploaded media:
postflow posts create \ --account-id <acc_id> \ --text "<copy_block>" \ --media-id <media_id> \ --scheduled-at <ISO8601> - If a thread is needed, use
--segments-jsoninstead of--text.
- Accounts come from
-
Report completion
- Confirm each scheduled post by echoing returned IDs and scheduled time in CET (UTC+01:00 during winter). Example:
LinkedIn pst_... → 2025-01-11T10:00:00+01:00 (CET).
- Confirm each scheduled post by echoing returned IDs and scheduled time in CET (UTC+01:00 during winter). Example:
Resources
scripts/transcribe_burn.py: Whisper + ffmpeg pipeline used in Step 2. Copy-safe to reuse elsewhere but do not edit unless the video workflow changes. Running the script produces all intermediate assets and the burned MP4 referenced throughout the workflow.