Structuring match analysis

I can create a template preview for a match. I’ll ask for details like match date and whether the user is interested in a betting angle. I’ll provide a framework that includes head-to-head stats, current form, tactical approaches, and injuries—although I should confirm the sources. If the network allows, I can check current injuries. I need to avoid making unverifiable claims and focus on patterns for the teams unless I receive more specific details from the user.Generating a match preview

I could create a match preview article in Chinese, focusing on storylines like Betis' form, Girona's injuries, and tactical insights, while also including low-risk betting suggestions. However, I need to clarify if that's what the user wants by asking, "要不要写一篇前瞻稿？给我比赛时间或偏好角度?" Since the user didn't specifically ask a question, I’ll offer options such as a short preview, in-depth analysis, betting advice, or social media headlines. I’ll include a mini-preview but note that I can’t verify injuries without more details.Creating a match preview in Chinese

I think I should produce a concise match preview in Chinese with sections like 形势解读, 关键对位, 战术脉络, 伤停与轮换, and 风险点. I want to keep it neutral and include disclaimers like, "数据与名单需以赛前官宣为准." I won’t need to run any tools for this. The title will be "西甲前瞻：贝蒂斯 vs 赫罗纳," and I'll use bullet points for clarity while keeping the language general enough to avoid specific betting advice. Overall, I’ll ensure to phrase it carefully to avoid any misinformation.Clarifying user needs

I should start by asking the user exactly what they need. I can provide a quick preview and then inquire if they want something deeper. For fetching the latest injuries, I’d need user approval, but I could also ask them for a lineup or fetch it myself. Since the conversation didn’t specify settings, I’ll stick with a default approach. My final answer will be concise bullet points in Chinese for the preview, while asking if they want a deeper analysis and the match time.