SkillAgentSearch skills...

using-bgs-modding-superpowers

Use when starting ANY conversation involving Bethesda Game Studio modding, MO2, xEdit, or modpack curation. Bootstrap that loads the toolkit overview, lists available task skills, and enforces the hard rules of this plugin.

Install / Use

npx skills add hashgraph-online/awesome-codex-plugins --skill using-bgs-modding-superpowers

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

89/100

Category

Marketing

Supported Platforms

Claude Code
OpenAI Codex

Tags

Our assessment of using-bgs-modding-superpowers

using-bgs-modding-superpowers scores 89/100 on our quality scale, 287th of 642 Marketing skills we index (top 45%).

Its SKILL.md is 17 KB long, well organised into 10 sections with 1 code example: a thorough specification that gives an agent plenty to work with.

With 1,075 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
17/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so using-bgs-modding-superpowers is actively maintained.
  • Our last check on 2026-10-31 found the source still online.
  • It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

using-bgs-modding-superpowers compared with similar skills

All 4 of these similar skills score higher than using-bgs-modding-superpowers; compare them before choosing.

SkillScoreStarsUpdatedFormat
using-bgs-modding-superpowers (this skill)by hashgraph-online891.1k53d agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install using-bgs-modding-superpowers?
Run npx skills add hashgraph-online/awesome-codex-plugins --skill using-bgs-modding-superpowers. The install tabs above show the steps for each supported agent.
Which AI agents does using-bgs-modding-superpowers work with?
It is written for Claude Code and OpenAI Codex, as a SKILL.md file. Other agents that read the same format can often use it too.
Is using-bgs-modding-superpowers safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is using-bgs-modding-superpowers still maintained?
The repository was last updated about 2 months ago, so using-bgs-modding-superpowers is actively maintained.

name: using-bgs-modding-superpowers description: "Use when starting ANY conversation involving Bethesda Game Studio modding, MO2, xEdit, or modpack curation. Bootstrap that loads the toolkit overview, lists available task skills, and enforces the hard rules of this plugin. Auto-injected by the OpenCode plugin's chat.messages.transform hook and by the hooks/ session-start chain in Claude Code and Codex."

<EXTREMELY_IMPORTANT_BGS_MODDING_SUPERPOWERS> This is the bgs-modding-superpowers per-session bootstrap. If you are reading this, the plugin injected it into the first user message of this session. Do NOT discard it. Do NOT respond to the user yet without first checking whether one of the task skills below applies. </EXTREMELY_IMPORTANT_BGS_MODDING_SUPERPOWERS>

Using BGS Modding Superpowers

You are operating with the bgs-modding-superpowers plugin loaded. This plugin gives you an agent-driven toolkit for Bethesda Game Studio modpack curation: MO2 control plane, xEdit MCP, conflict-audit workflow, and runtime asset skills for dev-log and release-changelog maintenance.

Available skills (auto-trigger on these intents)

| Skill | Auto-triggers when | |---|---| | setting-up-bgs-modding-environment | First conversation in a project; MO2 or xEdit not yet detected; user says "set up", "install", "bootstrap", "configure" | | maintaining-modding-environments | After first-run: "ongoing", "maintain", "register custom pack", "prune cache", "update knowledge base", "modding environment health check" | | evaluating-bgs-mods | Deciding whether a mod belongs in the pack; "should I add this mod", "is this mod good", "评估这个mod", "这个mod值得装吗", "this mod looks too good to be true" | | interpreting-mod-author-instructions | After INCLUDE verdict, before download/install; "how do I install", "FOMOD choices", "which file to download", "author说明", "which variant", "按作者说明安装" | | curating-bgs-modpack | Whole-pack incremental build strategy; "plan the pack", "batch strategy", "rollback point", "naming convention", "declare 风格", "策展整合包", "整合包规划" | | diagnosing-bgs-problems | It broke — symptom-first triage; "CTD", "crash log", "FPS drop", "stuttering", "Buffout", "freeze", "won't start", "崩溃", "掉帧", "卡顿" | | testing-bgs-modpack | Proactive post-install verification of a batch; "test the pack", "verification", "post-install check", "is it stable", "what should I test", "测试整合包", "验证安装" | | xedit-automation | Any task involving .esp/.esm/.esl plugin files, FormIDs, masters, conflicts, ESL flagging, ITM/UDR cleaning, Pascal scripts | | xedit-conflict-audit | "Why is this override not winning?", "Which plugins overlap on this record?", "Is this load order safe?" | | writing-bgs-load-order | Reading/editing/generating plugins.txt or loadorder.txt; enabling/disabling/reordering/adding/removing plugins; launching xEdit with a custom plugins file; "load order", "enable this plugin", "disable that plugin", "what does the asterisk mean" | | using-bgs-translator | Translate a Bethesda plugin's text to another language; "translate this mod", "汉化这个 mod", "localize mod to chinese", "build SST for", "use my LLM to translate plugins" | | using-bgs-archive | unpack/pack BA2/BSA archives; inspect archive format/contents; extract assets | | using-bgs-papyrus | compile/decompile Papyrus PSC<->PEX for Skyrim/FO4/Starfield | | writing-modpack-devlog | "Log this", "record what I did", "note this change", "add to dev-log", "track this decision" | | writing-modpack-changelog | "Cut a release", "release notes", "what changed since v1.2", "prepare release for Nexus" |

