BotCurrent↗
← Back to examples

Community recipe · Tool workflows

Transfer source animation onto a reviewed character rig

Source-backed example. Practical decision guidance is proposed and untested; this is not a full implementation guide.

The problem

Animation from one skeleton cannot be reused cleanly on another without inspecting and correcting bone mappings.

Agent job

Import the source animation, propose target-rig mappings, obtain corrections and bake the approved transfer.

Expected output

A retargeted animation track on the chosen rig.

Where this framing comes from
  • Core problem: Editorial purpose framing
  • Agent job: Editorial purpose framing
  • Expected output: Editorial purpose framing
  • Relevant job roles: Editorial purpose framing
  • Benefit type: Editorial purpose framing
Editorial framing and outcome limits

Describes the task’s purpose and intended output; measured benefit, safe unsupervised operation and successful delivery are not established by this framing.

Editorial synthesis based on the linked source. This framing does not add evidence of successful delivery or results.

Case-specific decision guidance · untested

Case-specific decision guidance and first checks are original proposals. The linked source supports the attributed task; this added guidance has not been executed.

Read the attributed source evidence and original caveats below ↓

Why use this

  1. A source motion can use bone names and proportions that only partly resemble the target character. A mapping that looks complete in a table may still twist limbs, move the root incorrectly or overwrite animation the artist intended to keep.

  2. A retargeting review packet could make ambiguous correspondences and preservation requirements explicit before applying constraints or baking keys. The artist could approve the mapping as a separate decision and define the motion checks needed before accepting a reusable track.

Why an agent / simpler alternative

Useful judgment

Compare rig hierarchies and identify ambiguous correspondences rather than treating similar names as sufficient evidence.

Simpler alternative

Use a known, artist-approved retarget preset when source and target rigs follow established compatible conventions.

Unsuitable when

Asset rights are unclear, the target rig is ambiguous or the only scene copy contains irreplaceable animation.

Proposed inputs

  1. Name

    Rig descriptors

    Owner

    Animator

    Minimum scope

    Source and target bone names, hierarchy and rest-pose descriptions

    Quality check

    Identify root, deforming bones and unresolved anatomy.

  2. Name

    Transfer brief

    Owner

    Animator

    Minimum scope

    Licensed asset references, target action and preservation requirements

    Quality check

    Specify existing tracks and scene elements that must remain unchanged.

Access and setup — proposed or unknown

Proposed minimum
  1. Text-only fictional rig descriptions and a mapping proposal; no animation application access.

Compatibility unknowns
  1. Unknown: current runtime, Blender version, add-on behavior, FBX interpretation and constraint compatibility.

External actions requiring approval
  1. Asset access or installation, exact mapping, motion preview, baking and replacing animation; do not enable skip-confirmation by default.

Expected deliverable and review checks

Proposed artifact

Bone-correspondence proposal with confidence notes, unresolved mappings and motion-review criteria.

Critical checks
  1. Anatomically ambiguous mappings remain unresolved for artist review.

  2. A scene-copy and existing-track preservation plan precedes any proposed bake.

Missing output evidence

No new workflow run or output inspection is performed for this editorial layer. The linked implementation evidence retains the original source-specific outcome and artifact limits.

Failure signals and proposed responses

  1. Signal

    A similarly named bone occupies a different hierarchy role.

    Why it matters

    A plausible name match can produce incorrect deformation.

    Proposed response

    Reject the automatic correspondence and request artist-confirmed anatomy.

  2. Signal

    The proposed bake targets an existing action.

    Why it matters

    The transfer could overwrite work the artist needs.

    Proposed response

    Stop and specify a separate action or track with a preserved scene copy.

Effort and cost — unknown

Setup work
  1. Inventory rigs, asset permissions and preserved animation.

Ongoing review
  1. Inspect mapping ambiguity and later motion previews.

Unknowns
  1. Unknown: manual correction effort, add-on compatibility and eventual render or processing costs.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Two fictional rig hierarchies share misleading bone names, and the target contains an existing action with the proposed output name.

Acceptance checks
  1. Flag the anatomical ambiguity.

  2. Require a distinct output action and preserved source scene.

Stop conditions
  1. Real assets, Blender execution, downloads or animation writes are required.

Limits

  1. The proposed checks and safeguards are editorial recommendations, not evidence of successful execution or permission to act. The linked implementation retains its own observed outcome and approval limits.

Tasks: Audio & videoDesign & prototypesResearch & discovery

Useful for: DesignerContent creator

Editorial relevance from the title and source-supported actions; not evidence of the operator’s occupation.
Claude CodeIndependent testing: No

Editorial candidate. This is source-backed reporting or a documented workflow. BotCurrent has not independently tested this task. A proposed Canadian adaptation is not evidence of a Canadian deployment or compliance certification.

Original source

https://github.com/Dev-GOM/claude-code-marketplace/blob/main/plugins/blender-toolkit/skills/SKILL.md ↗

Attributed to: Dev-GOM

Community recipe
Original action type
tool_action
What the source supports
Take an authorized animation FBX and target armature, import the source, inspect and propose bone correspondences, present the mapping for correction, then apply constraints, bake keyframes and add an NLA track.
Source outcome limits
Recipe only. No retargeted motion inspected. Bone-count ratings cannot establish correct anatomy or motion; manual FBX sourcing and mapping review remain necessary.
Evidence attribution caveat
This community recipe describes a procedure; it does not prove successful execution or independently reproduced results.
Source approval description
Two-phase workflow calls for user review and Apply Retargeting in Blender; source also offers skip-confirmation modes for known mappings and asks rather than guessing ambiguous rigs or file paths.
Named tools
Claude Code; original Dev-GOM Blender Toolkit; Blender WebSocket add-on; FBX; Mixamo manual download
Model or version
Unknown
Publication date
Unknown
Source last checked
2026-10-14
Demonstrated in Canada
Unknown
Canadian availability
Unknown
Proposed Canadian adaptation
Proposed: serve Canadian game, animation and training creators using licensed characters and motion files; review cultural/contextual suitability where applicable.
Recommended approval boundaries
Confirm licenses and the target rig; preserve a scene copy; require mapping and motion-preview approval before baking or replacing existing animation. Do not enable skip-confirmation by default.