Create shorts with AI

I want to automate this page’s Shorts workflow on a schedule, including upload/publication if I agree to it.
Ask me for any missing start/end dates, recurrence, execution time and time zone, videos per run, video length, and storage location. Also confirm the media, script, voice, subscription usage, and Typecast API spending limits.
First ask whether I want creation only or upload/publication as well. If I want publication, summarize the platform, account/channel, visibility, title/description guidelines, publishing schedule and time zone, and whether I want review before each post or automatic publication within agreed conditions, then have me confirm them.
If I choose upload/publication, check channel permissions, upload integration, and scheduled publishing support, and include them in the recurring task. If unsupported, keep the finished video and explain the connection steps or manual work needed.
After I confirm the conditions, verify access to the project media, cast, ffmpeg, and output storage.
Register a supported desktop schedule. If this CLI or IDE session cannot register it, give me the instructions and setup steps for Scheduled. Use a web schedule only after verifying its production tools and output storage.
If scheduling is unsupported, explain how to run it manually. If an end date cannot be set, explain the limitation and stopping method first.
Save each run’s video, script, and captions in a separate folder and keep an artifact list.
If I choose per-run review, ask before publishing. If I choose automatic publication, proceed without asking again within the agreed conditions. Ask before changing the channel, visibility, content guidelines, schedule, or budget. Verify and record the upload link, visibility, and scheduled or actual publication time.
After setup, report the schedule, next run, end conditions, and how to stop it. If an end date cannot be configured, explain that limitation first.

Please run this page’s Shorts workflow repeatedly, including upload/publication if I agree to it.
Ask me for any missing start/end dates, recurrence, execution time and time zone, videos per run, video length, and storage location. Also confirm the media, script, voice, subscription usage, and Typecast API spending limits.
First ask whether I want creation only or upload/publication as well. If I want publication, summarize the platform, account/channel, visibility, title/description guidelines, publishing schedule and time zone, and whether I want review before each post or automatic publication within agreed conditions, then have me confirm them.
If I choose upload/publication, check channel permissions, upload integration, and scheduled publishing support, and include them in the recurring task. If unsupported, keep the finished video and explain the connection steps or manual work needed.
After I confirm the conditions, verify that the task can run on the connected computer and access the media, cast, ffmpeg, and storage folder.
Once the environment is verified, register a supported recurring schedule. For cloud execution, separately verify the production tools and storage paths there. If unsupported, provide instructions for running the task manually.
Make each run’s video, script, captions, and results available in Activity.
Save each run’s video, script, and captions in a separate folder and keep an artifact list.
If I choose per-run review, ask before publishing. If I choose automatic publication, proceed without asking again within the agreed conditions. Ask before changing the channel, visibility, content guidelines, schedule, or budget. Verify and record the upload link, visibility, and scheduled or actual publication time.
After setup, report the schedule, next run, end conditions, and how to stop it. If an end date cannot be configured, explain that limitation first.

I want to repeat this workflow in a Claude Code cloud Routine to create shorts and, if I agree, upload/publish them.
Ask me for any missing start/end dates, recurrence, execution time and time zone, videos per run, video length, and storage location. Also confirm the media, script, voice, subscription usage, and Typecast API spending limits.
First ask whether I want creation only or upload/publication as well. If I want publication, summarize the platform, account/channel, visibility, title/description guidelines, publishing schedule and time zone, and whether I want review before each post or automatic publication within agreed conditions, then have me confirm them.
If I choose upload/publication, check channel permissions, upload integration, and scheduled publishing support, and include them in the recurring task. If unsupported, keep the finished video and explain the connection steps or manual work needed.
After I confirm the conditions, verify access to media, cast and ffmpeg execution, and persistent output storage in the Routine’s repository and cloud environment.
Register a Routine only if supported. If this session cannot register one, provide the instructions and setup steps for New routine. If cloud rendering or storage is unavailable, explain the local production option.
Save each run’s video, script, and captions in a separate folder and keep an artifact list.
If I choose per-run review, ask before publishing. If I choose automatic publication, proceed without asking again within the agreed conditions. Ask before changing the channel, visibility, content guidelines, schedule, or budget. Verify and record the upload link, visibility, and scheduled or actual publication time.
After setup, report the schedule, next run, end conditions, and how to stop it. If an end date cannot be configured, explain that limitation first.

