Run any Skill in Manus with one click

setup

Stars9

Forks2

UpdatedJune 12, 2026 at 05:34

Setup / health check for bpkit — verify the editor channel, Python, Remote Execution, AND that the native ctypes bridge resolves on THIS editor build. Adaptive: diagnose and self-heal, don't hard-fail. Run after pulling the repo.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

sinkingsugar

sinkingsugar/bpkit

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	setup
description	Setup / health check for bpkit — verify the editor channel, Python, Remote Execution, AND that the native ctypes bridge resolves on THIS editor build. Adaptive: diagnose and self-heal, don't hard-fail. Run after pulling the repo.

Run bpkit's readiness check as a smart diagnosis, not a pass/fail script — your job is to get it working, adapting where needed and only reporting a real blocker if you genuinely can't. $py = bpkit.config.BUNDLED_PYTHON (or $env:BPKIT_PYTHON; bare python may hit the disabled Windows Store alias — use the engine's bundled interpreter).

1. Channel

& $py ue_run.py bpkit/ops/ping.py

ENGINE_VERSION printed → live.
no editor node found → editor not running, the Python plugin disabled, or Remote Execution off. Tell the user: launch the editor; confirm Edit → Plugins → "Python Editor Script Plugin" is enabled (restart the editor after enabling — without it the remote-exec setting doesn't even exist); then Project Settings → Plugins → Python → enable "Remote Execution"; re-run /setup.
- A Dev Kit update RESETS Remote Execution to off (Epic launcher update replaces the project config; observed 2026-06-12, 364449→365199). If the channel worked before and the engine version in the log/ping changed, re-enable the setting first — don't debug anything else. Spot it host-side: tail ...\UE4\Saved\Logs\ConanSandbox.log and check the AppVersion.
Python path error → set $env:BPKIT_PYTHON to <engine>\Engine\Binaries\ThirdParty\Python3\Win64\python.exe (or edit BPKIT_ENGINE_ROOT in bpkit/config.py).

2. Native bridge (the important diagnosis)

& $py ue_run.py bpkit/ops/selftest.py — resolves every exported symbol the ctypes bridge calls on THIS editor build, plus one read-only native call.

BRIDGE OK → the native layer works here; nothing to do.
One or more FAIL → do NOT hard-fail. Adapt. The decorated names are MSVC-mangled and stable across UE5, but a different build can differ. For each failed symbol:
1. Note its DLL (the 2nd element of that key's bpkit.bridge.SYM entry) under <engine>\Engine\Binaries\Win64\.
2. Find the current decorated name: & $py -m bpkit.pe "<that DLL>" <a substring of the C++ function, e.g. ImportNodesFromText>.
3. Patch that entry in bpkit/bridge.py SYM with the name pe reports, then re-run selftest. Repeat until BRIDGE OK.
- If a symbol simply isn't exported at all, this probably isn't an editor build (shipping/monolithic) — the bridge needs an editor build; say so.
functional ... : False (but symbols resolved) → calls resolve but the probe didn't round-trip; re-run after confirming you're not mid-compile, and sanity-check find_object.

3. Report

Short status: channel up? · bridge OK (or exactly what you adapted)? · then the ready commands: /bp-channel, /bp-read <asset>, /bp-test, and /install (use these from any project). Run /bp-test if you want full functional coverage beyond the symbol check.

More from this repository

same repository

bpkit

sinkingsugar/bpkit

Drive Unreal Engine 5 Blueprint graphs from outside the editor with bpkit — read, author, edit, inject and compile K2 node graphs over the remote-exec channel. Use for ANY UE Blueprint node-graph task: authoring nodes, fixing pins, mod authoring, reading a graph — AND for answering "how does this game mechanic work?" by reading the game's own shipped Blueprints. (Windows + an editor build with Remote Execution on.)

2026-06-109

deploy

sinkingsugar/bpkit

Build and deploy a mod from this repo into the live Unreal editor — import its source assets, run its Blueprint build steps in order, then verify. Argument is the mod folder name under mods/ (or a path), e.g. mounted-followers.

2026-06-109

bp-channel

sinkingsugar/bpkit

Quick check that the Unreal editor remote-exec channel is live. Use before driving the editor, or when in-editor calls seem to hang.

2026-06-069

bp-read

sinkingsugar/bpkit

Read an Unreal blueprint's node graphs and show a dense, navigable outline. Use when inspecting or understanding a Blueprint's logic. Argument is the asset path, e.g. /Game/Foo/BP_Bar.

2026-06-069

bp-test

sinkingsugar/bpkit

Run the bpkit test suites — the offline library tests (no editor) and, if the editor is up, the in-editor authoring tests.

2026-06-069

install

sinkingsugar/bpkit

Install the bpkit slash-commands into your personal ~/.claude/skills so they work from any project directory, not just this repo. Run once after pulling the repo (and again after repo updates).

2026-06-069

name	setup
description	Setup / health check for bpkit — verify the editor channel, Python, Remote Execution, AND that the native ctypes bridge resolves on THIS editor build. Adaptive: diagnose and self-heal, don't hard-fail. Run after pulling the repo.

1. Channel

& $py ue_run.py bpkit/ops/ping.py

ENGINE_VERSION printed → live.
no editor node found → editor not running, the Python plugin disabled, or Remote Execution off. Tell the user: launch the editor; confirm Edit → Plugins → "Python Editor Script Plugin" is enabled (restart the editor after enabling — without it the remote-exec setting doesn't even exist); then Project Settings → Plugins → Python → enable "Remote Execution"; re-run /setup.
- A Dev Kit update RESETS Remote Execution to off (Epic launcher update replaces the project config; observed 2026-06-12, 364449→365199). If the channel worked before and the engine version in the log/ping changed, re-enable the setting first — don't debug anything else. Spot it host-side: tail ...\UE4\Saved\Logs\ConanSandbox.log and check the AppVersion.
Python path error → set $env:BPKIT_PYTHON to <engine>\Engine\Binaries\ThirdParty\Python3\Win64\python.exe (or edit BPKIT_ENGINE_ROOT in bpkit/config.py).

2. Native bridge (the important diagnosis)

& $py ue_run.py bpkit/ops/selftest.py — resolves every exported symbol the ctypes bridge calls on THIS editor build, plus one read-only native call.

BRIDGE OK → the native layer works here; nothing to do.
One or more FAIL → do NOT hard-fail. Adapt. The decorated names are MSVC-mangled and stable across UE5, but a different build can differ. For each failed symbol:
1. Note its DLL (the 2nd element of that key's bpkit.bridge.SYM entry) under <engine>\Engine\Binaries\Win64\.
2. Find the current decorated name: & $py -m bpkit.pe "<that DLL>" <a substring of the C++ function, e.g. ImportNodesFromText>.
3. Patch that entry in bpkit/bridge.py SYM with the name pe reports, then re-run selftest. Repeat until BRIDGE OK.
- If a symbol simply isn't exported at all, this probably isn't an editor build (shipping/monolithic) — the bridge needs an editor build; say so.
functional ... : False (but symbols resolved) → calls resolve but the probe didn't round-trip; re-run after confirming you're not mid-compile, and sanity-check find_object.