debug-operator
/debug-operator
TRIGGER when operator errors appear or user reports broken behavior. Systematic diagnosis workflow.
- Author
- dylanroscover ↗
- Repository
- embody ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 1
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.
What it does and when to use it
TRIGGER when operator errors appear or user reports broken behavior. Systematic diagnosis workflow.
Original author description
TRIGGER when operator errors appear or user reports broken behavior. Systematic diagnosis workflow.
How it works
- Common Error Patterns
SKILL.md preview
--- name: debug-operator description: "TRIGGER when operator errors appear or user reports broken behavior. Systematic diagnosis workflow." --- <!-- Generated by Embody/Envoy - Do not remove this comment - sha:c1677e9a9be6b4da --> # Debug Operator Workflow Systematic approach to diagnosing TD operator errors: 1. **Get errors and warnings**: `get_op_errors` with `recurse=true` on the suspected operator and its children. It covers all three surfaces TD paints red: cook errors, Python tracebacks (`kind: 'script'` entries), and GLSL compile failures (`shaderErrors`) 2. **Inspect the operator**: `get_op` to see type, family, parameters, inputs, outputs, children 3. **Check connections**: `get_connections` to verify input/output wiring is correct 4. **Read DAT content**: `get_dat_content` if the operator is a DAT with script errors 5. **Check parameters**: `get_parameter` on specific parameters that might be misconfigured 6. **Check performance**: `get_op_performance` if the issue is cook-time related ## Common Error Patterns - **Missing input**: Operator requires a specific input type -- check connections - **Script error in DAT**: Read the DAT content and fix the Python/expression - **Parameter out of range**: Check parameter values against valid ranges - **Missing operator reference**: An expression or parameter references a non-existent operator - **Script error (Python traceback)**: A raising callback, DAT script, or expression shows a red X but is NOT a cook error -- TD keeps it on a separate surface (`OP.scriptErrors()`), and `op.errors()` reports the op as perfectly clean. Two consequences: read the traceback from `get_op_errors`' `kind: 'script'` entries, and remember these errors PERSIST until cleared. An error thrown during an extension re-init window (the extension object is briefly the old one, so a method added later is missing) stays red long after the code is correct again -- re-cook the owning op, confirm it runs clean, then `clearScriptErrors(recurse=True, error='*')` to clear the stale badge. Field case 2026-08-22: Embody's own manager list sat red on `'EmbodyExt' object has no attribute 'DirtyState'` while the live extension had the method all along. A `SyntaxError ... Context:(Extension 1)` here with a `None` extension means the Extension Object par was set via `.expr` instead of `.val` (see /create-extension). - **Cook error**: The operator can't process its inputs -- check input data types match expectations - **Black or empty render**: Use `capture_top` on the intended output TOP, then check display/render flags on the output and upstream ops; missing light or camera (a 3D scene renders black without both); no cooking Null terminating the chain; a bypass flag left on; resolution is 0; alpha is premultiplied/zero so the image is present but invisible; and whether the op is cooking (check `cookedThisFrame` via `get_op_performance`, or force a cook). After each fix, use `capture_top` again to confirm the frame renders correctly. - **Stale content after a file change (cooks clean, shows old pixels)**: An op can cook with NO errors and the RIGHT resolution yet still hold STALE content. A Movie File In whose `par.file` changed serves its previous cached texture until it cooks on a real frame advance -- `cook(force=True)` in the same frame is not enough. And when a TOP chain's output looks exactly ONE frame stale, suspect same-pass reload propagation: a reload applied mid-pass may not reach downstream ops until the next real frame, even under forced cooks in dependency order. Verify CONTENT, not cook state -- read pixels back (`numpyArray()` / `capture_top`) at the POINT OF CAPTURE (the chain's output, not the source) and confirm they actually changed across a real frame advance. See rules/td-python.md (Cook Model) and rules/performance.md (Movie Export).
Versions
The database has no other skills named debug-operator.
Database snapshot: 13.11.2026 · package version f2a0fdeafabb (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100n8n-debugging-official
Use when an n8n workflow isn't working, errors appear, results don't match what was expected, or the user says "this isn't working." Triggers on errors, unexpected output, "it's not working", "why is this happening", "the workflow stopped", failure investigation, or any debugging context. - 100diagnosing-bugs
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow. - 90ci-debugging
Systematic CI/CD failure diagnosis with hypothesis-first approach, environment delta analysis, and anti-patterns. Use when CI fails, pipelines break, or the user says "CI is failing", "build broke", "pipeline error", or "tests pass locally but fail in CI". - 90diagnosing-bugs
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow. - 90rhdh-operator-pr-test
Tests an rhdh-operator pull request's CI-built operator, operator-bundle, and operator-catalog images on a live OpenShift cluster with oc, and reports evidence plus rollback. Use for "test this operator PR on a cluster", redhat-developer/rhdh-operator PR images or bundles, OLM… - 100kit-debug-prod
Investigate production bugs using logs, traces, error trackers, and metrics. Use when the user reports errors, user/session/trace IDs, timeframes, or status codes. Requires connected tools and/or a team `wire-observability.md`.