Scene Beat Designer

This skill requires the installed Renku runtime. If renku is unavailable, stop and direct the user to https://gorenku.com; do not substitute ad hoc files for the CLI-owned project state.

Efficient Command Use

Use --project <project-name> on screenplay beats commands when the project is known. Read current Beat context once; list/show only for missing revision detail. Create, reset, and apply validate before writes. Separate validation is for validation-only intent or a review pause; retain a meaningful apply --dry-run when reviewing a proposed change. Use returned exact revision and Beat identities for the next step. Refresh context after relevant edits or intervening user review, and keep Storyboard/media review separate.

When requesting visual references, resolve their assetFileId and assetFileId through visualReferences.assets. Lookbook placements retain their annotations and assetFileId; reference groups retain roles, subjects, and selection facts.

Consult the relevant CLI reference/help once if syntax is unknown, then reuse verified syntax for this task. Do not discover syntax by attempting mutations. Do not invent project list. If a known permission denial blocks cache/output/config or local-network access, explain the requirement and use the authorized host permission flow; do not repeat the denied attempt, read secrets, disable cache persistence, or change permissions. CLI026 means the mutation succeeded: report the notification warning without replaying the mutation.

Project Workspace

Keep every agent-created working file inside the current Project's categorized tmp/ tree. Never create operation JSON, Generation Specs, import manifests, QA images, downloads, crops, or scratch files at the Project root.