// ET Excel MCP workflow for reading, writing, styling, transforming, and inspecting xlsx data. Use when operating Excel cells, ranges, sheets, formulas, charts, merges, batch data import/export, or editing Luban source spreadsheets before export.
| name | et-excel |
| description | ET Excel MCP workflow for reading, writing, styling, transforming, and inspecting xlsx data. Use when operating Excel cells, ranges, sheets, formulas, charts, merges, batch data import/export, or editing Luban source spreadsheets before export. |
只要涉及 Excel/xlsx 的任何读写操作，都必须调用 excelmcp（ET.ExcelMcp）完成；禁止手写脚本或用其它库/工具直接改 xlsx。
excelmcp 源工程位置：./Packages/cn.etetet.config/DotNet~/ET.ExcelMcp。
运行入口（编译产物）：仓库根目录 ./Bin/ET.ExcelMcp.dll，统一在仓库根用 dotnet ./Bin/ET.ExcelMcp.dll ... 调用。
若 ./Bin/ET.ExcelMcp.dll 不存在（没有可执行文件），先编译工程再操作：
dotnet build "./Packages/cn.etetet.config/DotNet~/ET.ExcelMcp/ET.ExcelMcp.csproj" -c Debug
产物会输出到 ./Bin/ET.ExcelMcp.dll（csproj 的 OutputPath = $(RepoRoot)Bin，RepoRoot 即仓库根）。
Bin/ET.ExcelMcp.dll 读写 Excelet-luban）cli list 或 cli help <工具名>，不要硬背完整工具表。excel_range / excel_data_operations，不要逐格操作。pwsh 中优先外层单引号。__beans__/__enums__/多态数据表时：用 excel_data_operations batch_write 只写非空格（空行真空）；写完必须 excel_merge_cells merge 合并"列表"表头（*fields J1:P1、*items H1:L1、多态字段表头跨子列宽），否则 Luban 导出报缺 alias 列；含中文走 Write→UTF-8 Python→ExcelMcp，读回校验合并用 get_merged、文本用 ascii()。完整格式见 et-luban。et-luban。Assets/.../xxx.prefab 这类完整路径，应收敛为 xxx（加载侧按名字 LoadAsset）。__tables__.xlsx：补全 Category / value_type / input / index / group，否则 Luban 导不到这张表。s / c / cs），避免全量导出超时；导出与导出后 Unity 刷新走 et-luban。xlsx 的 sharedStrings.xml，不要只信终端输出（详见 references/et-excel-cli.md 的「中文写入防乱码」）。dotnet ./Bin/ET.ExcelMcp.dll cli listdotnet ./Bin/ET.ExcelMcp.dll cli help <工具名>dotnet ./Bin/ET.ExcelMcp.dll cli <工具名> '<JSON参数>'references/et-excel-cli.md：工具选择、pwsh JSON 传参、常用示例ET EUI client UI workflow for this project's cn.etetet.eui framework. Use when creating or modifying DlgXxx windows, ESxxx reusable sub-UI, ItemXxx loop items, AUIEvent handlers, WindowID registration, widget binding (E* via UIFindHelper), ShowWindow/Hide/Close flow, EUI root layers, or LoopScrollRect lists. Hand-authored 5-file pattern; there is NO code-gen menu here.
ET Luban export workflow. Use when exporting generated C# config/data code, refreshing aggregated luban.conf, validating CodeMode outputs, or troubleshooting ET.ExcelExporter, LubanGen.ps1, table definitions, beans, enums, Defines, and Luban export failures.
AIBridge batch and multi command automation. Use when Codex needs to run multiple Unity Editor CLI operations together, write batch scripts, use multi --cmd or multi --stdin, handle call/delay/log/menu lines, avoid PowerShell quoting issues, or automate long/JSON-heavy AIBridgeCLI workflows.
Optional read-only AIBridge Code Index semantic lookup for Unity projects. Use only when this Skill is installed and project rules or AIBridge settings say Code Index is enabled. Use for CLI-only symbol, definition, reference, implementation, derived-type, caller, and diagnostic queries. Do not use when Code Index is disabled; use rg, host file reads, and regular AIBridge commands instead.
Unity Prefab asset patch workflow for AIBridge. Use when modifying complex prefab assets with prefab patch operations, child or component creation, SerializedProperty writes, array edits, internal GameObject/component references, dry-run validation, or when deciding between prefab patch, inspector set_property, scene object commands, and direct Unity YAML fallback.
Unity Editor and Player Runtime CLI integration for AIBridge. Use when Codex needs to compile Unity, inspect Console logs, search/read assets, manipulate GameObjects, Transforms, components, SerializedProperty values, scenes, screenshots/GIFs, connect to built Player runtime targets, simulate Play Mode runtime input, editor focus/menu items/game view, or look up AIBridgeCLI command syntax. For batch/multi scripts use aibridge-batch-script. For complex prefab asset edits use aibridge-prefab-patch. For unsupported direct Unity YAML serialized asset edits use unity-yaml-editing.