Skip to content
Back to skills

Skyrim Frameworks Index

ASecurity

Conceptual framework selector for Skyrim runtime patching. Routes to one authoritative syntax owner per framework

  • 5 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 3, 2026
ai-agentsgodocumentation

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 3, 2026

npx -y skills add ShugokiFable/Ultimate-AI-Starter-Bundle --skill skyrim-frameworks-index --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Skyrim Frameworks Index?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Skyrim Frameworks Index
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/shugokifable-skyrim-frameworks-index/badge)](https://www.skillsdirectory.com/skills/shugokifable-skyrim-frameworks-index)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: skyrim-frameworks-index
description: Conceptual framework selector for Skyrim runtime patching. Routes to one authoritative syntax owner per framework
  and prevents conflicting dialects.
compatibility: Windows 10/11; Skyrim Special Edition or Anniversary Edition; exact installed framework version must be verified
metadata:
  version: 4.3.0
  updated: '2026-07-22'
  library: overseer-skyrim-agent-skills
  error_registry_revision: 4.3.0
---

# Skyrim frameworks index

This is a conceptual router. It does not own executable syntax.

## Authority order

1. Exact installed framework version, bundled documentation, parser DLL/source, and bundled working examples.
2. Authoritative upstream source or documentation matching that installed version.
3. The source-locked dedicated framework skill in this library.
4. Known-working local configuration files, read-only and version-identified.
5. This index.
6. Historical prompt libraries, integration plans, old guides, and remembered syntax.

A dedicated skill never outranks the actual parser. When evidence proves a skill wrong, fix the skill and its validator rather than rewriting working mods to match stale prose.

## Routing

| Goal | Primary mechanism | Syntax owner |
|---|---|---|
| Add keywords to records | KID | `kid-authoring` |
| Distribute forms to NPCs | SPID | `spid-authoring` |
| Patch supported record fields at runtime | SkyPatcher | `skyrim-skypatcher` |
| Swap base objects/references or supported properties | BOS | `skyrim-base-object-swapper` |
| Generate/audit large distributions | deterministic generator | `skyrim-distribution-pipeline` + `skyrim-distr-kid-validation` |
| CDF JSON container/vendor rules | Container Distribution Framework | `skyrim-container-distribution` |
| Interpret framework/SKSE logs | source-aware log forensics | `skyrim-runtime-log-forensics` |
| New settings menu | MCM Helper | `skyrim-papyrus-modding` |
| Legacy SkyUI MCM maintenance | SKI_ConfigBase | `skyrim-papyrus-modding` |
| Simple JSON/form persistence | PapyrusUtil | `skyrim-papyrus-modding/references/papyrusutil.md` |
| Nested/dynamic structured data | JContainers | `skyrim-papyrus-modding/references/jcontainers.md` |
| Unsupported operation | ESPFE, Papyrus, patcher, or DLL | `skyrim-plugin-authoring`, `skyrim-papyrus-modding`, or `skyrim-skse-commonlib` |

## Locked current decisions

- **SPID 7.3.x:** supported keys do not include `Weapon`; inventory objects use `Item` or generic `Form`. Level range endpoints must both exist. TraitFilters split on `/`, `D/-D` are valid, and Chance may end in `!`.
- **KID 4.0.6:** use human-readable type labels. Trailing optional fields may be omitted.
- **BOS 3.4.1:** use pipe-delimited entries under current sections including `[Forms]`, `[References]`, `[Transforms]`, and `[Properties]`.
- **SkyPatcher 6.4.2:** category placement is mandatory and operation names are category/version-specific.
- **MCM:** MCM Helper is the normal new-menu route; SKI_ConfigBase remains a legacy maintenance route.

The historical integration plan's comma-based SPID-trait decision is superseded by the current parser source. Historical documents are evidence leads, not executable syntax authorities.


## Cross-framework punctuation warning

A token valid in one framework is not portable:

- FLM `*FormList` expands a FormList;
- CDF `add: ["*Claw"]` is not a wildcard query in the pinned parser;
- SPID `/` may mean a level range in LevelFilters or trait combination in
  TraitFilters;
- BOS commas inside transform functions are not SPID filter separators.

Route first, then parse by the selected framework and exact field.

Files in this skill

  • SKILL.md3.6 KB
  • references/FRAMEWORK-SOURCE-LOCK.json4.2 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.