agentleFS
full-aigc-pluginsfull-aigc-plugins/dreamina-design-plugin/skills/dreamina-seedance-resume/SKILL.md

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.

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
  1. Very specific:

    Use McpDesignClient for all Dreamina Design operations.

    line 18
  2. Very specific:

    Only Draft, DccSelected, and PreviewSpecified may re-invoke the DCC adapter, and only if the on-disk artifact hash no longer matches.

    line 51
  3. Distinctive:

    Never auto-resubmit a paid action.

    line 62
  4. Distinctive:

    Never silently rewrite history.

    line 63
  5. Very specific:

    Never invent a design_submit_id.

    line 64

≈ “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.

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

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.

  1. Load. JobLedger.read() on the user's job file. If the file does not exist, stop and ask the user to specify a valid job_id.
  2. Map state → next action.

    Current stateNext 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 resubmit
    Submittedonly 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)
  3. Never repeat completed work.
    • A Completed job must never be re-submitted or re-exported.
    • A Submitted/Querying/Unknown job must never be re-exported.
    • Only Draft, DccSelected, and PreviewSpecified may re-invoke the DCC adapter, and only if the on-disk artifact hash no longer matches.

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.

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.