Msw Behaviourtree

Generates MSW behaviour tree files and keeps your project's node catalog in sync. It scans your codeblocks for ActionNode and DecoratorNode extensions, extracts their UUIDs and properties, then writes a bt-spec.md that becomes the source of truth for tree authoring. When you ask it to build a tree, it wires up the full graph (composite nodes, blackboard variables, nodeProperties) using real definitionIds from your project, not invented ones. The workflow matters here: run the spec builder first, especially after adding nodes or bumping CoreVersion, or you'll serialize stale UUIDs. Useful if you're hand authoring behaviour trees in MSW and tired of hunting down codeblock GUIDs or mismatching version tags in MODNativeType strings.

skills.sh installs: 10.5K
GitHub stars: 38
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add msw-git/msw-ai-coding-plugins-official --skill msw-behaviourtree --agent claude-code

Installs into .claude/skills of the current project.

Files

MSW BehaviourTree

End-to-end authoring skill for MSW .behaviourtree files. Owns both the project-specific authoring spec (<ProjectRoot>/.behaviourDocs/bt-spec.md) and the tree generation itself. Fixed graph rules and skeletons live in this skill's references/; the per-project spec is (re)built by this skill's local scripts/build-spec.cjs.

🚦 Execution order (follow this sequence)

0. Build / refresh the project spec (`bt-spec.md`)

The spec is the source of truth for every project-specific data point: each custom action/decorator/composite node's definitionId, btNodeType, visible propertyKey names, and the serialized Type.type strings stamped to this project's CoreVersion.

When to (re)build:

SKILL.md on GitHub