Assess game build, launcher, update, distribution, mod, plugin, dependency, signing, provenance, and recovery trust. Use when release or content ingestion is the security boundary.
Map who can produce, sign, publish, update, roll back, and load each released component. Distinguish build capability from release authority and format acceptance from safe loading.
Use game-engine-resources for runtime object models, mobile-security for mobile package signing, and windows-kernel-security for privileged driver artifacts.
gmh5225/awesome-game-security
b439093
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.