Steam Games Updates

Fetch recent game updates from Steam News. Use when the user asks about game patches, updates, or news for their tracked Steam games, or wants to add/remove...

Security Scan

The skill's code, instructions, and requirements are consistent with a Steam news fetcher: it only needs python3, talks to Steam endpoints, and stores its own config and data files in the skill directory.

Purpose & Capability

Name/description match the implementation. Required binary (python3) is appropriate and there are no unrelated credentials, binaries, or platform services requested.

Instruction Scope

SKILL.md instructs running the included Python script. The script only reads/writes local files inside the skill baseDir (skill-config.json, data/updates.json, data/.state.json) and performs HTTP requests to Steam endpoints; it does not read other system files or environment variables.

Install Mechanism

There is no install spec (instruction-only) and the shipped Python script is the only code. Nothing is downloaded or executed from arbitrary URLs during install.

Credentials

The skill requires no environment variables or credentials. Network access to Steam APIs is expected for the described functionality.

Persistence & Privilege

The skill does not request always:true and does not modify other skills or system-wide settings. It persists only its own config and data files within its base directory.

Assessment

This skill appears to do only what it says: it queries Steam's public endpoints and stores results under the skill folder (skill-config.json and data/). Before installing, review and be comfortable with the script being able to make outbound HTTP requests to Steam and create files in the skill directory. If you share an environment with sensitive files, confirm the skill is installed in a location that won't overwrite anything important. No credentials are required and there are no obvious exfiltration endpoints, so risk is low.

Fetch and accumulate game news from the Steam News API for a configurable list of games.

First run

On first run, skill-config.json is created with Counter-Strike 2 and PUBG: BATTLEGROUNDS as defaults. Tell the user which games are configured and ask if they want to add or remove any.

Usage

Fetch updates for all tracked games:

python3 {baseDir}/scripts/updates.py

List currently tracked games:

python3 {baseDir}/scripts/updates.py --list

Adding a game

When the user asks to add a game (even with an imprecise name), search Steam to resolve it:

python3 {baseDir}/scripts/updates.py --search "game name"

This returns a JSON array of matches with appid and name. Show the user the top results and ask them to confirm which one. Then add it:

python3 {baseDir}/scripts/updates.py --add <appid>

The canonical game name is fetched automatically from Steam when adding.

Removing a game

python3 {baseDir}/scripts/updates.py --remove <appid>

Changing settings

All settings live in {baseDir}/skill-config.json:

{
  "games": [
    {"name": "Counter-Strike 2", "appid": 730},
    {"name": "PUBG: BATTLEGROUNDS", "appid": 578080}
  ],
  "lookback_days": 3,
  "exclude_patterns": {
    "578080": ["Weekly Ban"]
  }
}

Key	What it does	How to change
games	List of tracked games with Steam appids.	Use --add / --remove commands, or edit directly.
lookback_days	Max days to look back for updates.	Set to any positive integer.
exclude_patterns	Per-game title regex filters (keyed by appid).	Add regex strings to skip unwanted posts (e.g. ban waves).

Data files

All data lives in data/ (gitignored):

• updates.json — accumulated update records
• .state.json — last-run timestamp

Notes

• No API key required. Uses the public Steam Web API (ISteamNews) and Steam Community search.
• Each update record contains: game, appid, title, url, date, content, discovered_at, status.
• Re-running merges new updates without duplicates.