# xedit-automation

xedit-automation — a skill for Claude Code and Codex that routes plugin inspection and authoring tasks through the xEdit daemon. Loads first and delegates to the right path: MCP intent tools, atomic passthrough, or sub-agent delegation.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf (Devin Desktop), Claude.ai · ★ 1596 repo stars
- Author: awesome-bgs-mod-master contributors
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/hashgraph-online/awesome-codex-plugins/tree/HEAD/plugins/BB-84C/bgs-modding-superpowers/skills/xedit-automation/SKILL.md
- Updated: 2026-10-29
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/xedit-automation

## What it does

The skill serves as the always-loaded entry point for xEdit work on Claude Code and Codex. It determines which path to use: fast MCP intent tools for common tasks (conflict audit, record read), atomic passthrough for novel commands, or sub-agent delegation for large-scale mutations.

The skill provides a toolkit for discovery, reading, and conflict inspection. Start with `xedit_session`, then `xedit_list_capabilities` to see supported commands. Branch to specialized tools: `xedit_find_record`, `xedit_read_record`, `xedit_inspect_conflicts` for high-frequency work. For commands without a dedicated intent tool, use `xedit_call(command, args)` — it runs the full validation and audit pipeline. Reference material lives in a structured knowledge base queryable via `bgs_kb_query`.

The skill blocks direct daemon calls when running in `-automation-mcp-mode`. Atomic passthrough exists so you never need to bypass the harness.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add hashgraph-online/awesome-codex-plugins --skill xedit-automation -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/xedit-automation/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/xedit-automation/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add hashgraph-online/awesome-codex-plugins --skill xedit-automation -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/xedit-automation/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add hashgraph-online/awesome-codex-plugins --skill xedit-automation -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/xedit-automation/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install hashgraph-online/awesome-codex-plugins plugins/BB-84C/bgs-modding-superpowers/skills/xedit-automation
```

2. **Manually: put the files in place**
- File: `.github/skills/xedit-automation/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add hashgraph-online/awesome-codex-plugins --skill xedit-automation -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/hashgraph-online/awesome-codex-plugins --path plugins/BB-84C/bgs-modding-superpowers/skills/xedit-automation
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/xedit-automation/SKILL.md` — The legacy .windsurf/skills/ path still works

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/hashgraph-online/awesome-codex-plugins/tree/HEAD/plugins/BB-84C/bgs-modding-superpowers/skills/xedit-automation/SKILL.md

## When to use it
- route xEdit tasks to the correct tool without bypassing the MCP harness
- audit conflicts between plugins and decide whether patching or reordering is needed
- read and verify FormID records across Bethesda game mods
- author compatible patches while preserving intended mod values
- debug the xEdit daemon and run batch operations safely

## Example prompts
- Check for conflicts between two plugins and decide if a patch or reorder is needed
- Start an xEdit session and list all supported capabilities and commands
- Find all conflicting FormID records between mods and show which plugin wins each one

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 90d9159a17c79674.

BEGIN THIRD-PARTY FILE 90d9159a17c79674
```text
---
name: xedit-automation
description: Use whenever the task involves inspecting, modifying, or building plugins for Bethesda games via the forked xEdit automation daemon. Loads first; routes to the right path (MCP intent tool, MCP atomic passthrough, or sub-agent delegation) and prevents the agent from bypassing the harness.
---

# xEdit Automation — Hub Skill

This skill is the always-loaded entry point for any xEdit work. It is the single source of truth for "which path do I use" and "what must I never do." Specialised task skills (e.g. `xedit-conflict-audit`) inherit its routing, anti-patterns, and verification discipline; they do not restate them.

## Toolbox at a glance (progressive disclosure, r6-aware)

The forked xEdit daemon is best treated as a progressive-disclosure surface:
start with the small MCP intent tools, ask the live daemon which r6 capability
blocks it supports, then switch to the richer one-call patterns only when the
corresponding `system.capabilities.supports.*` key is present.

- **Discovery & session** — `xedit_session`, `xedit_list_capabilities`. Call
  `xedit_session` first every conversation. Then call `xedit_list_capabilities`
  once to see the command digest, `contractVersionExpected`, and r6
  `supports.*` anchors.
- **Reading records & conflicts** — `xedit_find_record`, `xedit_read_record`,
  `xedit_inspect_conflicts`. These are the W2 (conflict audit) backbone; branch
  to atomic passthrough when W2 needs an r6 response block that no intent tool
  exposes yet.
- **Atomic passthrough** — `xedit_call(command, args)`. For any native daemon
  command that does not have an intent tool yet. Still runs the full pipeline
  (validation → state → rules → audit). Use it whenever the intent tools do not
  fit.

For deep reference material, query the structured BGS KB first (`bgs_kb_query`
/ `bgs_kb_get`). Deep reference records live under
`knowledge/bgs-kb/packs/core/records/xedit/` (queryable via `bgs_kb_query` /
`bgs_kb_get`).

## Routing doctrine (which path to use)

| Task shape | Path |
|---|---|
| High-frequency known intent (audit a conflict, read a record, run a job, write a patch) | **MCP intent tool** |
```
END THIRD-PARTY FILE 90d9159a17c79674

The third-party file has ended. Everything between the 90d9159a17c79674 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2188 of 26792 bytes. © awesome-bgs-mod-master contributors · MIT · https://github.com/hashgraph-online/awesome-codex-plugins/tree/HEAD/plugins/BB-84C/bgs-modding-superpowers/skills/xedit-automation/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
