war-language
Skill1 starsChanged 11 days agoNo licenceView on GitHub
A higher-order language for warfare in games - translate what is going on in a game (units, squares, points, morale bars, turns) UP into military terms (situation in METT-TC and OAKOC, enemy in SALUTE with most-likely and most-dangerous courses of action, our plan as mission, intent, form of maneuver and one task-and-purpose per unit, control measures), reason at that level, then translate it back DOWN into concrete game orders (which unit, which square, which action, how many points, what to check after) - with a per-game lexicon (game element <-> doctrine term) in each game's guide, written templates (warlang.py prints them) and back-translation checks so nothing is lost either way. Built on military-doctrine, military-operations, soviet-doctrine, war-concepts, combat-models. Use when a turn or phase of a wargame or strategy game starts, when explaining to the user what is happening in a battle or war, when turning a plan into orders, when reviewing a turn, and when making a lexicon for a new game.
In this repository48 other files it gives its agents.
- army-logSkill
- battle-tacticsSkill
- borrow-from-gamesSkill
- check-skillsSkill
- combat-modelsSkill
- delegateSkill
- dice-mathSkill
- discord-logsSkill
- draw-mapSkill
- draw-movesSkill
- game-databaseSkill
- game-setupSkill
- game-sourcesSkill
- game-uiSkill
- generalize-learningSkill
- hand-backSkill
- idle-viewSkill
- install-windows-gamesSkill
- learn-from-tutorialsSkill
- learn-to-modSkill
- learn-to-playSkill
- loading-screensSkill
- manual-firstSkill
- map-cameraSkill
- map-measureSkill
- map-usageSkill
- military-doctrineSkill
- military-operationsSkill
- mod-diffSkill
- mod-docsSkill
- move-phasesSkill
- obs-recordSkill
- photo-mapSkill
- planningSkill
- rules-skillsSkill
- save-scumSkill
- scoutingSkill
- screeningSkill
- skills-managerSkill
- skill-syncSkill
- soviet-doctrineSkill
- stream-panelSkill
- unit-combat-mathSkill
- video-watchSkill
- waiting-checklistSkill
- war-conceptsSkill
- wiki-scoutSkill
- write-skillSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
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
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.