MUST READ before calling externalize_op or save_externalization. Required workflow steps.
MUST READ before calling externalize_op or save_externalization. Required workflow steps.
npx skills add https://github.com/dylanroscover/Embody --skill externalize-operator复制此命令并粘贴到 Claude Code 中以安装该技能
MUST READ before calling create_op. Contains required verification, positioning, and error-checking steps.
MUST READ before writing TD Python via execute_python, set_dat_content, or edit_dat_content. API reference for parameters, storage, operators, threading.
Workflow for running multiple TD instances with Envoy, switching between them, and understanding the instance registry.
MUST READ before first MCP tool call in a session. Complete Envoy tool catalog with parameters and usage.
MUST READ before calling create_extension. Required parameters, lifecycle methods, and wiring steps.
TRIGGER when operator errors appear or user reports broken behavior. Systematic diagnosis workflow.
| name | externalize-operator |
| description | MUST READ before calling externalize_op or save_externalization. Required workflow steps. |
externalize_op tags the operator AND writes it to disk in one step (it calls Update() internally). No separate save is needed.
externalize_op on the operator (auto-detects type if omitted)get_externalization_status to confirm dirty state and file pathembody/ via file inspectionsave_externalization force re-exports an already-externalized operator. Use it after modifying an operator in TD when you need to update its file on disk.
When creating Python files (scripts, extensions, test files, callbacks):
create_op or in TD UI)set_dat_content)externalize_op) — Embody writes the .py file to diskNEVER manually set the file and syncfile parameters — Embody handles all file path management.
Export any COMP as a self-contained .tox with all Embody metadata stripped:
execute_python with op.Embody.ExportPortableTox(target=op('/path/to/comp'), save_path='/output/path.tox')The exported .tox works in any TD project with no missing file errors.
get_externalizations — list all externalized operators with statusget_externalization_status — get dirty state, build number, timestamp, file path for a specific operatorWhen exporting a TDN-strategy COMP whose network contains TD palette components (e.g. abletonLink, Widget components, anything under Samples/Palette/), Embody consults the Tdnpalettehandling par on the Embody COMP's TDN page:
comp.store('_tdn_palette_handling', ...) so repeated exports don't re-prompt."palette_clone": true, skip internal children. Correct for stock palette COMPs.Check and override programmatically: op.Embody.par.Tdnpalettehandling = 'blackbox' | 'fullexport' | 'ask', or force a specific COMP: op('/path/to/comp').store('_tdn_palette_handling', 'fullexport').