Conflict Auditor

Classify file, archive, and plugin-data conflicts between Bethesda Game Studios mods.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When working with multiple Bethesda Game Studios mods, overlapping files, records, or load-order entries often cause broken gameplay, missing content, or crashes that are hard to diagnose manually. This skill automates the classification of these conflicts and identifies the correct resolution path, saving modders hours of trial and error.

Core Features & Use Cases

  • Conflict Classification: Automatically categorizes overlaps as file, archive, or plugin-data conflicts.
  • xEdit Integration: Uses the native xEdit outer client for read-only conflict inspection, no custom extraction logic required.
  • Resolution Guidance: Determines if a load order adjustment or custom patch is needed, and tracks unresolved hotspots for future xEdit work. Use case: If two texture mods overwrite the same landscape mesh files, this skill quickly identifies if the conflict is a simple loose file precedence issue or requires a merged patch to preserve changes from both mods.

Quick Start

Use the conflict auditor skill to classify the overlapping mods between my texture overhaul and my weather mod and tell me the required resolution path.

Frequently Asked Questions about Conflict Auditor

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

FAQPage Schema
How do I classify Bethesda mod conflicts between overlapping plugins?

To classify Bethesda mod conflicts, you can separate overlaps into file, archive, or plugin-data categories. This process identifies whether loose file precedence or a merged patch is required to resolve broken gameplay or crashes.

How does xEdit inspect plugin conflicts for modpack curation?

xEdit inspects plugin conflicts using a native outer client for read-only inspection. It analyzes overlapping mods to generate conflict classifications and resolution paths without requiring custom extraction logic.

When do I need a custom patch for load order conflicts?

You need a custom patch for load order conflicts when simple precedence fails to preserve changes from overlapping mods. The audit determines if a load order adjustment or a merged patch is needed to restore missing content.

Can I audit texture overhaul and weather mod overlaps automatically?

Yes, you can audit texture overhaul and weather mod overlaps automatically. It categorizes whether the conflict stems from loose file precedence or archive issues and tracks unresolved hotspots for future xEdit work.

What is the best way to find unresolved conflict hotspots in a modpack?

The best way to find unresolved conflict hotspots in a modpack is to run an automated audit that tracks overlapping records. It generates a follow-up list of unresolved entries for future xEdit patching.