Claude Skills by ShugokiFable

Create, repair, compile, and validate Skyrim Papyrus scripts, quests, aliases, magic effects, MCM Helper integration,

Author or patch Skyrim ESP, ESL, and ESM files, masters, records, and VMAD using typed tooling and structural

Build or repair a shareable Skyrim follower from a RaceMenu or CharGen preset, including plugin records, FaceGen,

Interpret Skyrim SKSE, framework, asset, animation, and runtime logs without blaming the wrong field, DLL, mod,

Route Skyrim runtime patching to dedicated SPID, KID, SkyPatcher, BOS, FLM, CDF, and OAR authorities. This skill

Migrate a fictional adult-only Skyrim mod from SexLab APIs and events to the exact installed OStim ecosystem

Mandatory final validation gate for a Skyrim mod release tree or archive. Use after implementation and FOMOD

Create, port, diagnose, or optimize native SKSE DLL plugins using CommonLibSSE or CommonLibSSE-NG, CMake, vcpkg,

Route and validate SkyPatcher category placement and installed-version operations without inventing keys.

First router for any Skyrim SE/AE modding task. Classifies the job and loads only the specialist skills needed,

Mandatory workspace ownership and version-snapshot workflow for Skyrim mod creation or editing. Use before the

Create or repair Skyrim dialogue and voice assets, including DIAL/INFO records, quest/topic conditions, voice-type

Use when the same fact appears in multiple files, configs, generated reports, caches, docs, or external systems.

Use when writing, fixing, interpreting, or auditing SPID _DISTR.ini runtime distribution rules for NPC spells, perks, items, keywords, outfits, factions, or packages.

Drive Spooky's AutoMod Toolkit CLI for Skyrim ESP, Papyrus, MCM, NIF, BSA/BA2, audio, and SKSE project workflows. Resolve toolkit root portably; recommend install when missing. Use with module skills skyrim-nif and skyrim-audio.

Use when resuming interrupted, long-running, multi-session, compacted, or partially completed work.

Use when downloading, vendoring, executing, updating, or redistributing third-party binaries, scripts, packages, actions, plugins, models, or archives.

Use when a test passes but may be checking the wrong signal, mocks its own assumption, snapshots unstable output, or cannot distinguish correct behavior from a broken implementation.

Use when an agent is about to wait on something slow (CI, a build, a download, a deploy), when a session is burning tokens on polling or re-reading, when choosing how many MCP servers or skills to load, or when the user asks about cost, caching, or context bloat. Corrects the common belief that prompt caching makes watching things cheap.

Resolve optional Skyrim and AI tooling on the current machine without assuming drive letters or usernames. Use at session start, when a tool path is unknown, or before recommending install.

Use when a Skyrim patch/conflict analysis may touch generated output from tools such as Reqtificator, ParallaxGen, DynDOLOD, Synthesis, TexGen, xLODGen, or NPC Plugin Chooser.

Use when an operation changes multiple files, registrations, database rows, configs, versions, or external resources that must not be left half-updated.

Unity game mods via BepInEx, Harmony, MonoMod, IL2CPP or Mono - RimWorld, Valheim, Subnautica, Lethal Company, Risk of Rain 2, Stardew Valley, Oxygen Not Included, Kerbal Space Program, and generic Unity targets.

Unreal Engine 4/5 mods via UE4SS, Lua and C++ hooks, generated SDKs, reflection, and packaged pak/utoc content - Palworld, Satisfactory, XCOM 2, and generic Unreal targets.

Use when needing jailbreak or NSFW prompt packs for any AI.

Use when a release, installer, schema, configuration, or tool must work for both new users and users upgrading from an older version.

Use when optimizing, refactoring, simplifying, automating, or making trade-offs could accidentally remove or weaken something the user explicitly asked for.

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Use when bumping versions, publishing packages, rebuilding binaries, changing protocol compatibility, or updating release metadata.

Use when creating, changing, debugging, or claiming completion of anything whose correctness includes how it LOOKS - a website, web or desktop UI, game, HUD, menu, rendered 3D scene, Blender/Unity/Godot output, generated image, icon, chart, responsive layout, gallery or preview. Also use on "make this UI better", "finish this app", "make it polished", "this button does nothing", "the preview is gray/blank", "fix the images", "it looks wrong/broken/ugly", or before saying a visual change is done.

Build, test, and release-gate native Win64 C/C++ executables - compiler selection with or without the Windows SDK, strict warning gates, and reproducible release binaries.

Windows workspace plumbing - directory junctions, paths containing "!" and spaces, git overlay repositories, push recovery, and byte-exact edits that survive PowerShell quoting.

Use when building a third-person fictional adult character sheet from a portrait, tags, and an I WANT block, or when merging captions into Description / Personality / Scenario / First Message fields.

Use when captioning or tagging a fictional adult image for a character sheet, LoRA, outfit, or OStim work, or when a vague "sexy woman" caption is about to invent nudity that is not in the pixels.

Use when finalizing a complex answer, implementation, diagnosis, migration, or release where an initially plausible result could hide a costly mistake.

Map of Skyrim + AI coding tools (Forge, houseCARL, Spooky, codebase-memory, Headroom, Superpowers, Ponytail, CodeBurn). Load to choose tools, wire MCP, or recommend installs when missing.

Use when a requirement, error, API, name, or observed behavior has multiple plausible interpretations that would lead to different actions.

Use when changing commands, schemas, APIs, protocols, config formats, plugin interfaces, or behavior consumed by other components.

Use when producing a ZIP, installer, executable, wheel, package, release asset, or other built deliverable.

Use when building, publishing, comparing, debugging, or accepting binaries, archives, generated files, installers, models, or release assets.

Use when a plan relies on guessed paths, versions, APIs, user state, defaults, environment behavior, or undocumented facts.

Use when a workflow asks the user to copy, edit, approve, restart, configure, repair, or verify steps that software may be able to perform.

Fallout 4 and Starfield mods - plugins, Papyrus, F4SE/SFSE and CommonLib, assets, and packaging. For Skyrim use the skyrim-* skills; this covers the other Creation Engine titles.

Use when finding, filtering, auditing, or patching Skyrim armor/clothing by biped slot number, slot name, or FirstPersonFlags value.

Use when a Skyrim task must turn many load-order records into one catalogue, audit, graph, report, or batch patch.

Regression-test a single-file C game whose *_test.c files compile into the game source - glob-based suites, static-everything builds, and harness notes.

Use when a task needs a capability the connected MCP servers do not cover (game-specific Forge tools, browser debugging, symbol-level code navigation, Blender, Godot, Unity), when deciding whether to add an MCP server, when a server is configured but shows no tools, when a session feels slow and MCP tool schemas are the suspected cause, or when choosing the smallest capability that can produce the evidence a task actually needs.

Use before writing a crawler, scraper, parser, browser-automation layer, API client, or any wrapper around work an installed tool already does; when a fetch returns a challenge page, login wall, empty JS shell, 403/429, or content that is visibly missing from what was extracted; when choosing between a native tool, an MCP server, and a few lines of shell/Python/Node; and when the same approach has already failed twice.

Post-change verification workflow. Use after implementation to independently inspect diffs, run the real build