Steam Companion

Reusable Steam gaming companion for profiles, library insights, recommendations, wishlist tracking, achievement context, game lookups, reviews, setup verification, and preference memory.

Use this skill for Steam-related requests about profiles, library/backlog summaries, play recommendations, wishlist sales, achievement progress, game lookups, review help, setup verification, and durable preference memory.

Setup

• STEAM_API_KEY is required for Steam Web API access and is the only secret here.
• STEAM_ID is required to identify the target profile, but it is not a secret.
• IGDB_CLIENT_ID and IGDB_ACCESS_TOKEN are optional for richer game lookups.
• A vanity name is fine as input; the Core should resolve it to steamId64 before calling Steam APIs.
• The skill should not read secrets directly.
• Library summaries need public or accessible library data.
• Wishlist sales need a public wishlist or a store snapshot from the Core.
• Achievement summaries need accessible game details.
• Empty payloads usually mean privacy settings or unavailable data, not a skill failure.

Core Rules

• Let the Core resolve secrets and fetch Steam data first.
• Pass profile-shaped data through syncSteamSnapshot.
• Pass fresh library, wishlist, achievement, or lookup data into the matching context builder.
• Preserve genres, tags, Steam Deck compatibility, review scores, and privacy flags when they exist.
• Treat private or missing data as a real signal, not a gap to fill with guesses.
• Prefer source data first, then profile memory if the source is partial.
• Avoid recommending owned or disliked games unless explicitly asked.
• Keep achievement responses spoiler-aware.
• Surface Deck compatibility, review quality, and tags when available.

Main Areas

• Profile memory
• Library overviews
• Discovery and recommendations
• Wishlist sales and priorities
• Achievement context
• Game lookup summaries
• Setup verification
• Review drafting

Input Shapes

• buildLibraryOverviewContext(userId, games, topLimit?, recentLimit?): provide a game list with playtimeMinutes or playtimeHours, and optionally playtime2WeeksMinutes, deckCompatibility, reviewScore, and tags or genres.
• buildDiscoveryContext(userId, candidates?, options?): provide candidate games plus optional mood, timeAvailable, and recommendation filters.
• buildWishlistContext(userId, saleItems?, wishlist?, limit?): provide sale items from the store and/or tracked wishlist items.
• buildAchievementContext(userId, game, progress): provide the game plus achievement totals, recent unlocks, locked items, and privacy state.
• buildGameLookupContext(userId, game, options?): provide factual metadata from a lookup result, including summary, release info, price, platforms, tags, genres, review score, and Steam Deck support when available.
• buildSetupContext(userId, check): provide boolean checks for API key, Steam ID, library access, wishlist access, achievement access, and IGDB availability.

Typical Flow

1. Fetch Steam or store data in the Core.
2. Sync profile-shaped data with syncSteamSnapshot.
3. Save explicit feedback with saveFeedback or savePreference.
4. Use recommendGames or buildDiscoveryContext for ranked suggestions.
5. Use buildLibraryOverviewContext, buildWishlistContext, buildAchievementContext, buildGameLookupContext, or buildSetupContext for focused summaries.
6. Use buildReviewContext when writing about a specific game.

Example Prompts

• "Show my backlog and the games I keep ignoring."
• "What should I play on Steam Deck tonight?"
• "Check whether any wishlist games are on sale."
• "Build achievement context for Hades II."
• "Look up Celeste and summarize the useful metadata."
• "Verify my Steam setup and tell me what is missing."
• "Build review context for Hades."

Publishing Notes

• Keep the skill root self-contained.
• Keep the frontmatter quoted and accurate.
• Keep agents/openai.yaml in sync with the skill name, short description, and default prompt.
• Keep manifest.ts aligned with the skill description and version.
• Bump constants.ts before publishing a new release.
• Do not add behavior in docs that the service layer does not actually support.
• Keep SKILL.md as the only file users need to understand the skill.