agentleFS
AlomoesDataScienceAlomoesDataScience/claude-skills/.claude/skills/mod-docs/SKILL.md

mod-docs

Skill1 starsChanged 10 days agoNo licenceView on GitHub

Generic rules for keeping MODDED games separate from the base game (vanilla) in any game: find out first which mods and versions a game runs, give each mod its own folder (a skill named game-mod, e.g. dom6-scbm) for its database, change tables and playthrough notes, keep vanilla skills vanilla (one pointer line at most), tag every number with its source, check the mod's own files before quoting a vanilla manual, wiki or database number, record changes as diffs against vanilla, and handle mod versions and mod stacks. The user's rule (2026-11-03) after I quoted vanilla Destruction (E3) for his SCBM game, where it is E2. Use when playing or discussing any game that may run mods (balance mods, overhauls, total conversions, Workshop mods), before quoting a stat for it, when saving notes from a modded game, when a mod updates, and when writing or reviewing a game skill.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

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.