Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/curating-bgs-modpack
Use when planning or building the whole Bethesda modpack incrementally — batch strategy, rollback point, naming convention, separator discipline, attribution, and declaring 风格 before adding mods. Triggers - "build a modpack", "plan the pack", "batch strategy", "rollback point", "naming convention", "declare 风格", "策展整合包", "整合包规划". NOT for deciding whether one mod belongs (evaluating-bgs-mods), installing one mod from author instructions (interpreting-mod-author-instructions), load order mechanics
Passed 16 of 20 test cases with the skill, and 10 of 20 without it.
and 7 more in the full report
7 fixed11 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
I have established my pack's dark fantasy vision and functional lanes. Now I need to evaluate whether a candidate mod called 'Grim Lighting Overhaul' fits into the visual lane. Should I evaluate this candidate mod using whole-pack curation rules or hand it off?
| Checked | Without skill | With skill |
|---|---|---|
| Directs individual candidate mod evaluation to evaluating-bgs-mods. | Missed | Passed |
The instructions your model reads when the skill loads.
A BGS modpack is not a shopping cart of impressive files. It is a declared world-style, built in recoverable increments, with enough naming, attribution, and rollback discipline that future-you can still explain what every layer is doing. Stability is the floor. 风格 is the soul. The curator is co-authoring a systemic world, not proving they can install more mods than a Vault-Tec procurement clerk can misfile requisitions.
+------------------------------------------------------------------------------------------------+
| Declare the pack's 风格 first, then add mods in named, reversible batches; if you cannot say |
| what role a batch plays or how to roll it back, you are stockpiling files, not curating a pack. |
+------------------------------------------------------------------------------------------------+
Use this skill when the question is how to build or reshape the whole pack: declared style, batch sizing, rollback boundaries, separators, naming convention, attribution, and devlog discipline.
Do not use this skill as the primary skill for adjacent intents:
| User intent | Primary skill |
|---|---|
| "Should this mod be included?" / judge quality, risk, and pack fit | evaluating-bgs-mods |
| "How do I install this mod correctly?" / read author instructions / choose files or FOMOD options | interpreting-mod-author-instructions |
| Record a pack decision, batch boundary, or lesson learned | writing-modpack-devlog |
Enable/disable/sort plugins.txt or loadorder.txt | writing-bgs-load-order |
| Inspect actual conflicts, winning overrides, or whether reorder-vs-patch is safe | xedit-conflict-audit |
Terminal handoff: after this skill defines the style and next batch boundary, hand each candidate mod to evaluating-bgs-mods. After a batch decision is made, hand the decision to writing-modpack-devlog. Inclusion says "belongs in the next plan"; it does not mean "install loose files however you feel like it."
Use when:
test cases passed, vs 10 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.