Shortform production skill

Produce readable vertical shorts with evidence-based B-roll, three opening treatments, editorial review, and authorized Metricool API delivery.

by ericosiu·MIT license·★ 3,615 Stars on the repo·GitHub ↗

Use now

Files of Shortform production

ericosiu/main1 file shown
SKILL.md
Show the full text38 lines
shortform-production/SKILL.md38 lines · 2.7 KB

Shortform Production

Keep the visual style consistent. Change the storytelling to suit the source. An experiment is a hypothesis, not a proven retention gain.

Preamble

When available, use the repository's version check and telemetry initializer:

python3 telemetry/version_check.py 2>/dev/null || true
python3 telemetry/telemetry_init.py 2>/dev/null || true

Remote telemetry requires opt-in. Never log content, paths, account details, or credentials.

Choose the work

  1. Edit: Read V5 style and creative formats. Use the named source and timestamped transcript. Preserve credentials, claim qualifiers, natural speech, and the CTA. Inventory real assets before designing inserts. Use an available renderer; this package supplies editorial rules and delivery tools.
  2. Experiment: Produce three opening treatments for one clip. Choose one before rendering the full edit unless complete variants were requested. Do not automatically publish near-duplicates.
  3. Review: Read the bundled rubric, judge prompt, reference requirements, and scorecard schema. Apply review requirements. Report missing evidence; never invent a score.
  4. Caption or delivery: Read API delivery. Inspect the actual final video and CTA. Do not re-render an approved upload to match production defaults. Use the API for Metricool.
  5. Results: Read review and learning. Record missing metrics as null. One post cannot establish a winning style.

Installation does not authorize publishing, new accounts, automations, purchases, or public releases. Existing explicit task authorization is sufficient; do not ask twice.

Deliver

Include artifacts relevant to the requested mode: source hash and transcript; claims and asset provenance; hook hypothesis and shot list; versioned master and SRT; cover, title, caption and CTA; review evidence; verified delivery receipt; and supported performance observations.

Keep credentials and private receipts outside the repository. Preserve raw media and previous renders. Report review candidate, scheduled, publishing, or published only with matching evidence.

Use the next-batch plan to turn these rules into a production cycle.

1---
2name: shortform-production
3description: Produce readable vertical shorts with evidence-based B-roll, three opening treatments, editorial review, and authorized Metricool API delivery. Use for shortform edits, captions, hook experiments, or scheduling approved clips.
4---
5 
6# Shortform Production
7 
8Keep the visual style consistent. Change the storytelling to suit the source. An experiment is a hypothesis, not a proven retention gain.
9 
10## Preamble
11 
12When available, use the repository's version check and telemetry initializer:
13 
14```bash
15python3 telemetry/version_check.py 2>/dev/null || true
16python3 telemetry/telemetry_init.py 2>/dev/null || true
17```
18 
19Remote telemetry requires opt-in. Never log content, paths, account details, or credentials.
20 
21## Choose the work
22 
231. **Edit:** Read [V5 style](references/v5-style.md) and [creative formats](references/creative-formats.md). Use the named source and timestamped transcript. Preserve credentials, claim qualifiers, natural speech, and the CTA. Inventory real assets before designing inserts. Use an available renderer; this package supplies editorial rules and delivery tools.
242. **Experiment:** Produce three opening treatments for one clip. Choose one before rendering the full edit unless complete variants were requested. Do not automatically publish near-duplicates.
253. **Review:** Read the bundled [rubric](references/eval/rubric.json), [judge prompt](references/eval/judge-prompt.md), [reference requirements](references/eval/references.json), and [scorecard schema](references/eval/scorecard.schema.json). Apply [review requirements](references/review-and-learning.md). Report missing evidence; never invent a score.
264. **Caption or delivery:** Read [API delivery](references/metricool.md). Inspect the actual final video and CTA. Do not re-render an approved upload to match production defaults. Use the API for Metricool.
275. **Results:** Read [review and learning](references/review-and-learning.md). Record missing metrics as null. One post cannot establish a winning style.
28 
29Installation does not authorize publishing, new accounts, automations, purchases, or public releases. Existing explicit task authorization is sufficient; do not ask twice.
30 
31## Deliver
32 
33Include artifacts relevant to the requested mode: source hash and transcript; claims and asset provenance; hook hypothesis and shot list; versioned master and SRT; cover, title, caption and CTA; review evidence; verified delivery receipt; and supported performance observations.
34 
35Keep credentials and private receipts outside the repository. Preserve raw media and previous renders. Report `review candidate`, `scheduled`, `publishing`, or `published` only with matching evidence.
36 
37Use [the next-batch plan](references/next-batch.md) to turn these rules into a production cycle.
38 

Discussion