yilmaz-games

Use this skill whenever the user wants to work with Steam Web APIs — getting API keys, fetching player counts, app details, reviews, news, sales/revenue data, wishlist metrics, achievements, leaderboards, regional pricing, or building custom applications on top of Steam data. Also use this skill when the user is debugging Steam API issues (empty responses, 403 errors, wrong data), choosing between key types, or figuring out which Steam API host to use. Triggers include "Steam API", "Steamworks", "Steam Web API", "Steam sales data", "Steam wishlist", "Steam player count", "Steam reviews", "Steam pricing", "partner.steam-api.com", "IPartnerFinancialsService", "Steam API key", "publisher key", "financial key", "appdetails", "GetDetailedSales", "Steam current players", "Steam achievements API", "Steam leaderboard API", "Steam microtransactions". Use this even when the user doesn't say "API" explicitly but clearly needs Steam data programmatically — e.g., "how do I get my game's sales numbers in code" or "I want t