Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →artokun/panel-node-pack-sync
Keep the ComfyUI sidebar panel node-pack (comfyui-agent-panel) in step with the orchestrator after comfyui-mcp updates. Use this whenever the orchestrator was just updated (self_update, npm i -g comfyui-mcp, a new version in the ENVIRONMENT line), when a panel/bridge command fails in a way that smells like version drift ("panel is too old", a graph_/ui_ command the panel doesn't implement, a feature that works in the docs but not in the sidebar), or when the user asks to update/pin/unpin the pan
Passed 12 of 17 test cases with the skill, and 6 of 17 without it.
and 10 more in the full report
9 fixed7 passed either way5 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
The panel status check returned decision "dev-install" and indicates isDevSymlink is true. I want to update my panel to match the latest orchestrator build. What command should you run?
| Checked | Without skill | With skill |
|---|---|---|
| Refuses to modify or sync the developer symlinked checkout. | Missed | Passed |
| Instructs the user to execute git pull inside their local development repository. | Missed | Passed |
The instructions your model reads when the skill loads.
The orchestrator (comfyui-mcp, from npm) and the sidebar panel
(comfyui-agent-panel on the Comfy Registry, repo comfyui-mcp-panel) ship
separately. Updating one does not update the other. A new orchestrator
driving an old panel fails in confusing ways, such as a bridge command the panel
doesn't implement or a feature that exists in the docs but not in the sidebar,
and those failures are hard for a user to diagnose. This skill closes that gap.
Never report a sync that did not happen. This whole feature sits on top of
the fabricate-success fixes (#639/#641): ComfyUI-Manager reports its queue
"drained" even when it never enqueued anything, and a .bak-style copy in
custom_nodes can shadow the real panel in the browser. So the only version
you may ever tell the user is the one read back from disk after the fact.
If the tool throws, the sync FAILED. Say so plainly. Do not soften it, do not
retry it into a success, do not report the version you intended to install.
Never move a pinned user. A pin is a promise. If the user pinned the panel, you warn and stop. You do not unpin for them, you do not "just this once", you do not sync anyway because the new version is obviously better. Offer to clear the pin, and act only if they say yes.
install_comfyui(action:'panel', panel_action:'status')
This never errors. Read these fields:
| Field | Meaning |
|---|---|
installedVersion | The panel version on disk (from its pyproject.toml). |
sync.requiredPanelVersion | The highest panel version this orchestrator build needs. |
sync.decision | What to do — the whole decision is made for you (Step 2). |
sync.summary | Plain-language explanation, safe to paraphrase to the user. |
pin | The active pin: { pinned, version, source: "env"|"settings", reason }. |
shadows | .bak-style copies that shadow the real panel in the browser. |
test cases passed, vs 6 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.