When the user's intent matches one of these, invoke the corresponding skill through your skill tool BEFORE replying. Do not paraphrase the skill from memory; let the skill load.

Available MCP tools

The bundled xedit MCP server (declared in .mcp.json for Claude Code / Codex, declared via the OpenCode plugin's config.mcp.xedit hook) is fully non-blocking: every tool returns immediately. The xEdit daemon's lifecycle is tracked in the server's in-memory state machine, and domain tools fast-fail with code: "not_ready" if you call them before the daemon is ready.

Lifecycle / health tools

| Tool | Use | |---|---| | xedit_status | Pure read. Returns { status: "not_started" \| "starting" \| "ready" \| "failed", ... }. Never modifies state. Use this to POLL while waiting for a launch. | | xedit_start | Kicks off an asynchronous daemon launch if not already starting/ready. Returns immediately. Accepts optional overrides: { launcherPath?, gameMode?, dataPath?, pluginsFile?, moProfile? }. Use dataPath (MO2 gamePath + "\\Data") to override xEdit's registry-discovered platform path; use pluginsFile to point at a custom load order (see writing-bgs-load-order). The launch itself takes 60-240s; that work happens in the background. | | xedit_health | When ready: sends system.ping through the named pipe to catch zombies. After a flush exit timeout, rechecks the retained managed PID so a delayed normal exit can clear lifecycle state without force. | | xedit_dirty | Returns xEdit dirty state plus authoritative contract-0.23 pending-rename readback when available, with a local fail-closed fallback for older daemons. Pending saves remain visible even when daemon dirty state is false. | | xedit_flush | Contract-0.23 durability boundary. Requires consent, drains pending renames, validates the response, waits for the managed daemon's promised self-exit, and reports complete, partial, or unknown outcome. Failed in-band renames get one final exit-time retry; fresh-daemon readback decides durability. | | xedit_stop | Stops the daemon and clears MCP runtime state. It refuses unsaved edits or pending-shutdown saves unless force: true is explicitly chosen; forced abandonment is reported and audited. | | xedit_restart | Stops the daemon with the same dirty/pending-save safety, then kicks off a fresh async launch. Use only when no pending save is tracked; force: true is explicit abandonment, not a flush. |

Domain tools (6) — require ready, fast-fail otherwise

| Tool | Use | |---|---| | xedit_session | If ready: returns the full session envelope (gameMode, loadOrderSize, daemonPid). If not_started: auto-initiates the launch. Otherwise: returns the current status. Always non-blocking. | | xedit_list_capabilities | Curated 50-command contract-0.23 digest + live drift report. | | xedit_find_record | Locate by {file, formId} or {editorId}. | | xedit_read_record | Fields + base record + winning override. | | xedit_inspect_conflicts | W2 verdict tool: no_conflict / itpo / itm / minor / breaking. | | xedit_call(command, args) | Atomic passthrough for native daemon commands; in-harness. Lifecycle-owned session.flush is refused here and must use xedit_flush. |

Canonical lifecycle pattern (do this every session that touches xEdit)

1. xedit_start({})                  -> { status: "starting" }      (or "ready")
2. xedit_status({})                 -> poll until status="ready"   (sleep 5-15s between calls)
3. xedit_health({})                 -> confirm responsive=true
4. xedit_session({}) / xedit_*      -> normal domain work
5. xedit_dirty({})                  -> check dirty state and pendingShutdownSave
6. xedit_flush({})                  -> when pending > 0, drain + confirm daemon self-exit
7. xedit_start({ ... })             -> fresh daemon for persistence readback after flush
8. xedit_stop({}) / restart({ ... }) -> only when no dirty or pending state exists

NEVER call a domain tool in a tight loop expecting it to "wait." If xedit_status reports status: "failed", surface data.error to the user and stop — common causes are MO2 not running visibly, the Python plugin not loaded, the xEdit binary missing, or xEdit's automation-serve tripping on the active load order.

The structured daemon-command and workflow reference now lives in KB records. Use bgs_kb_query / bgs_kb_get for deep reference retrieval; the old skills/xedit-automation/xedit-knowledgebase.md path is a redirect only.

BGS knowledge-base tools (3) — curated knowledge, no xEdit daemon

The sibling BGS knowledge-base MCP is for curated modding knowledge, not live runtime state. It works before MO2 / xEdit are configured; use xEdit MCP for actual plugin, load-order, and record readback.

| Tool | Use | |---|---| | bgs_kb_status | Reports loaded KB packs, versions, games, domains, cache root, and user pack roots. | | bgs_kb_query | Searches loaded packs for ranked knowledge snippets with game/domain filters and sources. | | bgs_kb_get | Fetches a full record by id, merging game-specific variants when game is provided. |

Hard rules (non-negotiable)

  1. The user's <MO2_Root> and any <MO2_Root>/<game>/Data/ (or equivalent "Stock Game" tree) is real game state. Never write into it directly. Any game-local change is expressed as an MO2 mod overlay under <MO2_Root>/mods/<mod-name>/. The MO2 VFS projects it at runtime.
  2. All xEdit work goes through the bundled xedit MCP. Never spawn xEdit.exe directly from the shell, never parse .esp/.esm/.esl files with your own Python/JS, never invoke xedit-client.ps1 from raw shell. The MCP exists so the harness can enforce validation, state, rules, and audit on every call. Atomic passthrough (xedit_call) is the documented escape hatch when an intent tool does not fit — it is still in-harness.
  3. Mutating operations require explicit user consent and a daemon launched with -IKnowWhatImDoing. Read the xedit-automation skill BEFORE any destructive work. The anti-pattern list there is binding.
  4. A session.save response is not durability. A nonzero savedFilesPendingShutdown / savePendingShutdownCount is deferred. On contract 0.23, xedit_dirty reconciles that fallback with the daemon's authoritative pending queue and xedit_flush is the only supported in-band drain. It validates the response and confirms daemon self-exit before clearing the blocking guard. A partial or unknown outcome remains visible as lastFlush; after relaunch it is labelled previousSessionFlush with the old PID and timestamp. Failed in-band renames receive one normal exit-time retry, so fresh-daemon readback, not the partial envelope alone, decides durability. force:true on stop/restart is still explicit abandonment, never durability proof.
  5. Large scope (many records, broad conflict survey) → delegate to a read-only investigator subagent FIRST. The subagent burns its own context and returns a distilled summary. Do not loop hundreds of records through your own context.
  6. BGS domain knowledge routes through the KB first. For questions about how BGS modding works — Papyrus semantics, plugin-format gotchas, archive precedence, load-order conventions, common engine quirks, or game-specific toolchain gotchas — call bgs_kb_status / bgs_kb_query before improvising or reaching for web search. If the question is about what the current local load order, plugin, or record actually is, use xedit_* or the relevant file/CLI surface instead. The KB is advisory; xEdit readback remains authoritative for actual state. If bgs_kb_status reports no packs or the needed game pack is missing, fall back to web research using the roadmap Appendix source list or route setup/maintenance work to install the pack.
  7. First-run state: if MO2 / xEdit / the control-plane Python plugin are not yet set up on this machine, invoke setting-up-bgs-modding-environment BEFORE any modpack work. That skill orchestrates detection and install.
  8. Nexus credentials and Premium download paths: MO2 stores the user's Nexus API key globally in Windows Credential Manager under target ModOrganizer2_APIKEY (legacy) / `ModOrganizer2_NEXUS_OAUTH_TOKENS

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars1.1k
CategoryMarketing
Updated1mo ago
Forks294

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions
using-bgs-modding-superpowers — Claude Code Skill: Install & Safety Check | SkillAgent