Considering user request

The instructions indicate I should avoid fabricating facts. A cautious method would be to ask clarifying questions about the date, scoreline, or key stats. However, the user might be looking for a general template instead. I could present two options: either I craft a polished report if they provide specific information or offer a generic template for them to fill in with data.

Additionally, I can include a neutral recap without stats, focusing on the game's general outline.Clarifying user needs

The instructions indicate that I should only ask when necessary, but in this case, it's essential to avoid any inaccuracies. I should pose 1-2 questions while also providing a template for the user to fill in. Keeping the response concise is important, so I'll create an outline that includes optional prewritten paragraphs with placeholders for data.

I can ask about the game date, final score, key statistics, and describe critical moments. Instead of naming specific players, I could use "core players" to be cautious. I'll refrain from suggesting scraping data since it's not part of the request. I'll also produce different title variations and templates for a general recap, a quick news summary, and social media posts while keeping everything useful.Drafting advanced metrics response

I can also offer an option where the user pastes a box score, and I’ll automatically generate a response with advanced metrics. It's important to stick with ASCII formatting.

To start, I need to confirm some details: the game date, final score, key player statistics, important moments, and any current standings or ranking changes.

Then, I can provide a report template that includes sections like an introduction, game flow, key moments, data comparisons, post-game insights, impacts, and technical stats while using placeholder markers like {Clippers Total Score} and {Thunder Total Score}. A super-compact version could also be made. Let’s move forward!