agentleFS
AlomoesDataScienceAlomoesDataScience/claude-skills/.claude/skills/army-log/SKILL.md

army-log

Skill1 starsChanged 12 days agoNo licenceView on GitHub

Evaluate and log BOTH armies every turn of any wargame or battle (the user, 2026-11-02) - read every unit off the screen (cards, hovers, banners; never game data), write one CSV per side per turn (who, type, quality, armour, points, men, cohesion, action points, ammo, square, facing, role, task, commanders), store them in one battle log (armylog.py), then evaluate - losses, cohesion states, ammo, rout progress against the game's victory rules and units still to break, combat power (points x men left) by type and by sector for force ratios at the decisive point, unread units flagged - and diff turns (moves, losses, cohesion changes). Feeds war-language's UP step (Troops and Enemy) and the turn report to the user. Use when a battle turn starts (after the photo), after the enemy's turn, when reporting a battle, and after a battle for the lessons log.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    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 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.

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.