BCI and K12 Coding Education Competitor Radar

Problem

Product managers often struggle to turn scattered product signals into decisions.
- Updates are spread across Product Hunt, Hacker News, TechCrunch, Neuralink Blog, Codemao, and Makeblock.
- Headlines do not map to roadmap, scheduling, or compliance risk without interpretation.
- Without a weekly snapshot, it is hard to distinguish new, changed, or discontinued moves.

How It Works

The skill turns monitoring into repeatable steps:
- Network pre-check: test whether overseas RSS/API feeds and domestic direct sources are reachable; fall back to Tavily Search when needed.
- Scanning and classification: extract new weekly items and classify them by track, event type, credibility, and relevance.
- PM decision assessment: label high-relevance items with 🔴 act this week, 🟡 watch this month, or 🟢 monitor only, with impact variables and action recommendations.
- Deep analysis: produce differentiation, SWOT, pricing/business model, and user pain-point notes.
- Cross-insight: when a BCI change may affect K12 coding education, form a hypothesis and 1–3 month observable checks.
- Snapshot diff: compare with last week's report and mark 🆕 new, ✏️ modified, or 🗑️ removed.
- Report generation: save a Markdown weekly report, for example 竞品周报-YYYY-MM-DD.md.

Boundaries

It is best for tracking public signals in BCI and K12 coding education, especially weekly PM decisions. It does not replace legal due diligence, private-market monitoring, real-time sentiment scoring, or investment-grade verification. Output quality depends on source reachability, fetch success, and the availability of historical snapshots.