loading-screens
Skill1 starsChanged 11 days agoNo licenceView on GitHub
Tell whether a game's screen is a loading screen and wait through loads properly, in any game on Claude's virtual screen - the user's method (2026-11-03) - shoot the screen BEFORE starting a load, act, grab frames as fast as possible (~33 ms) until the screen changes (else the action DID NOT TAKE), then decide with ONE GENERAL test whether what came up is a loading screen (blank, fade, spinner/progress-bar-only motion, loading words) - no per-game learning - and poll it out every second. bgplay.py act / isloading / waitload. Use whenever Claude clicks or presses something that loads (Play game, End Turn, battle replays, menus, map screens), when a script waits for a game, when a wait timed out or ended early, or to check "is it still loading?".
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
- 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
- war-languageSkill
- wiki-scoutSkill
- write-skillSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
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.