Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/xedit-automation
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.
Passed 13 of 18 test cases with the skill, and 5 of 18 without it.
and 12 more in the full report
10 fixed6 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
My call to create a new record failed with a mutation consent error. What parameter must I pass when starting the xEdit daemon to enable mutating operations?
| Checked | Without skill | With skill |
|---|---|---|
| Passes iKnowWhatImDoing: true in the xedit_start tool call. | Missed | Passed |
| Verifies that consentEnabled equals true via xedit_session. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
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.
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.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.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).
| Task shape | Path |
|---|---|
| High-frequency known intent (audit a conflict, read a record, run a job, write a patch) | MCP intent tool |
| Novel / debugging / free composition of native commands | MCP atomic passthrough: xedit_call(command, args) — still in harness |
| Exploratory atomic-op storm (trial-and-error, repeated read-eval, hypothesis testing) | Delegate to a read-only investigator sub-agent with this skill loaded; the sub-agent burns its own context, returns a distilled summary |
| Large formalisable bulk mutation | MCP xedit_run_script (Batch 4+) with dry-run + snapshot |
| Daemon explicitly in default (non-MCP) mode, manual debug only | Direct xedit-client.ps1 is acceptable — but ONLY when the user has explicitly accepted the risk and the daemon is not in -automation-mcp-mode |
The agent should never have a reason to bypass the MCP. Atomic passthrough exists for that.
test cases passed, vs 5 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.