The Language of Simplicity

Structure the request with markdown headings and a numbered list of the specific outputs you want, which is the format this platform reads most cleanly. Convert every figure of speech into the literal thing underneath it before you type it - "hit the ground running" becomes a named action with a deadline. If you repeatedly ask for the same kind of output, the format instruction belongs in Custom Instructions rather than in each prompt.

• Number the outputs you want; one line each.
• Translate every idiom into the literal action underneath.
• Delete politeness, keep context - they are not the same.
• Name the artefact, not the vibe: "net profit figure", not "key numbers".
• Put recurring format rules in Custom Instructions.

## TASK

Analyse the Q3 sales report pasted below.

## OUTPUT - these four things, in this order, nothing else

1. **Net profit.** The final net profit figure, quoted exactly as it appears in the report, with the line item or page it came from.
2. **Top three products by sales.** A bulleted list, each with its sales figure. If the report ranks by revenue and by units and the two rankings differ, give me both and say which you used.
3. **The report's overall conclusion**, in one sentence.
4. **What is missing.** If any of the first three is not in the document, say "not stated in the report" and move on. Do not estimate, do not compute a figure the report does not give, and do not fill a gap from general knowledge about the industry.

## RULES

- Figures exactly as written, including the currency and the units - lakh, crore, million. Do not convert between them.
- No commentary, no recommendations, no "here are some observations". I will ask if I want them.
- If two places in the report give different numbers for the same thing, quote both and flag the discrepancy. That is the most useful thing you can find.

## REPORT TEXT

[Paste report text here]

Write a motivational email to the sales team for the start of Q4.

**Goal:** that each person ends Q4 above target.

**Key message:** acknowledge the work they put into Q3, then state plainly that Q4 carries the year.

**Call to action:** each team member books a 15-minute goal-setting meeting with their manager this week.

**Tone:** professional, energetic, encouraging. Direct rather than effusive.

**Length:** under 200 words, plus a subject line.

## THE INSTRUCTION THAT MATTERS MOST

No sports idioms and no business clichés. Specifically banned: hit the ground running, knock it out of the park, give it 110%, move the needle, take it to the next level, all hands on deck, circle back, let's crush it.

This is not a style preference. These phrases are what I would have written and they are precisely the reason the email would land flat - everyone on that team has read a hundred of them and reads past them automatically. Replace each one with the literal thing it was standing in for: "hit the ground running" means start on day one rather than week three; "give it 110%" means something I cannot actually ask for and should not pretend to. If you find yourself reaching for a phrase like that, say the plain thing instead.

## THEN

1. **Cliché check.** Quote any phrase in your draft that is doing the job of a cliché even if it is not on my list.
2. **One line on the hardest sentence.** "Q4 is the most important quarter" is a line that can read as pressure rather than motivation. Tell me how yours reads, and give me one alternative phrasing if you think it tips the wrong way.

Use [TEAM NAME] and [MANAGER] as placeholders. Do not invent Q3 numbers - if a specific achievement would strengthen the email, mark where I should insert it.

Write a Python script that scrapes news headlines.

## SPECIFICS

- **Libraries:** `requests` and `BeautifulSoup` (bs4). No Selenium, no Scrapy.
- **Target:** send an HTTP GET request to `https://timesofindia.indiatimes.com/`.
- **Extract:** the text of every `<h2>` element that contains a headline.
- **Output:** print each headline on its own line.

## REQUIRED BEYOND THE BARE SCRIPT

1. A `User-Agent` header. A bare `requests` call is frequently refused.
2. A timeout on the request, and a check of the status code before parsing.
3. Handle the realistic failures: connection error, non-200 response, and the case where no `<h2>` elements are found. The last one is the most likely and the easiest to mistake for the site being down.
4. Strip whitespace and skip empty strings - `<h2>` tags on news sites are frequently empty or contain only an icon.

## THE PART I ACTUALLY NEED YOU TO BE HONEST ABOUT

You do not know the current HTML structure of that site, and `<h2>` may not be where its headlines live. So:

- Write the script so the tag and class are set in one named variable at the top, not buried in the parsing call, and comment that line as the thing to change.
- Add a short block that prints how many elements were found and the first two raw matches, so I can see immediately whether the selector is wrong rather than guessing from an empty output.
- Then tell me in plain English how to find the right selector myself using the browser's inspect tool. That instruction will outlast the script.

Also: one line on whether scraping this site is permitted by its robots.txt and terms, and how I would check. Do not assert that it is allowed.