Considering match report approach
I think we shouldn't fetch live information unless the user specifically asks. The user only wrote the headline, so they might want an expanded discussion. I should confirm their intent and ask what they’re looking for—like the match details or style. It’s important to avoid making up facts since it’s for a future match in 2025. Maybe I can offer to draft a template article and ask if they want official stats or a link.Offering content options

I should provide the user with clear choices for creating a report. For example:
I also need to clarify the teams involved, as there are synonyms to consider. I’ll offer to draft a report or suggest variations for titles and short summaries. It’s essential to avoid fabricating details.Creating a match report template
Some users may specifically request, "write a match report." I think it’s a good idea to create a general template while asking for any missing details they might need. I’ll also prepare five title variations and a structured outline for them to choose from, providing clear options like:
No need to run any complex commands here; I can deliver this efficiently!
这是个很好的赛报标题草案!为避免张冠李戴,我先确认两点:
你希望我怎么帮:
先给你可直接替换信息的赛报模板,方便你马上用:
标题备选
导语
赛况回放
技术统计(可替换)
赛后点评
社媒快发文案(即发版)
需要我现在就去核对具体比分与细节并成稿吗?如果可以,请确认对阵双方(“狮子”的具体球队)并允许我查询,我会在同一条回复里给出完整赛报和数据卡。