Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/xedit-conflict-audit
Use when auditing conflicts in a Bethesda plugin set — determining for a record (or a plugin's records) which override wins, what the conflict label is, what references it, and whether the configuration is safe or breaking.
Passed 13 of 17 test cases with the skill, and 5 of 17 without it.
and 11 more in the full report
12 fixed5 passed either way3 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
A weapon record is overridden by 'Overhaul.esp', which intentionally changes its speed to match the overhaul's combat balance. The earlier plugin's change is not needed in this pack. What remedy decision should be made?
| Checked | Without skill | With skill |
|---|---|---|
| Designates ACCEPT as the decision when the later override is the intended rule. | Missed | Passed |
The instructions your model reads when the skill loads.
Inherits the hub xedit-automation skill. Do not restate routing or anti-patterns here; this skill is the W2 workflow only.
For a record or a plugin in scope, produce a verdict: no_conflict | itpo | itm | minor | breaking, plus the winning override, the override chain, and a list of plugins that reference the record. Output is a concise summary, not the raw daemon round-trips.
Use these MCP intent tools (do not drop to xedit_call unless an intent tool does not fit):
xedit_session (always first; once per conversation).xedit_list_capabilities (once per conversation; sanity-check drift).xedit_find_record (locate the record(s) you want to audit).xedit_inspect_conflicts (the verdict tool).xedit_read_record (when you need to see the actual conflicting field values).xedit_call for r6-only daemon fields that no intent wrapper exposes yet:
records.references, records.conflict_status, and records.apply_filter.If the conflict is broad (many records across many plugins), do not loop through them one by one in the orchestrator — delegate to a read-only investigator sub-agent (see Hub skill, "Sub-agent delegation recipes").
This is the judgment gate after the tool surface tells you what wins. xEdit shows the override chain; it does not decide whether the right answer is accept, reorder, clean, remove, or patch. BB84's rule is situational thought over ritual: most overlap is normal, sorting is a single-choice lever, and exhaustive FormID stitching is not realistic at pack scale.
Use this section only to choose the remedy. If the verdict becomes PATCH, stop here and hand off; this W2 skill audits conflicts and names intent, it does not author patch records.
digraph patch_vs_reorder {
rankdir=TB;
node [shape=box];
start [shape=doublecircle, label="Focused conflict readback\n(record fields + winning override)"];
test cases passed, vs 5 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.