xedit-automation

Route xEdit operations on Bethesda plugin files through mandatory safety harnesses.

11|3|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/BB-84C/bgs-modding-superpowers --skill xedit-automation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: xedit-automation
Source: https://github.com/BB-84C/bgs-modding-superpowers/tree/main/plugins/bgs-modding-superpowers/skills/xedit-automation
Command: npx skills add https://github.com/BB-84C/bgs-modding-superpowers --skill xedit-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Agents working on Bethesda game mod plugins frequently take incorrect or unsafe paths when using xEdit, such as bypassing safety harnesses, making irreversible edits to source mods, or applying poorly formed compatibility patches that introduce mod breakage. This skill eliminates those risks by serving as the always-loaded entry point that routes every xEdit task to the correct, safe workflow.

Core Features & Use Cases

  • Mandatory Task Routing: Automatically directs all xEdit work to the appropriate path: MCP intent tools for common high-frequency tasks, atomic passthrough for rare native daemon commands, or read-only sub-agent delegation for exploratory trial-and-error work.
  • Built-in Safety Guardrails: Enforces non-negotiable rules including never bypassing the MCP harness, requiring explicit consent for all mutating operations, mandating dry-run previews and post-save readback for edits, and blocking deletion of referenced records without impact assessment.
  • Patch Authoring Discipline: Includes a structured judgment framework to ensure compatibility patches are reversible, intentional, and free of unnecessary copied data, reducing long-term conflict debt for modpacks.
  • Use Case: When an agent needs to audit conflicts between multiple Skyrim mod plugins, this skill routes it to the correct xEdit conflict inspection tools, ensures it does not edit source mods directly, and guides it to create a separate, reversible compatibility patch if needed.

Quick Start

Load this skill first whenever you need to work with Bethesda game plugin files via xEdit, and it will automatically route your task to the correct safe workflow without requiring manual path selection.

Frequently Asked Questions about xedit-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely automate xEdit patch authoring for Skyrim mods without breaking source plugins?

Safe xEdit patch authoring requires mandatory task routing and safety harnesses that enforce explicit consent for mutations and block direct edits to source mods. This approach mandates dry-run previews and post-save readback to ensure reversible compatibility patches and prevent irreversible mod damage.

What's the best way to audit plugin conflicts across Bethesda game files using xEdit automation?

Auditing plugin conflicts safely involves routing xEdit tasks to read-only sub-agent delegation for exploratory work, ensuring no direct mutations occur. This conflict inspection mechanism prevents accidental data loss by separating trial-and-error analysis from actual patch creation.

Does xEdit automation support ESL flagging and load order management for Fallout 4 and Starfield?

Yes, xEdit automation supports ESL flagging and load order tasks for Fallout 4, Starfield, Skyrim, and Fallout 76. The safety harness routes these operations through validated workflows that enforce reversible patch authoring discipline to avoid long-term conflict debt in modpacks.

Can I use automated xEdit workflows to clean plugins without risking deleted record references?

Automated xEdit plugin cleaning is safe when governed by guardrails that block the deletion of referenced records without a full impact assessment. The safety harness requires explicit mutation consent and dry-run validation to prevent breaking dependent mod plugins.

Why do my automated xEdit compatibility patches introduce new conflicts in my modpack?

Compatibility patches introduce conflicts when they contain unnecessary copied data or bypass structured patch authoring discipline. Using a judgment framework ensures patches are intentional, reversible, and free of excess data, which reduces long-term conflict debt for modpacks.

When do I need explicit consent for mutating operations during xEdit plugin automation?

Explicit consent for mutating operations is always required during xEdit plugin automation to prevent irreversible damage. The safety harness enforces this non-negotiable rule across all patch authoring, plugin cleaning, and ESL flagging tasks to ensure no unauthorized modifications occur.