godot-deploy
仅当用户**只关心部署/重连本身**(部署 godot mcp / 安装 godot-mcp / setup mcp / godot mcp 连不上 / 端口 9080 没监听 / 重新连接 godot), 或被 godot-dev 因 godot-editor 缺失而让位过来时激活。执行 5 步部署 (Node 检查 → server build → .mcp.json 校验 → 下载 godot-editor → 9080 探测)。 用户提到任何具体游戏内容(做贪吃蛇/做平台跳跃/加玩法/改场景)时 **不要**激活本 Skill,应由 godot-dev 决定是否需要部署。
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- name
- godot-deploy
- description
- 仅当用户**只关心部署/重连本身**(部署 godot mcp / 安装 godot-mcp / setup mcp / godot mcp 连不上 / 端口 9080 没监听 / 重新连接 godot), 或被 godot-dev 因 godot-editor 缺失而让位过来时激活。执行 5 步部署 (Node 检查 → server build → .mcp.json 校验 → 下载 godot-editor → 9080 探测)。 用户提到任何具体游戏内容(做贪吃蛇/做平台跳跃/加玩法/改场景)时 **不要**激活本 Skill,应由 godot-dev 决定是否需要部署。
03 SKILL.md 正文
Godot MCP 部署 / 重连(Skill 自执行版)
严格遵循 docs/需求文档/4.23.md: MCP 只做编辑器单元操作;部署、构建、命令执行全部由 Skill 自己跑 shell。
路径变量约定:
${PLUGIN_ROOT}= 本插件根目录(含server/、addons/godot_mcp/、templates/),由 Codebuddy 环境变量CODEBUDDY_PLUGIN_ROOT提供${WORKSPACE}= 用户当前工作区根目录,由 Agent 上下文提供
工作区目录契约(4.23.md 强制,子 Skill 必须遵守,详见 godot-dev/SKILL.md):
${WORKSPACE}/
├── godot-editor/ ← 本 Skill 步骤 4 下载到这里
├── active-game.json ← godot-new 写入
├── game1/ game2/ ... ← godot-new 创建
本 Skill 只负责前者(godot-editor),其他由 godot-new 维护。
5 步部署流程(必须按顺序执行,每一步真实跑命令并把输出贴回对话)
步骤 1 — 检查 Node.js >= 18
$nodeVer = (& node --version) 2>$null
if (-not $nodeVer) { Write-Host "[FAIL] Node.js 未安装"; return }
$major = [int]($nodeVer.TrimStart('v').Split('.')[0])
if ($major -lt 18) { Write-Host "[FAIL] Node.js $nodeVer < 18" } else { Write-Host "[OK] Node.js $nodeVer" }
失败处置:让用户去 https://nodejs.org 安装 18 LTS+,安装后让用户重新触发部署。 不要继续后面步骤。
步骤 2 — 检查 / 构建 MCP Server
$dist = Join-Path "${env:CODEBUDDY_PLUGIN_ROOT}" "server\dist\index.js"
if (Test-Path $dist) {
Write-Host "[OK] dist/index.js 已就绪"
} else {
Write-Host "[BUILD] dist 缺失,开始 npm install + npm run build"
Push-Location (Join-Path "${env:CODEBUDDY_PLUGIN_ROOT}" "server")
npm install
if ($LASTEXITCODE -ne 0) { Pop-Location; Write-Host "[FAIL] npm install"; return }
npm run build
if ($LASTEXITCODE -ne 0) { Pop-Location; Write-Host "[FAIL] npm run build"; return }
Pop-Location
if (Test-Path $dist) { Write-Host "[OK] 构建完成" } else { Write-Host "[FAIL] dist 仍缺失" }
}
用户说「跳过安装 / skip-install」时,省略
npm install,仅跑npm run build。
失败处置:把 npm 末尾输出贴给用户,提示检查代理 / 镜像 / 磁盘空间。
步骤 3 — 确认 .mcp.json 已注册到 Codebuddy
$mcpJson = Join-Path "${env:CODEBUDDY_PLUGIN_ROOT}" ".mcp.json"
if (Test-Path $mcpJson) { Write-Host "[OK] .mcp.json 已存在" } else { Write-Host "[WARN] .mcp.json 缺失" }
向用户提示:插件启用时 .mcp.json 已自动注册 godot-mcp;若工具列表里
看不到,运行 /reload-plugins。
步骤 4 — 确认本地有 Godot 编辑器(按需下载到工作区)
这是 4.23.md 场景 1 明确要求的「下载 godot 编辑器」环节。 目录契约(4.23.md 强制):编辑器必须落到
${WORKSPACE}/godot-editor/, 与各个 game 目录、active-game.json平铺同级。严禁放到插件目录或 用户目录——godot-dev 与 godot-new 都按这个位置去找编辑器。
$ws = "${WORKSPACE}" # Agent 已知的当前工作区绝对路径
$editorDir = Join-Path $ws "godot-editor"
$editorExe = Get-ChildItem -Path $editorDir -Filter "Godot_v*.exe" -Recurse -ErrorAction SilentlyContinue | Select-Object -First 1
if (-not $editorExe) {
Write-Host "[INFO] ${ws}\godot-editor 下未发现 Godot,准备下载 4.6 stable"
New-Item -ItemType Directory -Path $editorDir -Force | Out-Null
$url = "https://github.com/godotengine/godot/releases/download/4.6-stable/Godot_v4.6-stable_win64.exe.zip"
$zip = Join-Path $editorDir "godot.zip"
Invoke-WebRequest -Uri $url -OutFile $zip -UseBasicParsing
Expand-Archive -Path $zip -DestinationPath $editorDir -Force
Remove-Item $zip
$editorExe = Get-ChildItem -Path $editorDir -Filter "Godot_v*.exe" -Recurse | Select-Object -First 1
}
if ($editorExe) { Write-Host "[OK] Godot editor: $($editorExe.FullName)" } else { Write-Host "[FAIL] Godot editor 不可用" }
用户系统 PATH 中已有 Godot(
godot --version可用)也不算通过—— 4.23.md 要求统一落到${WORKSPACE}/godot-editor/,否则其他 Skill 无法定位。 仍然按上面流程下载;下载失败时再回退到提示用户手动放置。
失败处置:网络问题让用户手动到 https://godotengine.org/download 下载并解压
到 ${WORKSPACE}/godot-editor/(不是插件目录!)后重新触发。
步骤 5 — TCP 探测 Godot 9080 + 引导用户启用插件
$probe = Test-NetConnection -ComputerName 127.0.0.1 -Port 9080 `
-InformationLevel Quiet -WarningAction SilentlyContinue
if ($probe) { Write-Host "[OK] Godot 编辑器在 9080 监听" }
else { Write-Host "[WAIT] 9080 未监听" }
[WAIT] 时给用户清晰的 5 行操作说明:
1. 用 Godot 编辑器打开当前游戏目录(或将要创建的项目目录)
2. 菜单:Project → Project Settings → Plugins
3. 把 GodotMCP 切到 Enabled
4. 状态栏出现 "MCP: Listening on port 9080" 即可
5. 然后对我说「再检查一次部署」即可重跑步骤 5
部署成功后
输出汇总:
[1/5] check_node_version ✓ Node.js v20.x 满足 >=18
[2/5] check_mcp_server_build ✓ dist/index.js 已就绪
[3/5] codebuddy_registration ✓ .mcp.json 已注册
[4/5] godot_editor_available ✓ Godot v4.6
[5/5] check_godot_listening_port ✓ 端口 9080 监听中
✓ Godot MCP 部署完成。现在可以让 godot-dev 帮你做游戏了。
如果是从 godot-dev 场景 1 让位过来,不要自动跳回 godot-dev——而是 明确告诉用户:「部署完成。请告诉我你想做什么游戏,我会接着用 godot-new 为你创建项目。」让用户重新触发即可。
严禁行为
- ❌ 不要调用任何 MCP 工具去检查部署状态(旧的
godot_deploy已删除) - ❌ 不要自己改
.mcp.json/package.json - ❌ 不要自动启动
Godot_v*.exe—— Godot 启用插件需要用户在 GUI 操作 - ❌ 不要在步骤失败后立刻重试,要先让用户处理根因
失败处理对照表
| 失败步骤 | 给用户的指引 |
|---|---|
| Node.js | 安装 https://nodejs.org 18 LTS+ |
| npm install / build | 贴 npm 输出末尾 / 检查代理 / npm config get registry |
| Godot editor 下载 | 检查网络 / 手动下载到 ${PLUGIN_ROOT}/godot-editor/ |
| 9080 未监听 | 见步骤 5 的 5 行操作说明 |
04 同仓库更多 Skills
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
internal-comms
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
algorithmic-art
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
theme-factory
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.