Clarifying options for summary
I'm considering how to approach what the user wants. It seems I should ask only when necessary. I could offer a few options like 1) 500字赛报, 2) 亮点评述, 3) 数据板块, 4) 社媒推文, and 5) 标题优化. Then, if they choose, I can deliver the content. Since this is all in Chinese, replying in that language feels right. I’ll ask a clarifying question and offer to draft a standard赛报 of about 600-800字.Preparing match report options
I think it’s a good idea to create a short, generic match report as a sample. I’ll also ask the user for team names to tailor it more specifically if they want that. It's important to keep the formatting light and simple—bullets work fine! I’ll prepare two options and include a brief sample body. This way, I can smoothly assist the user based on their preferences. Let's proceed with that!
这是个很“体坛风”标题。你是想让我据此写一篇赛报/点评吗？需要确认两点：
先给你一个通用版赛报示例（不指名球队，按你标题的信息展开），你看风格是否OK：
欧冠小组/淘汰赛焦点战，英超豪门与意甲豪门鏖战90分钟，最终英方0-1惜败。身价达“7亿”的英方“战舰”开场求稳，以控球与高位逼抢主导节奏，但两次意外受伤改变了比赛走向：上半场中段与下半场初段，英方两名关键主力先后因伤离场，被动调整打乱了原有压迫与出球节奏。意方则以紧凑5-3-2/4-4-2形态伺机反击，长短结合寻找肋部与身后空间。
比赛第88分钟，意方在左路完成层层推进，二过一撕开边肋，倒三角回做后低射入网，完成绝杀。终场数据上，英方在控球、射门次数占优，但高质量机会有限；意方的预判与协防落点精准，门将数次关键扑救保住零封。此役的拐点在于英方的两处被动换人——中后场衔接下降，转换速度减缓，高位逼抢的回收与反防站位出现迟滞，为对手最后时刻的致命一击埋下伏笔。
看点与争议：
如果你给出具体球队与细节（受伤球员、进球者），我可以：
选个编号或直接给我球队信息，我马上完善。
