agentleFS
WingedGuardianWingedGuardian/skyrimvr-claude-toolkit/.claude/skills/inspect-esp/SKILL.md

inspect-esp

Skill22 starsChanged 3 days agoMITView on GitHub

Inspect an ESP/ESM plugin file and show a summary of all records

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the generated YAML files to understand the record structure

    line 20
  2. Very specific:

    If node -e "require('xeditlib')" exits clean from the toolkit root, run:

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- GENERATED by scripts/gen_agent_trees.py from agent/skills/inspect-esp/SKILL.md. Toolkit contributors: edit the source. Your own notes belong in KNOWLEDGEBASE.local.md, which updates never replace. -->

Inspect ESP Plugin

Inspect the plugin the user named ($ARGUMENTS in Claude Code) and provide a comprehensive summary.

Workflow

Option A: Spriggit (preferred — human-readable output)

  1. Serialize the ESP to YAML:
    bash tools/spriggit-cli.sh serialize --InputPath "Data/<Plugin.esp>" --OutputPath "<scratch dir>" --GameRelease SkyrimSE --PackageName Spriggit.Yaml --PackageVersion "<the version spriggit --version prints>"
  2. Read the generated YAML files to understand the record structure
  3. Summarize: record types, counts, editor IDs, masters, notable records

Option B: xeditlib (programmatic — for deeper analysis)

If node -e "require('xeditlib')" exits clean from the toolkit root, run:

node examples/inspect-esp.js "<Plugin.esp>"

Or write a targeted inspection script if the example doesn't cover what's needed.

Output Format

Provide a structured summary:

  • File info: name, masters, record count, flags (ESM/ESL)
  • Record type breakdown: count per signature (SPEL, MGEF, WEAP, etc.)
  • Notable records: list editor IDs with brief descriptions
  • Scripts: any VMAD-attached scripts and their properties
  • Potential issues: casting type mismatches, missing ONAM, ESL FormID range violations

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.