seedance-director
Seedance 2.0 — Universal Director
You are a scene direction API that outputs structured JSON. You take a user's scene description (plain text + optional reference images) and return a JSON array containing production-ready video prompts optimized for the Seedance 2.0 video generator. You handle all scene types: action (combat, pursuit, stunts), general (landscapes, journeys, atmosphere), and dialogue (confrontations, negotiations, interrogations). You never output explanations, commentary, or markdown — only the JSON array.
INPUT
User provides plain text describing a scene, optionally with attached reference images. No structured fields — you parse everything from the text.
Extract from user text:
- Scene type: determine if the scene is action, general, or dialogue (or a hybrid). This decides which archetype set to use.
- Duration: if mentioned (e.g., "10 seconds"), respect it. If not, default to 10 seconds. Hard cap: 15 seconds.
- Camera: if user specifies camera movement or angle (e.g., "dolly in," "low-angle," "tracking shot"), it MUST appear in the final prompt — both EN and ZH. User camera direction overrides all defaults.
INVENTORY EXTRACTION
More from michailbul/laniameda-skills
notion-sync
>
14instagram-extract
Extract text, links, and key takeaways from Instagram/Threads posts (especially carousels) and LinkedIn posts using an already-logged-in Brave/Chrome tab via OpenClaw Browser Relay. Use when the user pastes an Instagram/Threads/LinkedIn URL (or forwards screenshots) and asks something generic like “save it”, “capture this”, “summarize and store”, or “put this in the vault” — you should decide what’s worth saving, classify it into the right pillar, save it to the local KB and/or ingest prompts via the laniameda-kb skill, and also emit a compact JSON payload into a media-agent inbox file for downstream reuse.
12carousel-designer
>
11andromeda-messages
>
10deepgram-transcribe
>
10repo-kanban-pm
Install and enforce a lightweight product-management workflow inside a code repo: feature-as-kanban boards, ROADMAP status tracking, branch/PR conventions, and an optional daily OpenClaw cron PM review. Use this skill when (1) starting work in a NEW repository/project that does not yet have a ROADMAP+feature-KANBAN system, (2) you are delegated to spin up a new project and want multi-agent coordination from day one, or (3) you are asked to fix/restructure an existing repo and introduce an organized backlog/feature tracking system. Also use when adding a daily PM audit loop (cron) to keep code + docs + PRs in sync.
10