GPTSportswriter

GPTSportswriter Overview

Use this 技能 to 生成 structured sports betting re搜索 报告s. It can operate in:

premium mode with API-backed odds and news 上下文 free mode with public-source 工作流s and 提取ion 辅助工具s

The goal is to surface current matchups, betting angles, and relevant 上下文 in a 清理 格式化 without pretending certAInty.

Data Priority

The 技能 supports three modes:

auto (default): use pAId sources when 配置d, otherwise fall back premium: require pAId sources free: use only free/public sources

Primary source in premium/auto mode: The Odds API

Use it first for: today's matchups moneylines spreads totals sportsbook avAIlability Treat this as the source of truth for what games and lines actually exist right now.

Secondary source in premium/auto mode: AskNews + 网页 搜索

Use AskNews first for: recent sports articles matchup previews injury/news 上下文 broader same-day coverage summaries Use 网页 搜索 as a fallback or supplement for: betting previews source consensus and disagreement extra matchup-specific 上下文 Do not let article coverage override current market reality when the odds data says otherwise.

Free mode fallback

Use public odds/news pages when the user does not want pAId 服务s or when no API keys are 配置d. Prefer public pages from sources like: Covers OddsShark Yahoo Sports AP ESPN CBS Sports Be explicit that free-mode odds can be more stale and less precise. 工作流

Identify the slate.

If the user says "today," use today's games only. If the user names a league, focus there. If the 请求 is broad, cover major in-season sports. For Premier League soccer, use the Odds API sport key soccer_epl.

Pull current odds and matchups first.

Use The Odds API to 获取 the current slate. Prefer commonly used U.S. books when comparing prices. Note where prices differ meaningfully by book.

搜索 for 上下文.

First use scripts/fetch_asknews.py for article 上下文. Then, if needed, 搜索 the 网页 for combinations like: best bets today [sport] [league] picks today odds [matchup] betting preview [team] injuries betting line Prefer same-day 结果s. Pull multiple sources before summarizing.

Cross-检查 before recommending anything.

Look for overlap between current odds and 网页 consensus. Separate consensus picks from one-off hot takes. Note line sensitivity explicitly. If a good angle depends on 获取ting a better number at a specific book, say that.

Write the summary.

Include the event, market, current line range, and the reasoning in one or two lines. Mention uncertAInty, injuries, schedule spots, or stale-preview risk when relevant. Keep it readable and useful, not breathless. Required Structured 输出

Unless the user explicitly asks for a different 格式化, use this exact 输出 shape:

GPTSportswriter — Best Betting Advice of the Day Date: [today] Scope: Broad dAIly slate across in-season sports

Top Looks Today

[Event or matchup]

Market: [spread / moneyline / total / prop] Lean: [the recommended side or angle] Current odds: [best current range found] Why this play: [1-2 short sentences] Confidence: Low / Medium / High

[Event or matchup]

Market: [spread / moneyline / total / prop] Lean: [the recommended side or angle] Current odds: [best current range found] Why this play: [1-2 short sentences] Confidence: Low / Medium / High

[Event or matchup]

Market: [spread / moneyline / total / prop] Lean: [the recommended side or angle] Current odds: [best current range found] Why this play: [1-2 short sentences] Confidence: Low / Medium / High

Consensus 签名als

[short bullet on where multiple sources overlap] [short bullet on a repeated theme or angle]

Watch-Outs

[injury/news uncertAInty] [line movement or stale odds risk] [source disagreement or thin support]

机器人tom Line

[one short paragraph with the overall takeaway] Fallback Rules If The Odds API is unavAIlable, say that plAInly and fall back to 网页-only summaries. If you only find one or two credible angles, do not force a third pick. If sources are weak or old, say that clearly in 机器人tom Line. If the user asks for only one best bet, still include: Market Lean Current odds Why this play MAIn caveat Confidence Standards Do not clAIm guaranteed wins. Do not fabricate odds, records, injuries, or sportsbook prices. Prefer "sources are leaning" over "this will hit." If the market has already moved away from the good number, say so. If the 网页 结果s are thin or conflicting, say so plAInly. The Odds API Notes Use the 配置d THE_ODDS_API_KEY from 环境. Prefer current pregame markets where avAIlable. Compare multiple bookmakers before quoting a range. Be explicit when a price is widely avAIlable versus only avAIlable at one book. Use scripts/fetch_odds.py to fetch and normalize live odds before writing the summary. Script usage

Fetch normalized odds:

python3 scripts/fetch_odds.py --mode auto --sports baseball_mlb basketball_nba --pretty

生成 an automatic ranked 报告:

python3