Use this skill for data-layer Skyrim Special Edition modding through the configured houseCARL MCP server. houseCARL reads a Mod Organizer 2 instance, resolves the true load-order winner, and writes changes into reviewable patch plugins; original source mods are never edited.
Core workflow
- Confirm context when it matters:
housecarl_load_order_statusfor profile/plugin status, or to check whether a mod or plugin is active.housecarl_set_mo2_instancewhen the user gives a new MO2 instance folder.
- Read before any record write:
mutagen-referenceto verify field names, writability, enum values, and composed-struct shapes.housecarl_read_recordorhousecarl_batch_record_detailto inspect the current winner. Addconflict_tree=truefor contested records or when winner provenance matters.housecarl_cross_plugin_queryto locate records or references across the load order.
- Pick the narrowest write tool:
housecarl_set_fieldfor a single scalar or simple-collection edit.housecarl_bulk_applyfor several edits in one patch, dict merges, leveled-list entries, effects, or other composed structs.housecarl_create_recordfor a new top-level record (it needs an EditorID).housecarl_remove_recordonly to drop a record or override from a houseCARL-owned patch — never from a source mod.
- Accumulate related edits into one patch with
into=<patch filename>after the first write returns a patch name. - Prefer runtime, no-ESP INI systems when they fit the user's intent:
skypatcher-authoringfor SkyPatcher record edits.spid-authoringfor distributing spells, perks, items, factions, outfits, or packages to NPCs.kid-authoringfor distributing keywords onto items.
papyrus-referencebefore answering any Papyrus or SKSE function-signature question.
FormID notes
houseCARL tools use XXXXXX:Plugin.esp FormIDs — six hex digits, then the filename of the master that defines the record. SkyPatcher, SPID, and KID each use their own FormID syntax; consult their skills before writing INI lines.
Safety notes
- houseCARL patches are reviewable output mods. Tell the user which patch was created or extended.
- Don't invent schemas or field paths. If
mutagen-referencehas no entry for a type, say so directly rather than guessing. - Don't reach for record edits when the user explicitly wants a no-ESP / runtime distribution file — use SkyPatcher, SPID, or KID instead.
V5 multi-provider + discovery (pack extension)
This skill originally targets Claude Code + houseCARL MCP. On any AI:
- Load
tool-discoveryand confirmhousecarl-mcpis FOUND and MCP tools are actually listed in the session. - If the binary exists but MCP tools are absent → tell the user to register MCP for this app and fully restart.
- If neither binary nor MCP → recommend:
INSTALL houseCARL:
1. Get the houseCARL distribution (houseCARL-Setup.exe + housecarl\ folder).
2. Install .NET 9 Runtime AND ASP.NET Core Runtime 9:
https://dotnet.microsoft.com/download/dotnet/9.0
winget install Microsoft.DotNet.Runtime.9
winget install Microsoft.DotNet.AspNetCore.9
3. Run houseCARL-Setup.exe (quit AI apps first when updating).
4. Fully restart the AI application.
5. Set MO2 instance (folder containing ModOrganizer.ini).
6. Verify with a load-order question.
- FormIDs for houseCARL tools:
XXXXXX:Plugin.esp(six hex + defining master filename). - SkyPatcher / SPID / KID FormID dialects differ — use their authoring skills.
- Always load
tool-output-awarenessbefore patch writes from conflict winners. - Prefer runtime INI frameworks when the user wants no-ESP distribution.
- Codex users: a
codex\housecarlstub may exist in the product zip; MCP is still required. - Grok users: add an MCP server block pointing at
housecarl-mcp.exein.grok\config.toml, then restart.
Fallback without houseCARL
- Forge inspection jobs if available
- Spooky
esp info/ analyze on owned plugins only - Manual xEdit findings reported by the user (agent does not launch GUI)
- Never invent load-order winners
V5 automatic setup (MO2 + Vortex)
houseCARL always needs an MO2-shaped instance directory (folder containing ModOrganizer.ini).
| User's manager | Action |
|---|---|
| Mod Organizer 2 | Point at the real instance folder |
| Vortex | Build a shim that looks like MO2 (junction mods → Vortex staging, copy/symlink plugins.txt) |
Agent must run or recommend
# From the V5 pack:
powershell -NoProfile -ExecutionPolicy Bypass -File "<PACK>\TOOLS\Setup-HouseCarl.ps1"
Also shipped beside this skill when installed from the pack:
housecarl\scripts\Setup-HouseCarl.ps1
Behavior of Setup-HouseCarl.ps1
- Finds
housecarl-mcp.exe(env,%LOCALAPPDATA%\houseCARL, Claude/Codex skill trees, optional tool vaults). - Checks .NET 9 + ASP.NET Core 9 runtimes.
- Auto selects MO2 if
ModOrganizer.iniinstances exist; else Vortex if staging is found. - MO2: sets instance path.
- Vortex: creates
%LOCALAPPDATA%\houseCARL-Shimperreferences/houseCARL-Vortex-shim-setup.pdf(also in packTOOLS\housecarl\). - Sets user env:
HOUSECARL_MCP,SKYRIM_MO2_INSTANCE,HouseCarl__Mo2InstanceDir. - Wires Grok MCP block when present; writes Codex hint; writes
%LOCALAPPDATA%\houseCARL-data\uabs-setup-state.json. - User must fully restart the AI app.
Refresh (Vortex)
After load-order or mod changes in Vortex (copy mode):
.\Setup-HouseCarl.ps1 -RefreshOnly
When MCP tools are missing mid-session
- Run setup script (or recommend it).
- Confirm state file exists.
- Tell user to restart AI.
- Do not invent load-order winners while MCP is down.
Vortex caveats (do not hide these)
plugins.txtorder is authoritative.- Generated
modlist.txtloose-file priority is approximate (mtime). - Patches land as
houseCARL - <name>under staging — user must import into Vortex and Deploy. - Parallel real MO2 is better if loose-file conflict authoring must be exact.
Claude Code
Still prefer official houseCARL-Setup.exe for the plugin. Set plugin MO2 instance folder to the path printed by Setup-HouseCarl.ps1 (real MO2 or shim).
UABS AIO installer (pack)
New users and missing-tool recovery:
# Pack root
.\INSTALL-AIO.ps1
.\INSTALL-AIO.ps1 -Mode OnlineLatest
.\TOOLS\Ensure-Tools.ps1
.\TOOLS\Update-From-GitHub.ps1
Offline snapshots live in BUNDLED-TOOLS\offline\. Component registry: BUNDLED-TOOLS\CATALOG.json.
After MCP changes the user must fully restart the AI application.