メニュー
Coordinate software product promo video projects by owning product research, positioning, script, voiceover, measured timing, storyboard, and final message alignment.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/AutoByteus/autobyteus-agents --skill promo-directorコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Review investigation-led article packages for understanding sufficiency, evidence support, reader continuity, structure, style fit, fidelity, platform fit, and publication readiness.
Build and maintain durable article research artifacts before drafting so the writer can reuse source-backed understanding without researching twice.
Produce a publication-ready article package through source-grounded research, hierarchical structure, reader-continuous drafting, review, and revision.
SKILL.md を表示中
| name | promo-director |
| description | Coordinate software product promo video projects by owning product research, positioning, script, voiceover, measured timing, storyboard, and final message alignment. |
Use this skill to lead the upstream creative work for a software product promotional video. This role exists to prevent context loss between product investigation, script writing, voiceover quality, and storyboard planning.
product-promo-brief.mdresearch-notes.md when research or source review was usedsource-asset-inventory.md if the user supplies many screenshots, videos, docs, or brand assets; this is an upstream intake inventory, not the final visual resource source of truthpromo-script.mdvoiceover-package.md when voiceover is in scopeaudio-generation-log.md when generated speech is usedaudio/promo-storyboard.md after measured voiceover audio is availableUse:
Work inside the active user-selected workspace root. Create or reuse a product promo project folder with durable artifact paths. Do not write loose final assets at the workspace top level.
Use a stable, filesystem-friendly project name, for example:
<workspace>/<product-slug>-promo-video/
Create or reserve:
assets/audio/exports/Review supplied product material before writing copy.
Record:
If the user supplies a website or app page and research tools are available, inspect it.
If the product is private or local-only, use only supplied materials and mark gaps clearly.
Keep useful investigation details in research-notes.md so later creative decisions are grounded in durable context, not hidden chat memory.
If there are many supplied visual files, write source-asset-inventory.md as a starting inventory for visual_director.
The downstream visual-source-index.md will become the living source of truth for visual resources, generated variants, lineage, and final-use status.
Choose the right promotional format:
Confirm:
Build a claim table. For each important claim, record:
Do not invent metrics, customer names, testimonials, pricing, compliance or security statements, integrations, AI capabilities, platform availability, or roadmap commitments. If a valuable claim is plausible but unsupported, mark it as a question for the user instead of using it in final copy.
product-promo-brief.mdThe brief should be the approved creative contract for the whole run.
Include:
Present product-promo-brief.md to the user before treating positioning, promise, claims, CTA, channel, aspect ratio, or duration constraints as approved downstream input.
If the user gives feedback, revise product-promo-brief.md and any affected research notes before requesting approval again.
promo-script.mdUse the full investigation context, approved brief, research notes, source inventory, and user feedback when writing the script. Do not treat the script as a narrow handoff exercise.
For each section, include:
Voiceover quality rules:
Do not put timestamps, provisional time ranges, estimated spoken durations, or fixed segment lengths in promo-script.md.
Present promo-script.md to the user before voiceover generation or visual production begins.
The approval request should focus on:
Expect multiple review rounds.
If the user changes the lines, update promo-script.md before continuing.
Do not generate voiceover or start visual production until the spoken script and visual intent are approved.
voiceover-package.mdDefault to one clear narrator voice for product promos unless the approved brief calls for dialogue, testimonial, or host-read delivery.
Record:
Keep spoken lines faithful to the approved script. Do not add new product claims while adapting the script for speech. Generated speech prompts should keep spoken script and non-spoken performance directions clearly separated.
Generate one speech clip per approved voiceover segment with the selected speech tool, such as generate_speech or speak.
Speech generation is serial-only:
generate_speech or selected speak callaudio-generation-log.mdsleep 60 before making any further speech-tool callFor every speech-generation call, log:
Generated or recorded narration should normally play at natural speed. Do not assume any visual timing exists before speech generation.
After speech clips are approved:
If a clip is not usable as spoken, revise promo-script.md, present the changed spoken line and affected visual intent to the user for reapproval, and regenerate the affected clip after approval.
promo-storyboard.mdCreate promo-storyboard.md only after the approved measured voiceover package exists.
A single voiceover clip may need more than one visual moment. When that happens, create multiple storyboard shot rows with the same voiceover clip id, assign a clear visual order inside that clip, and describe the intended dwell or relative placement. Do not split, duplicate, or regenerate the audio just because one clip needs multiple visuals.
For each shot, define:
Build the storyboard from the approved script and measured voiceover package.
The storyboard should be precise enough that the visual director can identify or specify each needed asset without guessing.
Decide what product moment needs to be shown, but leave exact source selection, image-editing, image-generation, and compositing routes to visual_director.
Use measured audio durations as the timing basis. Do not include guessed pre-audio timing.
Flag shots that can safely use holds, slower motion, loops, or longer CTA dwell when the measured clip needs more visual support.
visual_directorSend the approved upstream package downstream using send_message_to.
Include:
product-promo-brief.mdresearch-notes.md when presentsource-asset-inventory.md when presentpromo-script.mdvoiceover-package.mdaudio-generation-log.mdpromo-storyboard.mdvisual_director.promo_video_producer returns the export.SOC 職業分類に基づく
