agentleFS
full-aigc-pluginsfull-aigc-plugins/blender-design-plugin/skills/blender-seedance-pipeline/SKILL.md

blender-seedance-pipeline

Skill4 starsChanged 21 days agoApache-2.0View on GitHub

Drive a Blender preview through the validated Dreamina 3D pipeline. Use when the user has a Blender scene and wants a Seedance 2.5 render from it.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 3 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When the user provides one auto_with_budget envelope — approved reference upload, model/resolution/duration preferences, a maximum charge, …

    line 22
  2. Distinctive:

    Stop and ask only when the quote exceeds the cap, a required reference was not authorized for upload, a platform-mandated confirmation or …

    line 30
  3. Very specific:

    Inspect: Call inspect_scene(executable=blender-design_adapter, scene=<user_scene>).

    line 41
  4. Very specific:

    Export: Call request_preview_export(...) with the user's prompt metadata embedded in the request payload.

    line 45
  5. Very specific:

    Validate: Run validate_artifact(receipt, current_file) from the dreamina-design plugin scripts/seedance_pipeline/handoff_validator.py.

    line 49
  6. Very specific:

    Resolve readiness: Use the dreamina-design MCP tools to call dreamina_cli_status and dreamina_account.

    line 52
  7. Very specific:

    Never resubmit a job whose design_submit_id is already set.

    line 76
  8. Distinctive:

    Never skip the preview validation gate.

    line 77
  9. Distinctive:

    Never send DCC scene data to the design plugin — only the validated artifact reference (artifact_id + sha256), the user prompt, and the …

    line 78
  10. Very specific:

    Never use the dreamina-design fixture-only design_handoff.py for a production route.

    line 81

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

blender-seedance-pipeline

When to use

The user wants a Dreamina 3D render from a Blender scene. Companion blender-design is already installed.

Workflow

Automatic run policy

When the user provides one auto_with_budget envelope — approved reference upload, model/resolution/duration preferences, a maximum charge, and permission for one remote submission — perform the following workflow without asking at every state transition. Resolve capability, validate the preview, obtain and compare the quote, submit once only when it is within the cap, query the recorded identifier, download, and independently verify the final artifact. Return one final artifact inventory.

Stop and ask only when the quote exceeds the cap, a required reference was not authorized for upload, a platform-mandated confirmation or web prerequisite is pending, validation fails, or recovery would require another paid submission. interactive retains the review at each gate; review_only does not upload or submit.

Because Dreamina Design currently exposes no authoritative quote tool, auto_with_budget stops at QUOTE_UNAVAILABLE. The user may instead approve one fully specified auto_exact_request; that grants one submission only and does not bypass the native paid-action approval in Dreamina Design.

  1. Inspect. Call inspect_scene(executable=blender-design_adapter, scene=<user_scene>). Reject if the scene cannot be inspected.
  2. Specify preview. Collect user-approved camera, frame range, output path, and dimensions. Build a PreviewSpec.
  3. Export. Call request_preview_export(...) with the user's prompt metadata embedded in the request payload. Independent re-hash is performed by the orchestrator — never trust the producer's declared sha256 alone.
  4. Validate. Run validate_artifact(receipt, current_file) from the dreamina-design plugin scripts/seedance_pipeline/handoff_validator.py. On any error, transition the job to Failed with the classified error_category.
  5. Resolve readiness. Use the dreamina-design MCP tools to call dreamina_cli_status and dreamina_account. On user action required, stop with the returned remediation.
  6. Bind request. Build QuoteInputs(prompt, model, resolution, ratio, duration) and the validated preview reference. Record that an authoritative quote is unavailable; never synthesize one.
  7. Authorize. Require auto_exact_request (or a future authoritative quote within auto_with_budget) plus reference-upload and one-submit flags.
  8. Submit. Let the dreamina-design MCP tools call dreamina_submit_video; Dreamina Design obtains native approval internally. Persist submit_id before reporting Submitted.
  9. Query. Let the dreamina-design MCP tools call dreamina_query_task for the stored identifier and approved download root. Unknown is query-only.
  10. Download + verify. Re-hash the downloaded artifact and compare to the declared hash; reject on mismatch.

Ledger transitions

Drive the job through Draft → DccSelected → PreviewSpecified → PreviewValidated → CapabilityResolved → Quoted → Approved → Submitted → Querying → Completed | Failed | Unknown exactly once each.

Never do

  • Never resubmit a job whose design_submit_id is already set.
  • Never skip the preview validation gate.
  • Never send DCC scene data to the design plugin — only the validated artifact reference (artifact_id + sha256), the user prompt, and the quote inputs.
  • Never use the dreamina-design fixture-only design_handoff.py for a production route. It is a fixture-only compatibility harness for deterministic tests.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.