菜单
Placeholder — the original marketplace download shipped a zero-byte `SKILL.md`. Restore the body from the source marketplace before activating this skill. The two `references/*.md` files (`test-templates.md`, `sample-size-guide.md`) are intact.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | ab-test-setup |
| description | Placeholder — the original marketplace download shipped a zero-byte `SKILL.md`. Restore the body from the source marketplace before activating this skill. The two `references/*.md` files (`test-templates.md`, `sample-size-guide.md`) are intact. |
| license | MIT |
Status: body missing. The marketplace export delivered a zero-byte file for this skill on download. Re-pull from the source to restore. References under
notes/skills/ab-test-setup/references/are present and useful on their own.
Write effective prompts for Seedance 2.0 (bytedance/seedance-2.0) multimodal video generation — the official basic prompt formula (Subject+Motion required; Environment/Aesthetics/Camera/Audio optional), the @ reference system (@Image1/@Video1/@Audio1 role assignment, equivalent to the guide's plain Image 1/Video 1), camera-language vocabulary, time-segmented prompt structure, in-video text (slogans/titles, subtitles, speech bubbles), and capability-specific patterns (character consistency, camera/effects replication, video extension, editing, track completion / multi-clip stitching, music beat-matching, dialogue, one-take, e-commerce, educational). A craft overlay on the art-director step: the output prompt is fed to `ralphy generate video --model bytedance/seedance-2.0`, never to a provider API directly. USE WHEN the user is generating video with seedance and needs a prompt drafted or improved, asks "write a seedance prompt", "how do I reference my uploaded image/video in the prompt", wants beat-synced cuts
Publish or schedule a finished Ralphy Unit through the active workspace's saved Postiz connection. Prepares the target-shaped title, description, body, CTA, hashtags, thread parts, and required Postiz settings, then calls `ralphy publish` and records provenance for later analytics. USE WHEN the user asks to "publish this", "post it now", "schedule this post", "send this to Telegram", "post this thread to X", "publish the reel", or "put this on YouTube/Instagram". DO NOT FIRE for copy-only requests with no posting intent; use social-copy instead.
Run an autonomous, issue-driven development loop over Ralphy itself — the same cadence as a focused maintainer session: pick the open `notes/issues/`, order them by dependency, then for each issue dispatch a scoped sub-agent, review its diff, run the real gates, and commit + push to main before moving to the next. Sequential by default (one agent at a time) so changes never collide on shared files. Default scope is ALL open issues with a safety limit of 25; the user can widen the scope or raise the limit in their prompt. Pauses for the user only at genuine decision forks and before any paid generation or irreversible/outward-facing action. USE WHEN the user types `/dev-loop`, says "work through the issues", "run the dev loop", "grind the backlog", "implement all the open issues", "keep going through notes/issues until done", or after `/dev-issues` has filed a batch they now want executed. DO NOT FIRE for a single issue (just implement it), for content/video production, or when there are no open issues to exec
Publish a finished Ralphy unit and its reusable blocks to the public library. Use when the user asks to publish a template, unit, style, recipe, or asset to the library. The CLI prepares the entity bundle; the sibling ralphy-web repository owns the committed library and upload script.
Cut a Ralphy CLI release across GitHub Releases, Homebrew, and npm. Use when the user asks to release, tag, publish, or prepare release notes for the CLI. Public documentation and the marketing site live in sibling repositories and are synchronized separately when their content is affected.
The eval-to-repair loop — the consumer of the evaluator's report (#409). Reads the eval output (eval-deep-vision.json's `what_to_redo` first, else eval.json `findings[]`), runs `ralphy project repair-plan <id>` to classify every finding by owner (art-director / scenarist / editor) and order it by severity, presents the ordered plan grouped by owner, gets the user's approval, then applies targeted fixes through the EXISTING `ralphy` verbs (art-director regen / scenarist rewrite / editor recut), re-renders, re-evals, and compares the old vs new verdict. HARD GATE: no paid model regeneration runs until the user approves the plan (or previously opted into batch repair). The deterministic `repair-plan` step itself makes ZERO model calls and is safe to run unprompted. USE WHEN the user says "fix the eval", "repair this render", "make it shippable", "fix the issues / problems / findings", "address the eval", "now fix it", "make the fixes", or hands off a failed / warn eval and asks what's next. ALSO FIRE right after
