◆ HTML

Perform reporting and analysis tasks

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All HTML tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskExtract all the H2 headings from the 'Annual Report 2023' page and list them in a plain text…+
Extract all the H2 headings from the 'Annual Report 2023' page and list them in a plain text file. Then, count how many images are on that page.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptI need to present a report on website performance to the executive team next week. Generate a…+
I need to present a report on website performance to the executive team next week. Generate a summary of all pages modified in the last month, their current page titles, and a count of broken links on each. Make sure the data is easy to read.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe sales team is complaining that the 'Contact Us' form isn't reliably sending leads, but I…+
The sales team is complaining that the 'Contact Us' form isn't reliably sending leads, but I can't see any obvious errors in the HTML.
The sales team is complaining that the 'Contact Us' form isn't reliably sending leads, but I can't see any obvious errors in the form's structure or attribute values. I'm afraid there's a subtle issue preventing submission or data capture, and we're losing potential customers. What's the most common reason a form might fail silently, and what's the first thing I should check in the markup to pinpoint the problem?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently spend too much time manually inspecting web page structures for inconsistencies,…+
I frequently spend too much time manually inspecting HTML for inconsistencies or errors when preparing for audits or performance reviews.
I frequently spend too much time manually inspecting web page structures for inconsistencies, missing attributes, or structural errors when preparing for audits or performance reviews. This always feels tedious and prone to human error. What habit should I change in my development and review process to more efficiently identify and address web page quality issues before they become a time-consuming reporting task?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from HTML's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.