I want to repeatedly create shorts in a local folder and, if I agree, upload/publish them using this page’s workflow.
Ask me for any missing start/end dates, recurrence, execution time and time zone, videos per run, video length, and storage location. Also confirm the media, script, voice, subscription usage, and Typecast API spending limits.
First ask whether I want creation only or upload/publication as well. If I want publication, summarize the platform, account/channel, visibility, title/description guidelines, publishing schedule and time zone, and whether I want review before each post or automatic publication within agreed conditions, then have me confirm them.
If I choose upload/publication, check channel permissions, upload integration, and scheduled publishing support, and include them in the recurring task. If unsupported, keep the finished video and explain the connection steps or manual work needed.
After I confirm the conditions, verify the media folder, cast, ffmpeg, and storage permissions, then register a supported desktop local Routine. If you cannot register it directly, provide the instructions and setup steps for New routine → Local.
If only /loop is available, explain that it runs only in the open session and provide manual execution instructions instead of presenting it as long-term scheduling.
Save each run’s video, script, and captions in a separate folder and keep an artifact list.
If I choose per-run review, ask before publishing. If I choose automatic publication, proceed without asking again within the agreed conditions. Ask before changing the channel, visibility, content guidelines, schedule, or budget. Verify and record the upload link, visibility, and scheduled or actual publication time.
After setup, explain when the computer and app must stay running, the schedule, next run, end conditions, and how to stop it. If an end date cannot be configured, explain that limitation first.

I want to set up recurring Cowork work to create shorts and, if I agree, upload/publish them using this page’s workflow.
Ask me for any missing start/end dates, recurrence, execution time and time zone, videos per run, video length, and storage location. Also confirm the media, script, voice, subscription usage, and Typecast API spending limits.
First ask whether I want creation only or upload/publication as well. If I want publication, summarize the platform, account/channel, visibility, title/description guidelines, publishing schedule and time zone, and whether I want review before each post or automatic publication within agreed conditions, then have me confirm them.
If I choose upload/publication, check channel permissions, upload integration, and scheduled publishing support, and include them in the recurring task. If unsupported, keep the finished video and explain the connection steps or manual work needed.
After I confirm the conditions, verify that the current account and execution environment can access media, run production tools, and save output files. Do not assume scheduling alone supports rendering or uploading.
If supported, propose a Scheduled task for me to confirm with Schedule. Explain the computer/app requirements if local execution is needed. If production tools cannot run there, prepare instructions for a suitable local agent.
Save each run’s video, script, and captions in a separate folder and keep an artifact list.
If I choose per-run review, ask before publishing. If I choose automatic publication, proceed without asking again within the agreed conditions. Ask before changing the channel, visibility, content guidelines, schedule, or budget. Verify and record the upload link, visibility, and scheduled or actual publication time.
After setup, report the schedule, next run, end conditions, and how to stop it. If an end date cannot be configured, explain that limitation first.

I want to automate this page’s Shorts workflow on a schedule, including upload/publication if I agree to it.
Ask me for any missing start/end dates, recurrence, execution time and time zone, videos per run, video length, and storage location. Also confirm the media, script, voice, subscription usage, and Typecast API spending limits.
First ask whether I want creation only or upload/publication as well. If I want publication, summarize the platform, account/channel, visibility, title/description guidelines, publishing schedule and time zone, and whether I want review before each post or automatic publication within agreed conditions, then have me confirm them.
If I choose upload/publication, check channel permissions, upload integration, and scheduled publishing support, and include them in the recurring task. If unsupported, keep the finished video and explain the connection steps or manual work needed.
After I confirm the conditions, verify media access, cast and ffmpeg execution, and output storage in the production project.
Check whether I need repetition in the current conversation or an Automation that persists across sessions, and register only a supported option. Do not describe /schedule as permanent scheduling. If unsupported, explain manual execution.
Save each run’s video, script, and captions in a separate folder and keep an artifact list.
If I choose per-run review, ask before publishing. If I choose automatic publication, proceed without asking again within the agreed conditions. Ask before changing the channel, visibility, content guidelines, schedule, or budget. Verify and record the upload link, visibility, and scheduled or actual publication time.
After setup, explain the execution environment requirements, schedule, next run, end conditions, and how to stop it. If an end date cannot be configured, explain that limitation first.

Set up recurring OpenClaw work to create shorts and, if I agree, upload/publish them using this page’s workflow.
Ask me for any missing start/end dates, recurrence, execution time and time zone, videos per run, video length, and storage location. Also confirm the media, script, voice, subscription usage, and Typecast API spending limits.
First ask whether I want creation only or upload/publication as well. If I want publication, summarize the platform, account/channel, visibility, title/description guidelines, publishing schedule and time zone, and whether I want review before each post or automatic publication within agreed conditions, then have me confirm them.
If I choose upload/publication, check channel permissions, upload integration, and scheduled publishing support, and include them in the recurring task. If unsupported, keep the finished video and explain the connection steps or manual work needed.
After I confirm the conditions, verify the Gateway’s running state, the agent’s media access, cast and ffmpeg execution, and storage-folder write permissions.
Register recurring work only through supported automations. If the current version cannot register it directly, provide verified setup or manual execution instructions.
Keep an artifact list in the run history.
Save each run’s video, script, and captions in a separate folder and keep an artifact list.
If I choose per-run review, ask before publishing. If I choose automatic publication, proceed without asking again within the agreed conditions. Ask before changing the channel, visibility, content guidelines, schedule, or budget. Verify and record the upload link, visibility, and scheduled or actual publication time.
After setup, report the task ID, time zone, next run, end conditions, and how to stop it. If an end date cannot be configured, explain that limitation first.