Daily Game Opportunity Radar: Automate Your Indie Game Discovery

Where this fits

You run a small studio or a content pipeline that needs fresh indie game leads every morning. Instead of manually crawling Steam, itch.io, Poki, and community radars, you want a repeatable, auditable process that produces a clean, deduplicated list of games released in the last 24 hours — with proof of every step.

Why agents benefit

• Checklist enforcement: The skill runs 10 explicit checks (C01–C10) and writes evidence to .rankup/, guaranteeing every platform is covered and every result is traceable.
• Deterministic dedup: New games are merged from discovery and radar sources, then deduplicated by name or URL — so your agent never hands you the same game twice across feeds.
• Failure isolation: Each platform gets a compared, baseline, or failed status. If a sitemap fails, the agent knows exactly which check to fix and can re-run without losing context.
• Time-bound freshness: All outputs are tagged to the current day, preventing stale or accidental inclusion of older titles.
• Output contract: The skill only considers the task complete when the latest checklist JSON has ok: true — a machine-readable success gate for downstream automation.

Practical scenarios

Pre-production research for a game curation newsletter

Every morning, your agent runs this skill, picks up the merged new-games list, and drafts brief reviews for the top 10 entries. Because the checklist filters out social campaigns and non-game records, the newsletter stays on-topic.

Competitive tracking for a publisher

You want to see every new release on Steam, itch, and Poki within 24 hours. The skill's per-platform added/changed/removed breakdown lets your agent flag unusual spikes (e.g., sudden delistings) and report them to your business team.

Automated backlog for a game jam curator

After the skill collects daily opportunities, a secondary agent scores them by genre, price, and platform. The evidence files in .rankup/ let you audit why a title was included or excluded — useful for quality review.

Add it to your agent workflow

Install the skill directly into your agent's environment and invoke the checklist command from your project root:

npx skills add yan-labs/yan-skills --skill game-opportunity-collect
node game-opportunity/scripts/game-opportunity.mjs collect-checklist

The command writes artifacts under .rankup/demand/game-review/. Check latest-collect-checklist.json for the ok status and per-check evidence. If any check fails, read the SKILL.md guidance and re-run the same command — no manual cleanup needed.

Compare before adopting

Before committing to this skill, compare it with alternatives on four axes: quality signals (does the checklist prove data provenance?), maintenance freshness (are sitemap parsers updated when platforms change?), alternatives (e.g., RSS aggregators or custom scripts), and workflow fit (does the output format plug into your existing pipeline?). This skill shines when you need auditability over speed.

Why it is worth tracking

With 130 stars and an active yan-labs repository, this skill demonstrates steady community interest in reproducible, evidence-based game discovery. Its explicit checklist design makes it easy to evaluate for adoption — and because it barely changes your existing automation, you can trial it for a week and discard it if the signal isn't valuable. Check the OpenAgentSkill listing for version history and community feedback before deciding.