clip/hook-overlay
Hook Text Overlays — AI-generated attention-grabbing text burned into clips.
Category: clip
Source: workflows/clip/hooks.py
Input Schema
Section titled “Input Schema”| Field | Type | Default | Description |
|---|---|---|---|
full_text | string | "" | |
hook | string | "" | |
hook_style | string | "bold and provocative" | |
media_path | string | "" | |
regenerate | object | — | When set, this run is a regeneration. Workflows may read direction / keep / extra_instructions to modulate prompts; the engine persists parent_run_id and parent_variant_index as run lineage columns. |
subtitled_path | object | — | |
variants | integer | 1 | Number of independent variant executions (1–10). When > 1, the engine runs the workflow N times with different sampling, producing N outputs. |
vertical_path | object | — |
Output Schema
Section titled “Output Schema”No schema defined.
Task Pipeline
Section titled “Task Pipeline”generate_hook_text → burn_hook_overlay| Task | Description |
|---|---|
generate_hook_text | Generate hook text for a clip using an LLM. |
burn_hook_overlay | Burn hook text overlay onto the first 3 seconds of the video. |
Run-spec example
Section titled “Run-spec example”Save the YAML below as my-run.yaml, edit the values, and run with the CLI or POST it to the API. Required fields are uncommented; optional knobs are documented above the input: block — copy any line under input: and uncomment to set.
workflow: clip/hook-overlay
# Optional fields — copy any line(s) under `input:` and uncomment to set:# full_text: ""## hook: ""## hook_style: bold and provocative## media_path: ""## subtitled_path: null## vertical_path: null#
input: {}Run it locally:
fab-workflow --from-file my-run.yamlOr submit over the wire — the same file is the request body:
curl -X POST 'https://gofabric.dev/v1/workflows/runs?name=clip/hook-overlay' \ -H 'Authorization: Bearer fab_xxx' \ -H 'content-type: application/yaml' \ --data-binary @my-run.yamlEvery workflow also accepts the universal WorkflowInput fields — variants (1–10 fan-out) and regenerate (creative-direction hints with run lineage). See Run-specs (YAML / TOML / JSON) for the full top-level shape (metadata, priority, bundle, parent, etc.).
Warnings
Section titled “Warnings”- Last user task
burn_hook_overlayhas no Pydantic return type — workflow output schema is null. Declare a WorkflowOutput subclass and pass it to Flow(output=…) for a strict contract.