dreamina-seedance-resume
Skill0 starsChanged 23 days agoApache-2.0View on GitHub
Resume a paused Dreamina 3D job from its ledger state. Use when the user wants to continue an in-flight job without re-paying or re-exporting.
In this repository30 other files it gives its agents.
- AGENTS.mdAGENTS.md
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- openspec-update-changeSkill
- dreamina-auto-seedanceSkill
- dreamina-cli-image2imageSkill
- dreamina-cli-image2videoSkill
- dreamina-cliSkill
- dreamina-cli-text2imageSkill
- dreamina-cli-text2videoSkill
- dreamina-design-harnessSkill
- dreamina-design-useSkill
- dreamina-opencli-image2imageSkill
- dreamina-opencli-image2videoSkill
- dreamina-opencli-text2imageSkill
- dreamina-opencli-text2videoSkill
- dreamina-prompt-image2imageSkill
- dreamina-prompt-image2videoSkill
- dreamina-prompt-text2imageSkill
- dreamina-prompt-text2videoSkill
- dreamina-shot-annotatorSkill
- dreamina-video-evaluatorSkill
- dreamina-video-productionSkill
- dreamina-video-shotsSkill
- dreamina-video-syncSkill
- dreamina-vision-judgeSkill
- dreamina-visual-targetSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Use McpDesignClient for all Dreamina Design operations.
- Very specific: line 51
Only Draft, DccSelected, and PreviewSpecified may re-invoke the DCC adapter, and only if the on-disk artifact hash no longer matches.
- Distinctive: line 62
Never auto-resubmit a paid action.
- Distinctive: line 63
Never silently rewrite history.
- Very specific: line 64
Never invent a design_submit_id.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
dreamina-seedance-resume
When to use
The user references an existing job id and wants to continue without restarting local export or remote submission. The job ledger is the single source of truth for what has already happened.
Use McpDesignClient for all Dreamina Design operations. Resume may call only
the typed status, account, submit, and query mappings; after a stored
design_submit_id exists it may call only the query mapping.
Workflow
For a persisted auto_with_budget job, automatically resume only the safe
next state: capability/quote work before a submission, or query/download work
after its stored submit identifier. Never convert a budget stop, missing web
prerequisite, failed validation, Unknown, or failed job into a new paid
submission without a new user instruction.
- Load.
JobLedger.read()on the user's job file. If the file does not exist, stop and ask the user to specify a validjob_id. Map state → next action.
Current state Next action Draftask the user to choose a companion DCC DccSelectedresume from the PreviewSpecified step PreviewSpecifiedre-validate the existing preview receipt; on mismatch re-export PreviewValidatedresume capability resolution CapabilityResolvedresume quote (do not reuse a quote for inputs that have changed) Quotedask the user to confirm or reject the quote Approvedcheck submit.design_submit_id— if present, only query, never resubmitSubmittedonly query the design plugin; never re-export or re-submit Queryingcontinue polling Completedverify the on-disk artifact hash; if missing, transition to Failed Failed/Unknownask the user to authorise a recovery action (re-quote / re-query / restart) - Never repeat completed work.
- A
Completedjob must never be re-submitted or re-exported. - A
Submitted/Querying/Unknownjob must never be re-exported. - Only
Draft,DccSelected, andPreviewSpecifiedmay re-invoke the DCC adapter, and only if the on-disk artifact hash no longer matches.
- A
Resume from persisted evidence, not a reconstructed identifier:
{"state":"Querying","design_submit_id":"<stored-submit-id>","next_action":"query_only"}Never do
- Never auto-resubmit a paid action.
- Never silently rewrite history; append to the job ledger instead.
- Never invent a
design_submit_id; the design plugin is the only source.
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
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.

